Just Claude Things
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| things3_get_todosA | List todos from Things 3 with optional filters and pagination. Returns todos matching the specified criteria. Use "status" to filter by list (inbox, today, upcoming, anytime, someday, logbook). Combine with projectId, areaId, tag, or search filters to narrow results. Args:
Returns: { items: Todo[], total_available, offset, limit, has_more } |
| things3_get_todoA | Get a single todo by its ID from Things 3. Returns full details including title, notes, checklist items, due date, tags, project, and area. Args:
Returns: Todo object with all fields |
| things3_get_projectsA | List all projects in Things 3 with pagination. Returns projects with their status, area, tags, and dates. Use the returned project IDs to filter todos or assign new todos to a project. Args:
Returns: { items: Project[], total_available, offset, limit, has_more } |
| things3_get_areasA | List all areas of responsibility in Things 3. Returns area IDs, names, and tags. Use area IDs to filter todos or assign projects to an area. Returns: Array of { id, name, tags } |
| things3_get_tagsA | List all tags defined in Things 3. Returns tag IDs and names. Use tag names to filter todos or apply tags when creating/updating todos. Returns: Array of { id, name } |
| things3_create_todoA | Create a new todo in Things 3. Supports title, notes, scheduling, deadline, tags, project assignment, heading placement, and checklist items. Args:
Returns: { id, name } of the created todo |
| things3_create_projectA | Create a new project in Things 3. Args:
Returns: { id, name } of the created project |
| things3_update_todoA | Update an existing todo in Things 3 by ID. Only provided fields are updated; omitted fields are left unchanged. Note: tags specified in addTags are added to existing tags, not replaced. Args:
Returns: { success, id, name } |
| things3_complete_todoA | Mark a todo as complete in Things 3. Args:
Returns: { success, id, name } |
| things3_delete_todoA | Move a todo to the Trash in Things 3. This does NOT permanently delete it — the todo can be recovered from Trash inside Things 3. Args:
Returns: { success, id, name } |
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
Each tool targets a distinct operation on clearly separate entities (todos, projects, areas, tags). No two tools perform the same function, and the slight overlap between complete_todo and update_todo with completed=true is mitigated by the dedicated convenience tool.
All tools follow a strict `things3_<verb>_<noun>` pattern. Verbs are consistently in imperative form (create, get, update, delete, complete), and nouns are singular or plural appropriately. No mixing of styles or irregular names.
With 10 tools covering the basic lifecycle of tasks and supporting entities, the count is well-scoped for a task management MCP server. It provides enough functionality without being bloated or too sparse.
Core CRUD for todos is complete, and project/area/tag retrieval is present. However, there is no update_project, delete_project, or get_single_project endpoint, and the update_todo lacks a projectId parameter, creating minor gaps for project management workflows.