Install and troubleshoot the ToDoddle MCP

The ToDoddle MCP requires Node.js 20 or newer. Use the configuration generated by the one-time credential dialog; keep the values in the MCP host's environment configuration rather than source control.

{
  "mcpServers": {
    "tododdle": {
      "command": "npx",
      "args": ["--yes", "--prefer-online", "tododdle-mcp@latest"],
      "env": {
        "TODODDLE_CLIENT_ID": "<client-id>",
        "TODODDLE_CLIENT_SECRET": "<client-secret>"
      }
    }
  }
}

Production TODODDLE_BASE_URL defaults to https://www.tododdle.com. Restart the MCP host after changing configuration, scopes, or grants. In Workspace Settings → Agent Connections, open Check setup, copy its read-only verification prompt, and run it from the configured agent. This proves the actual one-time credential, token exchange, scopes, project grants, and authorizing-user access together.

For local uploads, configure TODODDLE_UPLOAD_ROOTS with existing absolute staging directories (: separated on macOS/Linux and ; on Windows). Local file access is disabled without this setting. Use one root per independently operating connection and stage files under <project-id>/<run-id>/.

Common failures:

• unauthorized: confirm the client ID and secret; replace the old secret after regeneration and restart the agent.
• scope_required: enable the named capability.
• not_found for a known item: check the project grant and the creator's current access.
• permission_denied: the authorizing user cannot perform that action.
• conflict: reload and retry with the latest updatedAt.
• rate_limited: wait until the supplied reset time.
• Local path rejected: confirm it resolves inside an approved upload root.

Never paste credentials, ephemeral download URLs, or upload signatures into tasks, Notes, logs, or support messages. Rotate a secret if it may have been exposed.