Skip to main content
Glama
vadim0x60

amp-mcp

by vadim0x60
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

amp-mcp

amp-mcp lets MCP-compatible coding harnesses read Amp threads referenced in commit messages, pull requests, and source code.

It exposes one tool, read_amp_thread. The server is deliberately read-only: it cannot create, continue, rename, share, archive, or delete threads.

How it works

The server runs locally over stdio and calls the authenticated Amp CLI:

MCP host → read_amp_thread → amp threads markdown → Amp

It does not read, copy, or store Amp credentials. A thread is available only when amp threads markdown <thread-id> allows the signed-in user to read it.

Related MCP server: reddit-mcp

Requirements

  • Node.js 20 or later

  • The Amp CLI installed and signed in

Verify Amp before configuring the MCP server:

amp --version
amp threads markdown T-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Install from this checkout

npm install
npm run build

Configure your coding harness to launch the built server. Most MCP hosts accept this shape:

{
  "mcpServers": {
    "amp-threads": {
      "command": "node",
      "args": ["/absolute/path/to/amp-mcp/dist/index.js"]
    }
  }
}

If the host cannot find amp (common when a desktop app has a restricted PATH), set its absolute location:

{
  "mcpServers": {
    "amp-threads": {
      "command": "node",
      "args": ["/absolute/path/to/amp-mcp/dist/index.js"],
      "env": {
        "AMP_CLI_PATH": "/absolute/path/to/amp"
      }
    }
  }
}

Find that path with command -v amp on macOS/Linux or where amp on Windows.

After this package is published, hosts can instead launch it with npx:

{
  "mcpServers": {
    "amp-threads": {
      "command": "npx",
      "args": ["-y", "amp-mcp"]
    }
  }
}

Tool

read_amp_thread

Reads a thread as Markdown. thread accepts all common reference forms:

  • T-019fcd6f-9212-7238-aaf7-3f08ffee3c7f

  • @T-019fcd6f-9212-7238-aaf7-3f08ffee3c7f

  • https://ampcode.com/threads/T-019fcd6f-9212-7238-aaf7-3f08ffee3c7f

Long threads are returned in pages. The optional arguments are:

Argument

Default

Description

offset

0

Character offset at which to read; negative values count from the end

limit

100000

Maximum characters to return, up to 500000

include_tool_outputs

true

Set to false to replace raw tool results with omission markers

max_tool_output_length

—

Truncate each tool result to this many characters

mode

full

Set to metadata for thread metadata and the latest conversation message

Filtering is applied before offsets and character counts, so pagination offsets always refer to the selected representation. When more content exists, the result gives the exact offset for the next call. For example, offset: -100000 reads the final 100,000 characters without first fetching the beginning of the thread.

Metadata mode returns the title, creation time, agent mode, readable status, user-turn count, original and filtered character lengths, and the latest non-tool-result conversation message. The Amp Markdown export does not expose live execution status, which is called out in the result.

Development

npm run check

To exercise the server interactively with the MCP Inspector:

npx @modelcontextprotocol/inspector node dist/index.js

Copyright © Archestra AI

Available Tools

1 tool
read_amp_threadRead Amp threadA
Read-onlyIdempotent

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
modeNoUse metadata for a lightweight overview and latest conversation message. Defaults to full.
limitNoMaximum characters to return. Defaults to 100000.
offsetNoCharacter offset at which to read. Negative values count from the end. Defaults to 0.
threadYesAmp thread ID, @T-… mention, or URL such as https://ampcode.com/threads/T-….
include_tool_outputsNoInclude raw tool result output. Defaults to true.
max_tool_output_lengthNoTruncate each raw tool result output to this many characters.

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate a read-only, idempotent, non-destructive operation. The description adds behavioral context beyond annotations by mentioning support for tail reads, tool-output filtering, pagination, and metadata mode. It does not mention any side effects or failure modes, but these are not expected for a read-only tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, front-loaded with the core purpose, and every clause adds value. It avoids restating the schema or including irrelevant details, making it highly concise and scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 parameters and no output schema, the description covers the core purpose and salient features, but it does not explicitly describe the return format (e.g., text vs. JSON). However, the schema already details parameter behavior, and the description's feature list gives sufficient context for an agent to invoke the tool correctly. It is nearly complete for a read tool with good annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides 100% coverage of parameter descriptions, so the baseline is 3. The description adds value by grouping parameters into named features (tail reads, tool-output filtering, pagination, metadata) that map to offset, include_tool_outputs, limit, and mode, respectively. This helps the agent infer parameter usage without reading the full schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool reads an Amp coding-agent thread, with a specific verb (Read) and resource (Amp coding-agent thread). It also lists the accepted reference formats (ID, @T-… mention, URL) and key capabilities, making the purpose unambiguous even without sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage from the tool name and context, but it does not explicitly state when to use this tool versus alternatives. With no sibling tools listed, there is no exclusionary guidance. The intended use is clear but not explicitly spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0
Disambiguation5/5

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.

Naming Consistency5/5

The single tool name 'read_amp_thread' follows a clear verb_noun pattern and is descriptive. There are no other names to create inconsistency.

Tool Count3/5

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.

Completeness2/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

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/vadim0x60/amp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server