Things MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| THINGS_AUTH_TOKEN | No | Your Things auth token (required for update operations). Get it from Things → Settings → General → Enable Things URLs → Manage → Copy 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| things_add_todoA | Add a new to-do to Things with full support for checklists to break down complex tasks into manageable steps. Use checklist when task has multiple components that don't warrant a separate project. |
| things_add_projectB | Creates a project in Things with support for sections (headings) and todos. Perfect for complex projects with multiple phases, days, or categories. Headings act as visual dividers - todos that follow a heading in the items array will appear grouped under it. |
| things_get_inboxC | Get all to-dos in the Inbox |
| things_get_todayC | Get all to-dos scheduled for Today |
| things_get_upcomingB | Get all scheduled to-dos (with dates) |
| things_get_anytimeC | Get all to-dos in Anytime |
| things_get_somedayC | Get all to-dos in Someday |
| things_get_logbookC | Get all completed to-dos in the Logbook |
| things_get_trashB | Get all deleted to-dos in the Trash |
| things_get_projectsB | Get all active projects |
| things_get_areasD | Get all areas |
| things_get_tagsC | Get all tags |
| things_get_projectC | Get all to-dos in a specific project |
| things_get_areaC | Get all items in a specific area |
| things_get_listC | Get all to-dos from a specific list by name |
| things_get_todo_detailsA | Get detailed information about a specific to-do including deadline, notes, status, etc. |
| things_showC | Navigate to a specific item or list in Things |
| things_update_todoC | Update an existing to-do in Things using JSON API for full feature support |
| things_update_projectC | Update an existing project in Things using JSON API for full feature support |
| things_add_items_to_projectA | Add todos and headings to an existing project. Items are added as a flat array where headings act as visual separators for the todos that follow them. |
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 20 tools
Most tools have distinct purposes, but there is some overlap between 'things_get_anytime', 'things_get_someday', 'things_get_today', and 'things_get_upcoming' which could confuse an agent about which to use for time-based queries. The 'things_show' tool is also ambiguous as it navigates rather than retrieves data, potentially overlapping with get tools. However, descriptions help clarify specific contexts like inbox, logbook, or project-specific queries.
All tools follow a consistent 'things_verb_noun' pattern with snake_case throughout, such as 'things_add_todo', 'things_get_project', and 'things_update_todo'. This predictability makes it easy for an agent to parse and understand the tool set without confusion from mixed conventions.
With 20 tools, the count is slightly high but reasonable for a task management domain like Things, covering CRUD operations, queries across different contexts (e.g., inbox, projects, areas), and navigation. It feels comprehensive without being overly bloated, though it could be streamlined by merging some get tools.
The tool set provides complete coverage for the Things domain, including create (add_project, add_todo), read (get_* tools for various contexts), update (update_project, update_todo), and delete (implied via trash). It supports full lifecycle management of todos and projects, with no obvious gaps that would hinder agent workflows.