Skip to main content
Glama
soycanopa

SupaThings MCP

by soycanopa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to SupaThings MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • 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
      4 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
      76 npm
      3
      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 37 tools

    Disambiguation2/5

    Multiple tools have unclear boundaries and overlapping purposes, such as search/search-advanced/search-items/search-todos and show/show-item, which could cause confusion and misselection. While some tools like get-inbox and get-today have distinct purposes, the significant overlap in search and display functions creates ambiguity.

    Naming Consistency3/5

    The naming follows a mostly consistent verb-noun pattern with hyphens (e.g., get-projects, update-todo), but there are deviations like json, version, and show without clear nouns, and inconsistencies such as add-project vs create-project-with-headings. The pattern is readable but mixed in style.

    Tool Count2/5

    With 37 tools, the count is too high for the apparent task management domain, suggesting bloat and potential redundancy, as seen with multiple search and get variants. This many tools can overwhelm agents and indicate poor scoping, though it's not extreme like 50+.

    Completeness4/5

    Inferred as a task/project management system, the tool set covers core CRUD operations (add, get, update, delete via trash), lifecycle aspects (log-completed, summarize-project), and advanced features like search and suggestions, with only minor gaps such as potential missing bulk operations or detailed configuration tools.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources