MCP ContentEngineering
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| content_get_rawB | Get raw markdown content without any processing. If source is a file, returns that file. If source is a directory, combines ALL .md files into one content with separators |
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 one tool, there is no possibility of ambiguity or overlap between tools. The tool has a single, clearly defined purpose.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'content_get_raw' follows a clear verb_noun pattern.
A single tool is too few for a server named 'ContentEngineering', which suggests a broader domain of content manipulation or processing. This minimal set feels incomplete and thin for the implied scope.
The tool surface is severely incomplete for content engineering. It only provides raw content retrieval, lacking essential operations like content creation, editing, transformation, analysis, or management, which are expected in this domain.