Todoist connector removed from Claude, custom setup required

Todoist connector no longer available in Claude
The official Todoist connector has been removed from Claude's built-in connectors. Users who previously relied on this integration now need to set it up manually as a custom connector.
Custom connector setup steps
To add Todoist back to Claude:
- Step 1: Open Customize in Claude Desktop or on claude.ai (click Customize in the left sidebar)
- Note: You cannot use the Claude mobile app to configure connectors, but you can use the connectors on mobile after configuring them via Desktop or web
- Step 2: Click Connectors in the Customize panel
- Step 3: Click the + (plus) icon, then click Add custom connector
- Step 4: Paste the Todoist MCP URL in the URL field: https://ai.todoist.net/mcp
- Step 5: Click Add to save the connector
- Step 6: Authenticate with Todoist. The connector will appear in your list, but it's not connected yet. Click on the connector to open it. This will launch Todoist's OAuth flow in your browser, where you authorize Claude to access your Todoist account. Grant the permissions and you'll be redirected back to Claude. The connector should now show as connected
- Step 7: Test it. Start a new conversation and try something like "What tasks do I have due today?" or "Add a task to buy groceries." Claude should be able to read and write to your Todoist
Requirements and limitations
You need to be a Claude Pro or Max subscriber to add custom connectors. The setup must be done via Claude Desktop or the web interface at claude.ai - the mobile app cannot configure connectors, though configured connectors will work on mobile.
📖 Read the full source: r/ClaudeAI
👀 See Also

Four Common Setup Mistakes That Make People Quit OpenClaw
A Reddit user reports seeing over 50 people quit OpenClaw due to four specific setup issues: missing SOUL.md files, excessive API costs from using Opus model for everything, installing too many skills at once, and creating multiple agents before the first one works properly.

Mac Mini M4 Pro vs Mac Studio M4 Max for Local LLM Inference – Key Considerations
A developer compares Mac Mini M4 Pro (12C CPU/16C GPU, 273 GB/s) vs Mac Studio M4 Max (16C CPU/40C GPU, 546 GB/s), both 64GB/1TB, for local inference with Gemma 4 and Qwen. Key question: is the bandwidth jump worth $600?

Qwen 3.5 Tool Calling Fixes for Agentic Use: Server Status and Client-Side Workarounds
A detailed analysis identifies four bugs that break Qwen 3.5 tool calling in agentic setups, tracks server fixes as of April 2026, and provides a client-side Python function to parse XML tool calls when servers fail.

Methodology for Consistent Benchmarking of Local vs Cloud LLMs
A developer shares a measurement setup using sequential requests and rule-based scoring to compare local models (via llama.cpp, vLLM, Ollama) with cloud APIs (GPT-5.4, Claude Sonnet 4.6, Gemini 3.1 Pro) through a unified endpoint like ZenMux.