Things MCP 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": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_todoB | Create a new to-do item in Things.app. Add notes, tags, checklist items, and assign to projects or areas. |
| add_projectA | Create a new project in Things.app. Add notes, tags, assign to areas, and pre-populate with initial to-dos. |
| update_todoB | Update an existing to-do item in Things.app. Modify title, notes, scheduling, tags, checklist items, project/area assignment, and completion status. |
| update_projectA | Update an existing project in Things.app. Modify title, notes, scheduling, tags, area assignment, and completion status. |
| things_summaryA | Generate a summary of your Things database with filtering options. Returns formatted Markdown or structured JSON data for tasks, projects, areas, and tags. |
| export_jsonA | Export complete Things database as structured JSON for debugging, backup, or data processing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server-info |
TDQS
Scored across 6 tools
Each tool has a clear and distinct purpose: adding projects/todos, updating them, exporting data, and generating summaries. There is no overlap or ambiguity between these actions.
All tools follow a consistent verb_noun pattern using snake_case (e.g., add_project, update_todo, export_json). The naming is predictable and uniform across the entire set.
With 6 tools, the server is well-scoped for a personal task management system. It covers core CRUD (without delete) for projects and todos, plus export and summary utilities—each tool earns its place.
The tool set covers creation, retrieval (via summary and export), and update for projects and todos, but missing delete operations for both. Additionally, there are no dedicated tools for managing areas or tags independently, which limits lifecycle coverage.