async-claude-agentsdk-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ASYNC_CLAUDE_MCP_PERMISSION_MODE | No | The permission mode for Claude Agent SDK. Default is 'bypassPermissions'. Accepted values: default, acceptEdits, bypassPermissions, plan, dontAsk, auto. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| claudeA | Start a Claude Agent SDK session in the background and immediately return its session handle. |
| claude-continueB | Start another background turn in a completed Claude session and immediately return. |
| claude-statusA | Return an immediate snapshot of a Claude session, including current todos and reported problems. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.