agent-content-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_CONTENT_KEY | Yes | The API key from the site's django-agent-content installation. | |
| AGENT_CONTENT_URL | Yes | The site's API root. Must be `https://`; plain `http://` is accepted only for `localhost`. |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agent_content_statusB | Explains why the site's content tools are unavailable. |
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 1 tool
With only a single tool, there is no possibility of overlap or misselection between tools. The lone tool's purpose (explaining tool unavailability) is unambiguous on its face.
The single name 'agent_content_status' uses a clean snake_case noun_qualifier pattern and is well-formed. However, a one-tool surface provides no real pattern to validate consistency against, so it cannot earn a full 5.
The server exposes exactly one trivial status/stub tool, an extreme mismatch for a server named agent-content-mcp that implies content management capabilities. There is essentially no functional surface to speak of.
The only tool merely explains why content tools are unavailable, meaning the entire content lifecycle (read/create/update/delete) is absent. This is a severely incomplete surface for the stated domain.