Skip to main content
Glama
Just Claude Things

Just Claude Things

Just Claude Things

An MCP server that lets Claude read and write your Things 3 tasks on macOS via AppleScript.

Requirements

  • macOS

  • Things 3 installed and running

  • Node.js 18+

  • When first used, macOS will prompt you to grant Automation permissions (System Settings → Privacy & Security → Automation)

Related MCP server: Things MCP

Quick Start

Claude Desktop

Add to your ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "things3": {
      "command": "npx",
      "args": ["-y", "things3-mcp"]
    }
  }
}

Claude Code

claude mcp add things3 -- npx -y things3-mcp

Available Tools

Read

get_todos

List todos with optional filters.

{ "status": "today" }
{ "tag": "work", "status": "anytime" }
{ "search": "meeting notes" }
{ "projectId": "ABC123" }

Parameter

Type

Description

status

string

Filter by list: inbox, today, upcoming, anytime, someday, logbook

projectId

string

Filter by project ID

areaId

string

Filter by area ID

tag

string

Filter by tag name

search

string

Search todo titles and notes

get_todo

Get a single todo by ID with full details.

{ "id": "ABC123" }

get_projects

List all projects with status, area, and tags. No parameters.

get_areas

List all areas. No parameters.

get_tags

List all tags. No parameters.

Write

create_todo

Create a new todo.

{
  "title": "Review PR #42",
  "notes": "Check the error handling changes",
  "when": "today",
  "tags": ["work"],
  "checklistItems": ["Read the diff", "Run tests locally", "Leave review"]
}

Parameter

Type

Description

title

string

Required. Title of the todo

notes

string

Notes/description

when

string

today, evening, tomorrow, someday, or date (YYYY-MM-DD)

deadline

string

Deadline date (YYYY-MM-DD)

tags

string[]

Tag names to apply

projectId

string

Project ID to add this todo to

heading

string

Heading within the project

checklistItems

string[]

Checklist items

create_project

Create a new project.

{
  "title": "Q2 Planning",
  "notes": "Quarterly goals and milestones",
  "tags": ["work"],
  "when": "2025-04-01",
  "deadline": "2025-06-30"
}

Parameter

Type

Description

title

string

Required. Title of the project

notes

string

Notes/description

areaId

string

Area ID to assign to

tags

string[]

Tag names

when

string

today, evening, tomorrow, someday, or date (YYYY-MM-DD)

deadline

string

Deadline date (YYYY-MM-DD)

update_todo

Update an existing todo by ID.

{
  "id": "ABC123",
  "when": "tomorrow",
  "tags": ["urgent"]
}

Parameter

Type

Description

id

string

Required. Todo ID

title

string

New title

notes

string

New notes (appended to existing)

when

string

today, evening, tomorrow, someday, or date (YYYY-MM-DD)

deadline

string

New deadline (YYYY-MM-DD)

tags

string[]

Tags to add

complete_todo

Mark a todo as complete.

{ "id": "ABC123" }

delete_todo

Move a todo to Trash (recoverable from Things 3 Trash).

{ "id": "ABC123" }

License

MIT

Available Tools

10 tools
things3_complete_todoComplete Things 3 TodoA
Idempotent

Mark a todo as complete in Things 3.

Args:

  • id: The unique ID of the todo to complete (required)

Returns: { success, id, name }

Inputs: id (required).

things3_create_projectCreate Things 3 ProjectA

Create a new project in Things 3.

Args:

  • title: Title of the project (required)

  • notes: Markdown notes/description

  • areaId: ID of the area to assign this project to (get IDs from things3_get_areas)

  • tags: Array of tag names to apply (tags must already exist in Things 3)

  • when: Schedule — "today", "evening", "tomorrow", "someday", or YYYY-MM-DD

  • deadline: Deadline date in YYYY-MM-DD format

Returns: { id, name } of the created project

Inputs: title (required), tags, when, notes, +2 more.

things3_create_todoCreate Things 3 TodoA

Create a new todo in Things 3.

Supports title, notes, scheduling, deadline, tags, project assignment, heading placement, and checklist items.

Args:

  • title: Title of the todo (required)

  • notes: Markdown notes/description

  • when: Schedule — "today", "evening", "tomorrow", "someday", or a date (YYYY-MM-DD)

  • deadline: Deadline date in YYYY-MM-DD format

  • tags: Array of tag names to apply (tags must already exist in Things 3)

  • projectId: ID of the project to add this todo to (get IDs from things3_get_projects)

  • heading: Heading within the project to place this todo under (requires projectId)

  • checklistItems: Array of checklist item strings

Returns: { id, name } of the created todo

Inputs: title (required), tags, when, notes, +4 more.

things3_delete_todoDelete Things 3 TodoA
Destructive

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:

  • id: The unique ID of the todo to trash (required)

Returns: { success, id, name }

Inputs: id (required).

things3_get_areasList Things 3 AreasA
Read-onlyIdempotent

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 }

Inputs: no named parameters.

things3_get_projectsList Things 3 ProjectsA
Read-onlyIdempotent

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:

  • limit: Max results to return (default 50, max 200)

  • offset: Number of results to skip for pagination (default 0)

Returns: { items: Project[], total_available, offset, limit, has_more }

Inputs: limit, offset.

things3_get_tagsList Things 3 TagsA
Read-onlyIdempotent

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 }

Inputs: no named parameters.

things3_get_todoGet Things 3 TodoA
Read-onlyIdempotent

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:

  • id: The unique Things 3 todo ID

Returns: Todo object with all fields

Inputs: id (required).

things3_get_todosList Things 3 TodosA
Read-onlyIdempotent

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:

  • status: Filter by Things 3 list name

  • projectId: Filter by project ID (get IDs from things3_get_projects)

  • areaId: Filter by area ID (get IDs from things3_get_areas)

  • tag: Filter by tag name (get names from things3_get_tags)

  • search: Case-insensitive substring match against title and notes

  • limit: Max results to return (default 50, max 200)

  • offset: Number of results to skip for pagination (default 0)

Returns: { items: Todo[], total_available, offset, limit, has_more }

Inputs: tag, limit, areaId, offset, +3 more.

things3_update_todoUpdate Things 3 TodoA
Idempotent

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:

  • id: The unique ID of the todo to update (required)

  • title: New title

  • notes: New notes (replaces existing notes via URL scheme — append manually if needed)

  • when: Reschedule — "today", "evening", "tomorrow", "someday", or YYYY-MM-DD

  • deadline: New deadline in YYYY-MM-DD format

  • addTags: Tag names to add to the todo

  • completed: Set to true to mark complete, false to mark incomplete

Returns: { success, id, name }

Inputs: id (required), when, notes, title, +3 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers