Skip to main content
Glama
jimfilippou

things-mcp

by jimfilippou
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to things-mcp

No user-submitted related servers found.

    Related Servers

    • Things MCP

      lucas-flatwhite
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for Things 3 on macOS that enables AI assistants to create, read, update, and manage tasks and projects. It utilizes the Things URL scheme for write operations and AppleScript for querying data from the app.
      15
      7 npm
      2
      MIT

    • Things MCP Server

      wbopan
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that allows AI assistants like Claude Code, Claude Desktop, and Cursor to interact with Things.app on macOS, enabling task creation, updates, viewing, scheduling, and organization through natural language.
      6
      16 npm
      3
      MIT

    • things-mcp

      than
      A
      license
      B
      quality
      A
      maintenance
      An MCP server for Things 3 on macOS that enables reading and writing tasks, projects, and more via Claude, using read-only SQLite and the official Things URL scheme.
      20
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    D1.5/5.0

    Scored across 8 tools

    Disambiguation2/5

    Several tools have ambiguous purposes: 'update' could apply to todos or projects, while 'show' and 'search' lack clear targets. 'add-todo' and 'add-project' are distinct, but the vague verbs make selection risky.

    Naming Consistency2/5

    Naming patterns are inconsistent: some tools follow verb_noun (add-todo, add-project, update-project), but 'update', 'show', 'search' are bare verbs, and 'version' and 'json' are nouns. This mix makes it hard to predict tool names.

    Tool Count4/5

    With 8 tools, the count is within a reasonable range and not overly heavy or thin. However, the inclusion of utility tools like 'version' and 'json' suggests some bloat relative to the apparent task-management domain.

    Completeness2/5

    The tool surface lacks essential operations such as delete or remove for todos and projects, and 'update' is too generic to cover specific update scenarios. The 'json' and 'version' tools do not contribute to domain coverage, leaving obvious gaps in lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources