Context11 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTEXT11_URL | No | API base URL | https://context11.com |
| CONTEXT11_API_KEY | Yes | Your Context11 API key (starts with ctx11_) |
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 |
|---|---|
| search_contextB | Search the company knowledge base for relevant context, guidelines, and rules |
| get_documentB | Get the full content of a specific document by ID |
| list_foldersA | List all folders in the workspace |
| list_documentsA | List all documents in a specific folder |
| read_documentB | Read a document's full content by ID |
| update_documentA | Update a document's title and/or content. Content must be in Tiptap JSON format. |
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 6 tools
The tools get_document and read_document are nearly identical—both retrieve full document content by ID—causing clear ambiguity. Other tools are distinct, but this overlap creates confusion over which to use.
Tool names follow a consistent verb_noun pattern (search_, get_, list_, read_, update_). However, the use of both 'get' and 'read' for the same operation is a minor inconsistency that disrupts the pattern.
With 6 tools, the server is well-scoped for a document/knowledge base management purpose. Each tool, apart from the get/read duplication, occupies a clear functional role, and the count is neither sparse nor bloated.
The surface covers search, listing, reading, and updating documents, but lacks create and delete operations. This is a significant gap for a document management server, as users cannot add or remove documents through the tools.