Docket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHON_BIN | No | Python executable used by the Next.js API routes. | python3 |
| GEMINI_MODEL | No | Override to use another Gemini model. | gemini-2.5-flash |
| GEMINI_API_KEY | No | Gemini 2.5 Flash API key. Without it, the heuristic fallback extractor is used. | |
| NOTION_API_KEY | Yes | Your Notion internal integration secret (ntn_...). Required for real Notion integration. | |
| NOTION_DATABASE_ID | Yes | 32-character ID from the Notion database URL. Required for real Notion integration. | |
| NOTION_OWNER_PROPERTY | No | The assignee/owner text column. | Owner |
| NOTION_TITLE_PROPERTY | No | The name of the title column in your Notion database. | Name |
| NOTION_SOURCE_PROPERTY | No | Text property tagging where the task came from. | Source Meeting |
| NOTION_STATUS_PROPERTY | No | Used to filter out completed tasks. | Status |
| NOTION_DUE_DATE_PROPERTY | No | Must be a Notion Date property. | Due Date |
| NOTION_STATUS_DONE_VALUES | No | Comma-separated list of done status values to exclude. | Done,Complete,Completed,Archived |
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 |
|---|---|
| list_open_tasksD | – |
| search_similar_tasksD | – |
| create_taskD | – |
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 distinct purpose: creating tasks, listing open tasks, and searching for similar tasks. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern: create_task, list_open_tasks, search_similar_tasks. No mixing of conventions.
With only 3 tools, the server is minimal. While it covers basic needs, it feels slightly thin for a task management domain, as core operations like update and delete are absent.
The server lacks fundamental CRUD operations such as update, delete, and get single task. This leaves significant gaps for any task management workflow.