tasks-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASK_DATABASE | Yes | Notion tasks database ID | |
| API_AUTH_TOKEN | Yes | API auth token | |
| COURSE_DATABASE | Yes | Notion courses database ID | |
| PROJECT_DATABASE | Yes | Notion projects database ID | |
| NOTION_AUTH_TOKEN | Yes | Notion integration token |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-tasksC | Fetches tasks from my Notion based on filtering criteria |
| create-taskC | Creates a new task in my Notion Tasks 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 2 tools
The two tools have clearly distinct purposes: get-tasks retrieves/filters tasks, while create-task creates a new task. There is no overlap or ambiguity in selecting between them.
Both names follow a consistent verb-noun hyphenated pattern (get-tasks, create-task). The only minor inconsistency is plural 'tasks' in get-tasks versus singular 'task' in create-task.
Two tools is thin for a task management server, even if the scope is limited to fetching and creating tasks. It is usable but lacks the breadth expected for the domain.
The surface covers creating and retrieving tasks, but lacks update, delete, complete, or status-change operations. These are notable gaps for a task management lifecycle.