Google Tasks vs Coda MCP

A side-by-side look at the Google Tasks and Coda MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Google Tasks logoGoogle TasksWorkplace & Productivity · Local subprocess (stdio)Read/write Google Tasks: create, update, complete, delete, move tasks and lists, with due dates.55GoodAuth: not declaredCoda MCP logoCoda MCPWorkplace & Productivity · Local subprocess (stdio)MCP server for Coda59GoodAuth: api key required

Verdict: choose Google Tasks for workplace & productivity work as a local process; choose Coda MCP for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Google Tasks logoChoose Google Tasks when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: GOOGLE_TASKS_CLIENT_SECRET, GOOGLE_TASKS_TOKEN_PATH, GOOGLE_TASKS_OAUTH_PORT.
  • You want tools like google_tasks_list_tasklists, google_tasks_get_tasklist, google_tasks_create_tasklist.
Explore Google Tasks

Coda MCP logoChoose Coda MCP when

  • You need dedicated capabilities in the Workplace & Productivity domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: API_KEY.
  • You want tools like coda_list_documents, coda_list_pages, coda_create_page.
Explore Coda MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGoogle Tasks logoGoogle TasksCoda MCP logoCoda MCP
CategoryWorkplace & ProductivityWorkplace & Productivity
Quality signal55/100 · Good59/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredBYOK (pay the provider)
Required env varsGOOGLE_TASKS_CLIENT_SECRETGOOGLE_TASKS_TOKEN_PATHGOOGLE_TASKS_OAUTH_PORTAPI_KEY
Verified ownerCommunity listingCommunity listing
GitHub stars262
Directory activity 2 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools1419

Tools & capabilities

Google Tasks tools 14

  • google_tasks_list_tasklists
  • google_tasks_get_tasklist
  • google_tasks_create_tasklist
  • google_tasks_update_tasklist
  • google_tasks_delete_tasklist
  • google_tasks_list_tasks
  • google_tasks_get_task
  • google_tasks_create_task
  • google_tasks_update_task
  • google_tasks_complete_task
  • google_tasks_reopen_task
  • google_tasks_delete_task
  • +2 more on the listing page

Coda MCP tools 19

  • coda_list_documentsList or search available documents
  • coda_list_pagesList pages in the current document with pagination
  • coda_create_pageCreate a page in the current document
  • coda_get_page_contentGet the content of a page as markdown
  • coda_peek_pagePeek into the beginning of a page and return a limited number of lines
  • coda_replace_page_contentReplace the content of a page with new markdown content
  • coda_append_page_contentAppend new markdown content to the end of a page
  • coda_duplicate_pageDuplicate a page in the current document
  • coda_rename_pageRename a page in the current document
  • coda_resolve_linkResolve metadata given a browser link to a Coda object
  • coda_list_tablesList tables in a document
  • coda_list_columnsList columns in a table
  • +7 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Google Tasks

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "google-tasks": {
      "command": "npx",
      "args": [
        "-y",
        "-p",
        "@girmmy/google-tasks-mcp-server",
        "google-tasks-mcp-auth"
      ],
      "env": {
        "GOOGLE_TASKS_CLIENT_SECRET": "YOUR_GOOGLE_TASKS_CLIENT_SECRET_HERE",
        "GOOGLE_TASKS_TOKEN_PATH": "YOUR_GOOGLE_TASKS_TOKEN_PATH_HERE",
        "GOOGLE_TASKS_OAUTH_PORT": "YOUR_GOOGLE_TASKS_OAUTH_PORT_HERE"
      }
    }
  }
}

Coda MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "orellazi-coda-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "coda-mcp@latest"
      ],
      "env": {
        "API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

Frequently asked questions

Google Tasks is categorized under Workplace & Productivity and uses a local stdio subprocess. Coda MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Google Tasks for workplace & productivity work and Coda MCP for workplace & productivity.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Google Tasks has no declared pricing — check the project's own site. Coda MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add google-tasks and orellazi-coda-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Google Tasks has a quality signal of 55/100 (Good) with 2 views, 0 installs and 2 GitHub stars. Coda MCP has 59/100 (Good) with 3 views, 0 installs and 62 GitHub stars.