content-knowledge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KNOWLEDGE_PATH | Yes | Path to the folder containing the knowledge markdown files (guidelines/, templates/catalog.md, past-posts/). |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_guidelinesB | Search the company brand and editorial rules. Returns matching rule blocks with their IDs (R#), e.g. 'tone course post linkedin'. |
| list_visual_templatesA | List the official visual template catalog with usage rules (T# IDs). Optional query filters by content type, e.g. 'annuncio corso'. Empty query returns the full catalog. |
| get_post_examplesA | Retrieve past posts with their outcomes, for tone calibration. Query by topic, channel or type, e.g. 'linkedin annuncio'. Returns up to 3 examples; never copy sentences from them. |
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 targets a distinct knowledge resource: editorial rules, visual templates, and past post examples. The descriptions clearly distinguish search, list, and get operations despite all supporting query. An agent can reliably choose the correct tool for each content creation step.
All tool names follow the consistent snake_case verb_noun pattern: search_guidelines, list_visual_templates, get_post_examples. The verbs also accurately reflect the operation type, making the naming predictable and scannable.
With only three tools, the server is tightly focused on content knowledge retrieval. Each tool covers a core knowledge domain for content creation—rules, templates, and examples—without redundant or unnecessary additions.
The set covers the main content-making inputs: brand/editorial guidelines, visual template catalog, and performance-calibrated post examples. Minor gaps exist such as fetching a specific rule by ID or retrieving more than three examples, but the tool set supports its purpose effectively.