Skip to main content
Glama

Todoist

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Todoist MCP Pack

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
47.8% over 37 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-todoist
GitHub Stars
0

TDQS

A3.8/5.0

Scored across 36 tools

Disambiguation3/5

Four universal routers (ask_pipeworx, its explicitly identical ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) plus validate_claim overlap heavily on answering factual questions, and discover_tools, suggest_questions, and pipeworx_trending overlap on capability discovery. Descriptions do a decent job of steering, but the presence of a byte-identical beta router and multiple near-duplicate answer paths creates real ambiguity. Mixing a full Pipeworx platform with five Todoist tools under a server named 'Todoist' further muddies what this server is for.

Naming Consistency3/5

Everything is snake_case, which is good, but the structural pattern is mixed: verb_noun (list_tasks, compare_entities, resolve_entity), noun-phrase/domain (entity_profile, polymarket_edges, ai_visibility_check, deep_research), single verbs (remember, forget, subscribe), and namespaced prefixes (todoist_, pipeworx_, polymarket_). Readable but no single predictable convention across the set.

Tool Count2/5

36 tools is heavy for one server and spans several distinct product surfaces (data routing, Polymarket analytics, subscriptions, memory, AI visibility, Todoist). The namesake Todoist needs only a handful, so the set is over-scoped and looks like two servers stapled together rather than a well-scoped toolset.

Completeness2/5

The Pipeworx data-routing half is broad and covers question answering, entity resolution, polymarket, and subscriptions reasonably well, but the namesake Todoist surface is read-only: it can list/get tasks, labels, projects, and sections but has no create, update, complete, or delete task operations. For a server named Todoist this is a severe lifecycle gap that will cause agent failures on basic 'add/complete a task' requests.

Tool Schema Changelog

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

  1. 1 tool update
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "when-will-bitcoin-hit-150k"
-  },
-  {
-    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
-  }
-]New value: +[
+  {
+    "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  },
+  {
+    "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
  2. 2 tool updates
    • Changedbet_research2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "market": "will-bitcoin-reach-100k-in-july-2026"
-  },
-  {
-    "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
-  }
-]New value: +[
+  {
+    "market": "when-will-bitcoin-hit-150k"
+  },
+  {
+    "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+  }
+]
      • changedInput schema / properties / market / description
        Previous value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
    • Changedpolymarket_kalshi_spread2 fields changed
      • changedInput schema / examples
        Previous value: -[
-  {
-    "topic": "fed"
-  },
-  {
-    "topic": "btc"
-  }
-]New value: +[
+  {
+    "topic": "fed"
+  },
+  {
+    "topic": "btc"
+  },
+  {
+    "topic": "bitcoin"
+  },
+  {
+    "topic": "fed rate decision"
+  }
+]
      • changedInput schema / properties / topic / description
        Previous value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."

Related MCP Connectors

Related MCP Servers

Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources