Contextual MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your Contextual AI API key | |
| AGENT_ID | Yes | Your Contextual AI agent ID |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queryC | An enterprise search tool that can answer questions about any sort of knowledge base |
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 confusion or overlap between tools.
A single tool name is inherently consistent; 'query' is a clear verb describing its action.
The server claims to handle 'any sort of knowledge base' but provides only a generic search tool, which feels too limited for the broad scope.
Missing essential tools for managing knowledge bases (e.g., listing sources, retrieving documents, updating content), leaving agents with only a single query capability.