Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/eddinsw/amp-mcp-server/agents-mdgit clone --depth 1 https://github.com/eddinsw/amp-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/eddinsw/amp-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/eddinsw/amp-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/eddinsw/amp-mcp-server/agents-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.04023 | $0.04023 |
| Opus 5 | $0.02011 | $0.02011 |
| Sonnet 5 | $0.00805 | $0.00805 |
| Haiku 4.5 | $0.00402 | $0.00402 |
Grade A, and why
amp-mcp-server AGENTS.md scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
├── Dockerfile # multi-stage; HEALTHCHECK uses node fetch (no curl in slim image) How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — amp-mcp-server
Context for AI coding agents (Claude Code, Codex, etc.) working on this repository.
Current state (v0.2.1, 2026-05-01)
- What's running: stable. v0.2.1 ships HTTP auth (bearer + OAuth 2.1), security hardening (host/origin allow-lists, rate limiting, unsafe-binding guard), and a
/healthliveness endpoint. v0.1 was already verified end-to-end against Will's live homelab AMP athttps://amp.darkforge.app. - Hosting: GitLab is primary (
https://gitlab.darkforge.app/weddins/amp-mcp-server). A push mirror to GitHub (https://github.com/eddinsw/amp-mcp-server) is being set up so the public can see the code; PRs from outside contributors land on GitHub but merges happen on the GitLab side. - CI/CD: GitLab CI builds + pushes Docker images to the GitLab registry on every push to
mainand on tags. No GitHub Actions. - Tests: vitest with 23 passing unit tests covering auth middleware (bearer, OAuth, scope check, audience check, error paths). Integration smoke-tested manually for the security guards (rate limit, origin, host, unsafe-bind refuse).
- Build:
npm run buildclean.npm testclean.
The earlier Phase A–D framing is retired — that was v0.1 packaging. We're past it.
What this is
An MCP (Model Context Protocol) server that wraps CubeCoders AMP (Application Management Panel) so MCP clients — Claude Desktop, Claude Code, Claude.ai, others — can list, inspect, and control AMP-managed game-server instances.
CubeCoders AMP is a paid, self-hosted game-server control panel. This project is a client of AMP's public REST API; no AMP source or binaries are redistributed. Users bring their own licensed AMP install.
Why it exists
No MCP server existed for AMP. Will runs AMP in his homelab. Building this gives Claude direct, structured access to start/stop game servers, send console commands, take backups, and read server state without screen-scraping the AMP web UI.
Architecture
MCP client (Claude.ai / Desktop / Code / custom)
│ stdio ── or ── HTTP (stateless Streamable + bearer/OAuth)
▼
amp-mcp-server
│
├─ src/transports/{stdio,http}.ts (transport entrypoints)
├─ src/server.ts (per-request McpServer factory)
├─ src/tools/{instances,console,operations}.ts (registered tools)
├─ src/auth/{bearer,oauth,shared}.ts (HTTP auth middleware)
├─ src/config.ts (zod-validated env loader)
└─ src/amp-client.ts ── REST/JSON ──▶ AMP install (homelab)
└─▶ @neuralnexus/ampapi (typed AMP client; native fetch, no transitive deps)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 233 lines · 4,023 tokens per session scan A e65edda105bc
amp-mcp-server AGENTS.md is an instructions file published in the GitHub repository eddinsw/amp-mcp-server (4 stars, last pushed 4mo ago), licensed MIT. It adds 4,023 tokens to every session, about $0.0201 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.