Claude Code MCP Async Server
Asynchronous MCP wrapper for Claude Code CLI
Enable Claude Code to spawn child Claude Code sessions for parallel task execution.
Features
- ✅ Async execution - Start tasks in background, continue working
- ✅ Multi-instance parallelism - Run multiple Claude Code sessions simultaneously
- ✅ Automatic cleanup - No zombie processes
- ✅ Zero config - Works out of the box
Quick Start
🚀 Install with UVX
Zero configuration - just run:
uvx claudecode-mcp-async
Configure Claude Code
Add to your ~/.claude/settings.json:
{
"mcpServers": {
"claude-code-mcp": {
"command": "uvx",
"args": ["claudecode-mcp-async"],
"env": {}
}
}
}
Restart Claude Code
Reload or restart Claude Code to load the MCP server.
Usage Examples
🚀 Async Execution (Game Changer!)
Start a long task and continue working immediately:
You:
Please analyze the entire project code and generate a comprehensive technical report
Claude: I'll analyze your entire project and generate a technical report. This is a large task, so I'll start it asynchronously...
✅ Task Started (Task ID: abc12345) You can continue working on other things while it runs in the background!
You: (Continue working immediately)
While the report is generating, help me write some unit tests
Claude: Sure! Let me write those unit tests for you...
You: (A few minutes later)
Can you check if the report task is finished?
Claude: ✅ Report Complete!
[View Detailed Technical Report]
- Project structure analysis
- Code quality assessment
- Performance optimization recommendations
- Security audit results
⚡ Parallel Execution
Run multiple tasks simultaneously:
You:
I need to do three things at once:
- Generate unit tests for utils.py
- Refactor database.py to use async/await
- Add type hints to all functions in api.py
Claude: I'll start all three tasks in parallel!
🔄 Task 1 Started (Task ID: task1) - Generating unit tests 🔄 Task 2 Started (Task ID: task2) - Refactoring database code 🔄 Task 3 Started (Task ID: task3) - Adding type hints
All tasks are running in parallel...
You: (Later)
Are all three tasks finished?
Claude: ✅ All Complete!
- ✅ Task 1: Unit tests for utils.py generated
- ✅ Task 2: database.py refactored to async mode
- ✅ Task 3: Type hints added to api.py functions
🎯 Quick Sync Tasks
For simple immediate tasks:
You:
Write a Python function to validate email addresses
Claude:
import re
def validate_email(email):
pattern = r'^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$'
return re.match(pattern, email) is not None
# Usage examples
print(validate_email("user@example.com")) # True
print(validate_email("invalid-email")) # False
✅ Task Complete!
Why Async?
Problem: Claude Code blocks the parent session while running.
Solution: This MCP server spawns child Claude Code processes that run in the background.
Benefits:
- 🚀 Start a task and continue working immediately
- ⚡ Run multiple tasks in parallel
- 🎯 No blocking, no waiting
- 🧹 Automatic process cleanup
Troubleshooting
Server not showing up?
- Use absolute path in config
- Run:
chmod +x claudecode_mcp_async_server.py - Restart Claude Code
Task stuck in "running"?
- Wait a moment, large tasks take time
- Check:
ls -la /tmp/claude_code_tasks/ - View logs:
tail -f /tmp/claude_code_mcp_debug.log
Requirements
- Python 3.6+
- Claude Code CLI installed
License
MIT License
Questions? Open an issue on GitHub.
Metadata
Release files for iflow-mcp_jeanchristophe13v_claudecode-mcp-async 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_jeanchristophe13v_claudecode_mcp_async-1.0.0.tar.gz | 14.2 kB | Without provenance | Details for iflow_mcp_jeanchristophe13v_claudecode_mcp_async-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_jeanchristophe13v_claudecode_mcp_async-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_jeanchristophe13v_claudecode_mcp_async-1.0.0-py3-none-any.whl |
Total release size: 27.0 kB
Release files / iflow_mcp_jeanchristophe13v_claudecode_mcp_async-1.0.0.tar.gz
| Download URL | iflow_mcp_jeanchristophe13v_claudecode_mcp_async-1.0.0.tar.gz |
|---|---|
| Size | 14.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
607ed23dfc1146b46b4ec7962d8fac40f307f3ea11879cc38d1f19458860744f
|
|
BLAKE2b-256 checksum How to use checksums |
91799495abdf1f8311cd50a8bedc8e8a1dbce184ab8d60950faabb68d78b6623
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.26 {"installer":{"name":"uv","version":"0.9.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_jeanchristophe13v_claudecode_mcp_async-1.0.0-py3-none-any.whl
| Download URL | iflow_mcp_jeanchristophe13v_claudecode_mcp_async-1.0.0-py3-none-any.whl |
|---|---|
| Size | 12.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fe247f8adea6e9451864ba5c1c2f89b46d67a9f01464a1a7e80e6bafa1619f68
|
|
BLAKE2b-256 checksum How to use checksums |
01eef9858444c57db0cef0d1e758fb0617196e5361ee42b7f799fe80c376cbca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.26 {"installer":{"name":"uv","version":"0.9.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_jeanchristophe13v_claudecode-mcp-async 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.