add-parallel
Skill98 starsChanged 8 months agoApache-2.0View on GitHub
Adds Parallel AI MCP integration to MatClaw for advanced web research capabilities. User must have: 1. Parallel AI API key from https://platform.parallel.ai 2. MatClaw already set up and running 3. Docker installed and running Run all steps automatically. Only pause for user input when explicitly needed. Use AskUserQuestion: Do you have a Parallel AI API key, or should I help you get one? If they have one: Collect it now. If they need one: Tell them: 1. Go to https://platform.parallel.ai…
- Reads credentials
8 other projects use a version of this, 8 of them edited.
Adopted by
Most recently taken up by
- shivasaini04/nanocrewedited, first seen Nov 15, 2026
- juancruzmunozalbelo/swarmclawedited, first seen Oct 8, 2026
- Runchuan-BU/BioClawedited, first seen Aug 2, 2026
- microsoft/amplifier-app-nanoclawedited, first seen Jun 12, 2026
- mcarmona1064-cell/clawbridge-codexedited, first seen May 11, 2026
- sskarz/nanoclawbsteredited, first seen Mar 11, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 8
- Runchuan-BU/BioClaw★ 40588% same
- microsoft/amplifier-app-nanoclaw★ 589% same
- shivasaini04/nanocrew★ 493% same
- jaypyles/nanoclaw-discord★ 289% same
- sskarz/nanoclawbster★ 293% same
- breakcafe/picoclaw★ 193% same
- juancruzmunozalbelo/swarmclaw★ 189% same
- mcarmona1064-cell/clawbridge-codex★ 192% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-dingtalkSkill
- add-discordSkill
- add-gmailSkill
- add-ollama-toolSkill
- add-slackSkill
- add-telegramSkill
- add-telegram-swarmSkill
- add-vaspSkill
- add-voice-transcriptionSkill
- add-whatsappSkill
- convert-to-apple-containerSkill
- customizeSkill
- debugSkill
- get-qodo-rulesSkill
- qodo-pr-resolverSkill
- setupSkill
- update-matclawSkill
- use-local-whisperSkill
- x-integrationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. 12 are common, 0 are distinctive, and 12 are very specific to this project.
12
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 20
Run all steps automatically.
- Common: line 37
Wait for the API key.
- Very specific: line 41
Add PARALLEL_API_KEY to .env:
- Very specific: line 67
Add PARALLEL_API_KEY to allowed environment variables in src/container-runner.ts:
- Very specific: line 90
Add Parallel AI MCP servers after the matclaw server:
- Very specific: line 133
Add Parallel AI usage instructions to groups/main/CLAUDE.md:
- Common: line 185
Use the Parallel Task MCP to check the task status
- Common: line 186
If status is 'completed', extract the results
- Common: line 188
Use mcp__matclaw__complete_scheduled_task to mark this task as done
- Common: line 190
If status is still 'running' or 'pending', do nothing (task will run again in 30s).
- Common: line 191
If status is 'failed', send error message and complete the task."
- Common: line 240
Wait 3 seconds for service to start, then verify:
- Common: line 258
Check logs to verify MCP servers loaded:
- Very specific: line 268
Check that type: 'http' is specified in MCP server config
- Common: line 269
Verify API key is correct in .env
- Very specific: line 270
Check container logs: cat groups/main/logs/container-*.log | tail -50
- Very specific: line 273
Ensure PARALLEL_API_KEY is in .env
- Very specific: line 274
Verify container-runner.ts includes PARALLEL_API_KEY in allowedVars
- Common: line 275
Check agent-runner logs for "Parallel AI MCP servers configured" message
- Very specific: line 278
Verify scheduled task was created: sqlite3 store/messages.db "SELECT * FROM scheduled_tasks"
- Very specific: line 279
Check task runs: tail -f logs/matclaw.log | grep "scheduled task"
- Common: line 280
Ensure task prompt includes proper Parallel MCP tool names
- Very specific: line 286
Remove from .env: sed -i.bak '/PARALLEL_API_KEY/d' .env
- Very specific: line 288
Remove Web Research Tools section from groups/main/CLAUDE.md
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add Parallel AI Integration
Adds Parallel AI MCP integration to MatClaw for advanced web research capabilities.
What This Adds
- Quick Search - Fast web lookups using Parallel Search API (free to use)
- Deep Research - Comprehensive analysis using Parallel Task API (asks permission)
- Non-blocking Design - Uses MatClaw scheduler for result polling (no container blocking)
Prerequisites
User must have:
- Parallel AI API key from https://platform.parallel.ai
- MatClaw already set up and running
- Docker installed and running
Implementation Steps
Run all steps automatically. Only pause for user input when explicitly needed.
1. Get Parallel AI API Key
Use AskUserQuestion: Do you have a Parallel AI API key, or should I help you get one?
If they have one: Collect it now.
If they need one: Tell them:
- Go to https://platform.parallel.ai
- Sign up or log in
- Navigate to API Keys section
- Create a new API key
- Copy the key and paste it here
Wait for the API key.
2. Add API Key to Environment
Add PARALLEL_API_KEY to .env:
# Check if .env exists, create if not
if [ ! -f .env ]; then
touch .env
fi
# Add PARALLEL_API_KEY if not already present
if ! grep -q "PARALLEL_API_KEY=" .env; then
echo "PARALLEL_API_KEY=${API_KEY_FROM_USER}" >> .env
echo "✓ Added PARALLEL_API_KEY to .env"
else
# Update existing key
sed -i.bak "s/^PARALLEL_API_KEY=.*/PARALLEL_API_KEY=${API_KEY_FROM_USER}/" .env
echo "✓ Updated PARALLEL_API_KEY in .env"
fiVerify:
grep "PARALLEL_API_KEY" .env | head -c 503. Update Container Runner
Add PARALLEL_API_KEY to allowed environment variables in src/container-runner.ts:
Find the line:
const allowedVars = ['CLAUDE_CODE_OAUTH_TOKEN', 'ANTHROPIC_API_KEY'];Replace with:
const allowedVars = ['CLAUDE_CODE_OAUTH_TOKEN', 'ANTHROPIC_API_KEY', 'PARALLEL_API_KEY'];4. Configure MCP Servers in Agent Runner
Update container/agent-runner/src/index.ts:
Find the section where mcpServers is configured (around line 237-252):
const mcpServers: Record<string, any> = {
matclaw: ipcMcp
};Add Parallel AI MCP servers after the matclaw server:
const mcpServers: Record<string, any> = {
matclaw: ipcMcp
};
// Add Parallel AI MCP servers if API key is available
const parallelApiKey = process.env.PARALLEL_API_KEY;
if (parallelApiKey) {
mcpServers['parallel-search'] = {
type: 'http', // REQUIRED: Must specify type for HTTP MCP servers
url: 'https://search-mcp.parallel.ai/mcp',
headers: {
'Authorization': `Bearer ${parallelApiKey}`
}
};
mcpServers['parallel-task'] = {
type: 'http', // REQUIRED: Must specify type for HTTP MCP servers
url: 'https://task-mcp.parallel.ai/mcp',
headers: {
'Authorization': `Bearer ${parallelApiKey}`
}
};
log('Parallel AI MCP servers configured');
} else {
log('PARALLEL_API_KEY not set, skipping Parallel AI integration');
}Also update the allowedTools array to include Parallel MCP tools (around line 242-248):
allowedTools: [
'Bash',
'Read', 'Write', 'Edit', 'Glob', 'Grep',
'WebSearch', 'WebFetch',
'mcp__matclaw__*',
'mcp__parallel-search__*',
'mcp__parallel-task__*'
],5. Add Usage Instructions to CLAUDE.md
Add Parallel AI usage instructions to groups/main/CLAUDE.md:
Find the "## What You Can Do" section and add after the existing bullet points:
- Use Parallel AI for web research and deep learning tasksThen add a new section after "## What You Can Do":
## Web Research Tools
You have access to two Parallel AI research tools:
### Quick Web Search (`mcp__parallel-search__search`)
**When to use:** Freely use for factual lookups, current events, definitions, recent information, or verifying facts.
**Examples:**
- "Who invented the transistor?"
- "What's the latest news about quantum computing?"
- "When was the UN founded?"
- "What are the top programming languages in 2026?"
**Speed:** Fast (2-5 seconds)
**Cost:** Low
**Permission:** Not needed - use whenever it helps answer the question
### Deep Research (`mcp__parallel-task__create_task_run`)
**When to use:** Comprehensive analysis, learning about complex topics, comparing concepts, historical overviews, or structured research.
**Examples:**
- "Explain the development of quantum mechanics from 1900-1930"
- "Compare the literary styles of Hemingway and Faulkner"
- "Research the evolution of jazz from bebop to fusion"
- "Analyze the causes of the French Revolution"
**Speed:** Slower (1-20 minutes depending on depth)
**Cost:** Higher (varies by processor tier)
**Permission:** ALWAYS use `AskUserQuestion` before using this tool
**How to ask permission:**AskUserQuestion: I can do deep research on [topic] using Parallel's Task API. This will take 2-5 minutes and provide comprehensive analysis with citations. Should I proceed?
**After permission - DO NOT BLOCK! Use scheduler instead:**
1. Create the task using `mcp__parallel-task__create_task_run`
2. Get the `run_id` from the response
3. Create a polling scheduled task using `mcp__matclaw__schedule_task`:Prompt: "Check Parallel AI task run [run_id] and send results when ready.
- Use the Parallel Task MCP to check the task status
- If status is 'completed', extract the results
- Send results to user with mcp__matclaw__send_message
- Use mcp__matclaw__complete_scheduled_task to mark this task as done
If status is still 'running' or 'pending', do nothing (task will run again in 30s). If status is 'failed', send error message and complete the task."
Schedule: interval every 30 seconds Context mode: isolated
4. Send acknowledgment with tracking link
5. Exit immediately - scheduler handles the rest
### Choosing Between Them
**Use Search when:**
- Question needs a quick fact or recent information
- Simple definition or clarification
- Verifying specific details
- Current events or news
**Use Deep Research (with permission) when:**
- User wants to learn about a complex topic
- Question requires analysis or comparison
- Historical context or evolution of concepts
- Structured, comprehensive understanding needed
- User explicitly asks to "research" or "explain in depth"
**Default behavior:** Prefer search for most questions. Only suggest deep research when the topic genuinely requires comprehensive analysis.6. Rebuild Container
Build the container with updated agent runner:
./container/build.shVerify the build:
echo '{}' | docker run -i --entrypoint /bin/echo matclaw-agent:latest "Container OK"7. Restart Service
Rebuild the main app and restart:
npm run build
launchctl kickstart -k gui/$(id -u)/com.matclaw # macOS
# Linux: systemctl --user restart matclawWait 3 seconds for service to start, then verify:
sleep 3
launchctl list | grep matclaw # macOS
# Linux: systemctl --user status matclaw8. Test Integration
Tell the user to test:
Send a message to your assistant:
@[YourAssistantName] what's the latest news about AI?The assistant should use Parallel Search API to find current information.
Then try:
@[YourAssistantName] can you research the history of artificial intelligence?The assistant should ask for permission before using the Task API.
Check logs to verify MCP servers loaded:
tail -20 logs/matclaw.logLook for: Parallel AI MCP servers configured
Troubleshooting
Container hangs or times out:
- Check that
type: 'http'is specified in MCP server config - Verify API key is correct in .env
- Check container logs:
cat groups/main/logs/container-*.log | tail -50
MCP servers not loading:
- Ensure PARALLEL_API_KEY is in .env
- Verify container-runner.ts includes PARALLEL_API_KEY in allowedVars
- Check agent-runner logs for "Parallel AI MCP servers configured" message
Task polling not working:
- Verify scheduled task was created:
sqlite3 store/messages.db "SELECT * FROM scheduled_tasks" - Check task runs:
tail -f logs/matclaw.log | grep "scheduled task" - Ensure task prompt includes proper Parallel MCP tool names
Uninstalling
To remove Parallel AI integration:
- Remove from .env:
sed -i.bak '/PARALLEL_API_KEY/d' .env - Revert changes to container-runner.ts and agent-runner/src/index.ts
- Remove Web Research Tools section from groups/main/CLAUDE.md
- Rebuild:
./container/build.sh && npm run build - Restart:
launchctl kickstart -k gui/$(id -u)/com.matclaw(macOS) orsystemctl --user restart matclaw(Linux)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

