platform-mcp-stub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APPROVALS_FILE | No | Path to the approvals ledger file. Defaults to 'approvals.json' at the repo root. | approvals.json |
| ANTHROPIC_ADMIN_KEY | No | Admin API key (sk-ant-admin01-...) for live usage and rate limit data. If not set, fixture data is returned. |
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 |
|---|---|
| request_api_keyA | Request an API key for a given scope. This does NOT mint a key: it files a pending approval request that a human operator must approve out-of-band by running the companion CLI ( |
| get_usage_summaryA | Last 7 days of organization token usage, daily buckets grouped by model, via the Anthropic Usage Admin API (GET /v1/organizations/usage_report/messages). Requires an Admin API key (sk-ant-admin01-...) in ANTHROPIC_ADMIN_KEY; without one, returns a clearly-labeled fixture with the real response schema. |
| get_limit_statusA | The organization's configured rate limit groups (per-model-group RPM/ITPM/OTPM, batch queue limits, ...) via the Anthropic Rate Limits Admin API (GET /v1/organizations/rate_limits). Requires an Admin API key in ANTHROPIC_ADMIN_KEY; without one, returns a clearly-labeled fixture with the real response schema. |
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 3 tools
Each tool addresses a distinct domain area: rate limits, API key requests, and usage summaries. There is no meaningful overlap between them, and the status-checking behavior inside request_api_key is clearly documented rather than being a separate ambiguous tool.
All tool names follow a consistent verb_noun pattern in snake_case: get_limit_status, request_api_key, get_usage_summary. The verbs are descriptive and the naming style is uniform across the set.
Three tools is a reasonable scope for a platform admin stub focused on limits, usage, and key requests. Each tool covers a distinct administrative area without unnecessary bloat or redundant operations.
The set covers the main admin concerns suggested by the server name: rate limits, usage reporting, and API key access requests. Minor gaps exist, such as no direct approval or managed key listing, but these appear intentionally delegated to an out-of-band CLI process.