amp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMP_CLI_PATH | No | Absolute path to the Amp CLI, used when the MCP host cannot find 'amp' on its PATH. |
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 |
|---|---|
| read_amp_threadA | Read an Amp coding-agent thread referenced by an Amp thread ID, @T-… mention, or ampcode.com URL. Supports tail reads, tool-output filtering, pagination, and lightweight metadata. |
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 1 tool
With only a single tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined, so an agent would never misselect.
The single tool name 'read_amp_thread' follows a clear verb_noun pattern and is descriptive. There are no other names to create inconsistency.
At only one tool, the server feels thin for a service as complex as Amp. While the tool is functional, it lacks the breadth expected of an integration server.
The tool only supports reading a thread given a reference, with no way to list, search, or interact with threads. This creates a dead end for agents that don't already have a thread ID, making the surface incomplete.