Back-Agent MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Set logging verbosity | INFO |
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 |
|---|---|
| execute-taskA | IMPORTANT: This is an AI programming assistant tool, NOT a direct shell command executor. This tool spawns Claude Code (an AI coding agent) as a subprocess to complete development tasks. Claude Code will interpret your natural language request and autonomously decide which actions to take (reading files, editing code, running commands, etc.) to accomplish the goal. What it does:
What it does NOT do:
Example usage:
The returned output is Claude Code's conversational response, not raw command output. |
| create-taskA | IMPORTANT: This creates a background task for an AI programming assistant, NOT a direct shell command executor. Spawns Claude Code (an AI coding agent) as a subprocess to complete development tasks in the background. Claude Code will interpret your natural language request and autonomously decide which actions to take. What it does:
What it does NOT do:
Returns a task ID. Use get-task-status to check progress and get-task-result to retrieve the output. |
| get-task-statusB | Get the current status of a task. Returns status, timestamps, and basic info. |
| get-task-resultA | Get the full result of a task including stdout/stderr output. Only available for completed tasks. |
| cancel-taskC | Cancel a pending or running task. |
| list-tasksC | List all tasks, optionally filtered by status. |
| delete-taskB | Delete a task from the task list. Use this to clean up old completed tasks. |
| get-task-statsC | Get statistics about all tasks. |
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 8 tools
There is significant overlap between create-task and execute-task, both described as spawning Claude Code AI for development tasks with similar capabilities and limitations, which could cause confusion. However, other tools like cancel-task, delete-task, get-task-result, get-task-status, list-tasks, and get-task-stats have clearer distinct purposes related to task management.
Tool names follow a consistent verb-noun pattern with hyphens (e.g., create-task, get-task-status), making them predictable and readable. The only minor deviation is execute-task, which uses a different verb than the others but still fits the pattern.
With 8 tools, the server is well-scoped for task management and AI programming assistance. Each tool has a clear role, such as creating, executing, monitoring, and managing tasks, which fits the server's purpose without being overly sparse or bloated.
The tool set covers the full lifecycle of tasks (create, execute, status, result, cancel, delete, list, stats), providing good coverage for task management. A minor gap is the lack of tools for updating or modifying tasks, but agents can work around this by recreating tasks if needed.