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 |
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
} |
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 | |
TDQS
Scored across 3 tools
Each tool serves a distinct purpose: starting a job, checking a specific job, and listing all jobs. No overlap in functionality.
All tools share the 'claude_' prefix, but the second part mixes verbs (check, start) and a noun (jobs). Consistent prefix but slightly inconsistent in part-of-speech.
Three tools is well-scoped for managing async background jobs, covering the essential operations without bloat.
Covers starting, checking, and listing jobs. Missing a cancel/abort tool, but the core workflow is functional.