What is the key difference between Todoist V1 MCP Server and Inbox Zero?

Todoist V1 MCP Server belongs to the Workplace & Productivity category with local stdio execution, while Inbox Zero belongs to the Workplace & Productivity category with local stdio execution.

How do I install Todoist V1 MCP Server or Inbox Zero in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Todoist V1 MCP Server and Inbox Zero free or paid?

Todoist V1 MCP Server operates under a Free / Open Source model (API Key required). Inbox Zero operates under a Freemium model (OAuth 2.0).

Which MCP server has more tools and community activity?

Todoist V1 MCP Server lists 31 tools with 2 views and 1 GitHub stars. Inbox Zero lists 6 tools with 1 views and 12,270 GitHub stars.

Can I use both Todoist V1 MCP Server and Inbox Zero together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Todoist V1 MCP Server vs Inbox Zero

In-depth architectural comparison of the Todoist V1 MCP Server and Inbox Zero MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Todoist V1 MCP Server

Workplace & Productivity · Local stdio

Quality: 45/100 (Fair) | Auth: API Key required

Inbox Zero

Workplace & Productivity · Local stdio

Quality: 55/100 (Good) | Auth: OAuth 2.0

Verdict Summary: Choose Todoist V1 MCP Server if you need specialized Workplace & Productivity tools running via a local process. Choose Inbox Zero if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Todoist V1 MCP Server when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: TODOIST_API_TOKEN.
Primary tools included: todoist_get_tasks, todoist_get_task, todoist_create_task.

Explore Todoist V1 MCP Server Details

Choose Inbox Zero when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Freemium).
You have access to required keys: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, MICROSOFT_CLIENT_ID, MICROSOFT_CLIENT_SECRET, GOOGLE_BASE_URL, MICROSOFT_BASE_URL.

Feature & Specification Comparison

Specification	Todoist V1 MCP Server christulino Workplace & Productivity	Inbox Zero elie222 Workplace & Productivity
Summary	MCP server for Todoist built on the unified API v1. Stdio transport, 20 tools covering tasks, projects, sections, and labels. No daily reconnection issues.	An MCP server for Inbox Zero. Adds functionality on top of Gmail like finding out which emails you need to reply to or need to follow up on.
Category & Scope

Tools & Capabilities Breakdown

Todoist V1 MCP Server Tools (31)

todoist_get_tasks

List/filter tasks — supports Todoist filter strings like `"today"`, `"overdue"`, `"p1"`, `"#ProjectName"`, `"7 days"

todoist_get_task

Get a single task by ID

todoist_create_task

Create a task with natural language due dates (`"tomorrow"`, `"every monday"`, etc.)

todoist_update_task

Update any field; pass `clear_due_date: true` to remove a due date

todoist_complete_task

Mark a task as done

todoist_reopen_task

Reopen a completed task

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Todoist V1 MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "christulino-todoist-v1-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "christulino-todoist-v1-mcp-server"
      ],
      "env": {
        "TODOIST_API_TOKEN": "YOUR_TODOIST_API_TOKEN_HERE"
      }
    }
  }
}

Inbox Zero Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "elie222-inbox-zero": {
      "command": "npx",
      "args": [
        "-y",
        "@inbox-zero/cli"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "YOUR_GOOGLE_CLIENT_ID_HERE",
        "GOOGLE_CLIENT_SECRET": "YOUR_GOOGLE_CLIENT_SECRET_HERE",
        "MICROSOFT_CLIENT_ID": "YOUR_MICROSOFT_CLIENT_ID_HERE",
        "MICROSOFT_CLIENT_SECRET": "YOUR_MICROSOFT_CLIENT_SECRET_HERE",
        "GOOGLE_BASE_URL": "YOUR_GOOGLE_BASE_URL_HERE",
        "MICROSOFT_BASE_URL": "YOUR_MICROSOFT_BASE_URL_HERE"
      }
    }
  }
}

Frequently Asked Questions

Todoist V1 MCP Server is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Inbox Zero belongs to Workplace & Productivity using local stdio subprocess. Select Todoist V1 MCP Server when you need capabilities focused on workplace & productivity and Inbox Zero when you require tools for workplace & productivity.

More alternatives to Todoist V1 MCP Server More alternatives to Inbox Zero Workplace & Productivity category hub