obsidian-tasks-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_API_KEY | Yes | The plugin's API key. | |
| OBSIDIAN_API_URL | Yes | Base URL of the Local REST API, for example http://localhost:27123. | |
| OBSIDIAN_TASKS_DEFAULT_BOARD | No | Board (file name without .md) used when a tool call does not name one. With exactly one board in the vault it is picked automatically. |
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_boardsD | – |
| list_tasksD | – |
| get_taskD | – |
| audit_boardsD | – |
| create_taskD | – |
| move_taskD | – |
| update_subtaskD | – |
| add_subtaskD | – |
| append_logD | – |
| set_task_fieldsD | – |
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 10 tools
Most tools are distinct (create, list, get, move, audit), but update_subtask, add_subtask, and set_task_fields overlap in scope—all modify task structure or fields, and their boundaries are unclear without descriptions. append_log is also ambiguous: it could be a task update or a separate logging feature.
Tool names mostly follow a verb_noun pattern (create_task, list_tasks, get_task, move_task, audit_boards). However, set_task_fields and append_log break the pattern slightly, and update_subtask vs add_subtask are consistent but less specific than the main task verbs.
10 tools is a reasonable size for a task management server, covering core operations without bloat. The count feels appropriate, though a few tools could potentially be consolidated.
The surface covers task creation, retrieval, listing, moving, subtask management, and board auditing, but lacks obvious operations like update_task, delete_task, or complete_task. The presence of set_task_fields and append_log suggests some update capability, but the absence of a clear delete/archive operation is a notable gap.