MCP Document & Task Server
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
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 |
|---|---|
| search_documentsB | Search documents by title. Returns matching document IDs and titles. |
| get_documentA | Retrieve a document by its ID. Returns the full document including content. |
| create_documentC | Create a new document in the database. |
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 has a clearly distinct purpose: create, retrieve by ID, and search by title. There is no ambiguity between them.
All tools follow a consistent verb_noun pattern in snake_case (create_document, get_document, search_documents), making naming predictable.
With only 3 tools, the server feels minimal for a 'Document & Task Server'. The count is borderline low but not excessively so.
The tool set lacks update and delete operations for documents, and entirely omits task-related functionality despite the server name. This creates significant gaps.