claude-async
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLAUDE_CLI_PATH | No | Path to the claude binary | claude |
| CLAUDE_ASYNC_JOB_DIR | No | Where per-job logs and exit codes are stored | ~/.claude-async-jobs |
| CLAUDE_ASYNC_DEFAULT_CWD | No | Default working directory for jobs | $HOME |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| claude_startA | Start a Claude Code task as a detached background job and return a jobId immediately. Use for any work that might run longer than ~30s. Poll with claude_check. |
| claude_checkA | Check a background job's status and recent output. Returns status (running | completed | failed | orphaned), exit code, and a tail of stdout/stderr. |
| claude_jobsB | List all known background jobs with their current status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/icey2488/claude-async'
If you have feedback or need assistance with the MCP directory API, please join our Discord server