things-mcp
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 |
|---|---|
| list_inboxC | To-dos in the Inbox. |
| list_today | To-dos scheduled for Today (plus overdue). |
| list_upcoming | Scheduled future to-dos (Upcoming). |
| list_anytime | To-dos in Anytime. |
| list_someday | To-dos in Someday. |
| list_logbook | Completed/canceled to-dos (Logbook). |
| list_todos | To-dos filtered by project/area/tag/status/deadline (all optional). |
| list_projects | Projects, optionally filtered by area uuid. |
| list_areas | All areas. |
| list_tags | All tag titles. |
| search | Search to-dos/projects by title and notes. |
| get_itemB | Fetch a single to-do/project/area by uuid (with checklist items). |
| list_recentC | Items created within an offset like '3d', '1w', '1y'. |
| add_todoC | Create a to-do. |
| add_projectC | Create a project, optionally pre-filled with to-dos. |
| update_todo | Update an existing to-do by id (requires Things URLs enabled). |
| update_projectC | Update an existing project by id (requires Things URLs enabled). |
| complete_todo | Mark a to-do complete. |
| cancel_todoC | Mark a to-do canceled. |
| doctorB | Preflight: DB found? readable (Full Disk Access)? Things URLs enabled? |
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 8 tools
Each tool targets a distinct aspect—list_recent for time-based retrieval, list_inbox for inbox, get_item for individual items, cancel_todo for state change, add_todo/add_project for creation, update_project for project updates, and doctor for diagnostics—no overlap in purpose.
Most tools follow a verb_noun pattern (list_recent, cancel_todo, add_todo, etc.), but 'doctor' is a noun and breaks the convention, creating a minor inconsistency.
With 8 tools, the server covers core operations for a task management system without being overwhelming; each tool serves a clear role.
Missing some lifecycle operations: no way to delete items, update to-dos beyond canceling, or list all projects explicitly. Core create/read/cancel is covered, but update and delete are limited.