ContextEngine MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTEXT_ENGINE_API_KEY | No | API key for authentication with ContextEngine |
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 |
|---|---|
| start_context_engineC | Starts the context engine and returns a confirmation message. |
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 confusion or overlapping purposes. The tool's purpose is clear and unique within the set.
The single tool name follows a clear verb_noun pattern ('start_context_engine'). With only one tool, the naming is internally consistent and predictable.
A single trivial start tool is an extreme mismatch for a server purporting to be a 'ContextEngine'. The server appears far too thin to be useful for any meaningful workflow.
The server offers only a start operation with no corresponding stop, status, configuration, or query capabilities. This is severely incomplete for any engine lifecycle or context management purpose.