amp-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMP_URL | Yes | Base URL of your AMP install, e.g. https://amp.example.local | |
| MCP_HOST | No | HTTP bind host (HTTP transport only). Docker image overrides to 0.0.0.0. | 127.0.0.1 |
| MCP_PORT | No | HTTP listen port (HTTP transport only) | 3000 |
| LOG_LEVEL | No | pino log level: trace / debug / info / warn / error / fatal. All logs go to stderr. | info |
| AMP_PASSWORD | Yes | AMP password (or remembered-token) | |
| AMP_USERNAME | Yes | AMP admin username | |
| MCP_AUTH_MODE | No | none / bearer / oauth — see Authentication section | none |
| MCP_TRANSPORT | No | stdio (subprocess use) or http (Docker / remote) | stdio |
| MCP_AUTH_TOKEN | No | Comma-separated list of accepted bearer tokens. Required when MCP_AUTH_MODE=bearer. | |
| MCP_PUBLIC_URL | No | Canonical external URL of this server (resource id + JWT audience). Required when MCP_AUTH_MODE=oauth. | |
| MCP_RATE_LIMIT | No | Max requests per window on /mcp. Set 0 to disable. | 120 |
| MCP_TRUST_PROXY | No | Forwarded to Express trust proxy. Set when behind nginx/Caddy so req.ip is the real client. | |
| AMP_ALLOW_WRITES | No | Set true to enable mutating tools | false |
| MCP_OAUTH_ISSUER | No | OAuth 2.1 authorization server issuer URL. Required when MCP_AUTH_MODE=oauth. | |
| MCP_ALLOWED_HOSTS | No | Comma-separated Host header allow-list (DNS rebinding protection). Required when MCP_HOST is 0.0.0.0/:: and MCP_AUTH_MODE=none. | |
| MCP_ALLOW_INSECURE | No | Override the startup guard that refuses 0.0.0.0 + none auth + no host allow-list. | false |
| MCP_OAUTH_AUDIENCE | No | Override expected JWT aud claim. Defaults to MCP_PUBLIC_URL. | |
| MCP_OAUTH_JWKS_URL | No | Override JWKS URL (skips OIDC discovery) | |
| MCP_RATE_WINDOW_MS | No | Rate-limit window length in milliseconds. | 60000 |
| MCP_ALLOWED_ORIGINS | No | Comma-separated Origin allow-list. Requests with a mismatching Origin get 403; requests with no Origin (server-to-server) are allowed. | |
| MCP_OAUTH_REQUIRED_SCOPES | No | Comma-separated scopes required on every request |
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 |
|---|---|
| amp_list_instancesA | Enumerate all instances managed by the AMP controller. Returns InstanceID, name, module type, running state, and parent target for each game-server instance. |
| amp_get_instance_statusA | Get state, uptime, and metrics (CPU, RAM, players) for a single AMP instance. Pass an InstanceID from amp_list_instances. |
| amp_get_active_usersB | List currently connected users / players for one AMP instance. Returns a map of session UID to username. |
| amp_get_console_outputA | Read recent console output for one AMP instance. AMP returns whatever buffer is currently held; pass |
| amp_get_host_statusA | Get state, uptime, and metrics (CPU, RAM) for the AMP controller host machine itself (not a game-server instance). |
| amp_get_running_tasksA | List currently-running tasks on one AMP instance (backups, updates, etc.) with progress percentage. Useful for polling whether amp_take_backup or amp_update_application has finished. |
| amp_get_update_infoA | Check whether a game-server update is available for one AMP instance. Returns the available version, build, and release notes URL. |
| amp_list_backupsA | List all local backups for one AMP instance (most-recent first per AMP's ordering). Returns whatever shape AMP's LocalFileBackupPlugin reports. |
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
Each tool targets a distinct resource and action, with no apparent overlap. For example, amp_get_active_users retrieves users, amp_get_console_output reads logs, and amp_get_host_status monitors host metrics, all clearly separate.
All tools follow the 'amp_{verb}_{noun}' pattern using lowercase and underscores. 'get_' is used for single resource or status retrieval, and 'list_' for enumerations, ensuring predictable naming.
With 8 tools, the set is well-scoped for an AMP server management context. The tools cover essential monitoring and listing operations without being over or under populated.
The set lacks control actions such as starting, stopping, or updating instances, which are typical for a management server. While monitoring tools are decent, the absence of lifecycle operations is a notable gap.