approval-gated-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGM_DATA_DIR | Yes | Path to the directory where the server stores its data (plans, audit log, etc.) | |
| AGM_CLIENT_NAME | Yes | Name of the MCP client connecting to the server (e.g. "claude") |
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 |
|---|---|
| list_campaignsA | List campaigns with status, daily budget, 30-day spend and conversions. |
| propose_budget_changeA | Propose a new daily budget for a campaign. Returns a pending plan with a diff; a person must approve it. |
| propose_status_changeA | Propose pausing or enabling a campaign. Returns a pending plan; a person must approve it. |
| propose_undoA | Propose reversing an applied plan. The undo is itself a plan that needs approval. |
| get_planB | Show a plan's diff and status. |
| list_plansA | List plans, newest first, with their status. |
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 6 tools
Each tool targets a distinct resource or action: listing campaigns vs. plans, proposing budget/status/undo changes, and fetching a single plan. There is no meaningful overlap or confusing boundary between tools.
All names use snake_case with a small set of predictable verb prefixes (list_, propose_, get_). The pattern is consistent throughout, including propose_budget_change, propose_status_change, and propose_undo.
Six tools is well-scoped for an approval-gated campaign change server. Each tool covers a necessary read or propose operation, and none feels redundant or missing at the count level.
The surface covers listing campaigns, proposing budget/status changes, proposing undos, and inspecting plans. It is strong, but if the server is meant to support broader campaign changes, other proposal types (e.g., creative or targeting) would be needed.