async-claude-agentsdk-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@async-claude-agentsdk-mcp start a new Claude session to review the main.js file"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
async-claude-agentsdk-mcp
An MCP server that lets coding agents run Claude Agent SDK sessions as asynchronous sub-agents.
claude and claude-continue return as soon as the background turn is scheduled. They never hold an MCP request open while Claude works. claude-status is an immediate point-in-time read of the in-memory session state.
Tools
claude
Starts a new Claude session and immediately returns a wrapper-owned session_id.
Inputs:
prompt(required): the task for Claude;model(optional): a Claude model override;effort(optional):low,medium,high,xhigh, ormax;cwd(optional): the working directory for the session.
Example result:
{
"session_id": "0bd9d545-6016-4a5e-89b7-93f85a059f38",
"status": "running",
"turn": 1,
"message": "Claude is running asynchronously. The MCP call is complete."
}claude-continue
Starts another background turn in a completed session. It keeps the wrapper session_id and resumes the underlying Claude Agent SDK session.
Inputs:
session_id(required): the handle returned byclaude;prompt(required): the next prompt.
Continuation is rejected while the preceding turn is running or if it failed without producing a resumable Claude session.
claude-status
Returns the current state without waiting for a change. The response includes:
lifecycle status:
running,completed, orfailed;the underlying Claude session ID once the SDK reports it;
the latest status summary and todo list reported by Claude;
caller-relevant problems reported by Claude;
the latest completed result or failure;
originating Codex session, thread, and turn IDs when Codex supplied them in MCP
_meta.
Related MCP server: claude-mcp-bridge
Claude status reporting
Every Claude run receives an in-process MCP server with two tools:
report_status: replaces the current todo list and optionally records the current focus;report_problem: appends a risk, blocker, or failure for the caller.
The tools only update session state and send best-effort MCP logging notifications. They do not block Claude waiting for the caller. Native TodoWrite calls are also captured when present in the Agent SDK message stream.
Permissions
The default permission mode is bypassPermissions. This intentionally gives Claude unrestricted tool execution in its environment and requires the Agent SDK's allowDangerouslySkipPermissions acknowledgement.
Set ASYNC_CLAUDE_MCP_PERMISSION_MODE to change it:
export ASYNC_CLAUDE_MCP_PERMISSION_MODE=defaultAccepted values are default, acceptEdits, bypassPermissions, plan, dontAsk, and auto.
Run
Run the latest published version without installing it globally:
npx --yes @wyrd-company/async-claude-agentsdk-mcpExample Codex configuration:
[mcp_servers.async_claude]
command = "npx"
args = ["--yes", "--@wyrd-company:registry=https://registry.npmjs.org", "@wyrd-company/async-claude-agentsdk-mcp"]The server uses stdio and writes protocol messages only to stdout. Claude Agent SDK authentication and settings are inherited from the server process environment.
The explicit scope registry in the Codex configuration ensures npmjs is used even when the local npm configuration routes @wyrd-company packages to another registry.
For a global installation instead, run npm install --global @wyrd-company/async-claude-agentsdk-mcp and use async-claude-agentsdk-mcp as the command.
Session records are in memory. They survive multiple MCP tool calls and Claude turns while the stdio server remains running, but they do not survive a server restart.
Publishing
The package is published publicly to npmjs and GitHub Packages as @wyrd-company/async-claude-agentsdk-mcp. The Publish Package GitHub Actions workflow validates the release, publishes to npmjs with provenance using the repository's NPM_TOKEN Actions secret, and then publishes to GitHub Packages using its GITHUB_TOKEN.
Run the workflow manually, or push a bare SemVer tag that exactly matches the version in package.json, for example 0.1.0. Tags prefixed with v do not trigger publishing.
The GitHub Packages release inherits the public repository's visibility and permissions. Publishing npmjs first lets a failed GitHub Packages job be retried without attempting the immutable npmjs version again.
After the first release creates the npmjs package, configure npm trusted publishing for publish-package.yml and remove NODE_AUTH_TOKEN from the npmjs job to eliminate the long-lived publishing token.
Development
npm install
npm test
npm run build
npm startAvailable Tools
3 toolsclaudeA
Start a Claude Agent SDK session in the background and immediately return its session handle.
Inputs: prompt (required), cwd, model, effort.
claude-continueB
Start another background turn in a completed Claude session and immediately return.
Inputs: prompt (required), session_id (required).
claude-statusA
Return an immediate snapshot of a Claude session, including current todos and reported problems.
Inputs: session_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool targets a distinct action on a session: starting, continuing, and checking status. No overlap or ambiguity.
All tool names follow the same hyphenated pattern with a 'claude-' prefix and action verb, ensuring predictability.
Three tools is appropriate for managing Claude sessions—covering initialization, continuation, and status—without being too few or too many.
The set covers starting and reading status, but lacks an explicit end/stop session tool, which could hinder agent workflows requiring session cleanup.
Maintenance
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
MCP server for building and testing AI agents with multi-model experimentation and insights.
Shared memory and mail for your AI agents. Verified with Claude Code; other MCP clients in testing.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Related MCP Servers
- AlicenseAqualityDmaintenanceThis MCP server enables remote control and management of Claude Code agents, allowing you to execute missions, configure agent personalities, and integrate with other MCP tools.715 npm1MIT
- AlicenseAqualityDmaintenanceMCP server that lets any agent or MCP host delegate tasks to Claude Code running headless, with tools for review, validation, analysis, and autonomous work.42MIT
- AlicenseAqualityFmaintenanceMCP server for running external coding agents as background tasks inside Claude Code. Supports multiple backends including Codex, Grok, GLM, DeepSeek, and more.7MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables Claude to orchestrate multiple autonomous Claude Code agents working in parallel across different projects, with tools to dispatch, monitor, and manage their progress.669 npm1MIT