# Connect Donezo Inbox to this AI agent

Official human guide: https://donezoinbox.com/docs/#agents
Remote MCP endpoint: `https://donezoinbox.com/mcp` (Streamable HTTP)

If a person asks you to connect Donezo:

1. Identify which agent/client you are running in. Ask before changing its user-level MCP configuration. Do not edit a project's shared MCP configuration for a personal mailbox.
2. Use that client's supported remote HTTP MCP setup below. If the client has no supported setup API or CLI, give the person the endpoint and guide them through its custom MCP screen. Do not claim to have connected until the client reports success.
   Do not open the MCP URL as an ordinary web page to test it: without a credential it correctly returns HTTP 401. An MCP client reads the `WWW-Authenticate` header and OAuth resource metadata to start sign-in.
3. Let the person complete the Donezo browser sign-in and choose inboxes and permissions. Never ask for a Donezo password, OAuth code, access token, or script key in chat. Never place a key in the URL or repository.
4. Verify by calling the `list_accounts` tool, if the client exposes it. Report the account count and the permission level, but do not read messages as a setup test. If the tool is unavailable, explain what remains unverified.
5. Suggest this first request: “Using Donezo, list the messages that need my attention today. Show the inbox, sender and subject. Do not change or send anything.”

## Client setup

- **Codex CLI / desktop:** `codex mcp add donezo --url https://donezoinbox.com/mcp` then `codex mcp login donezo`. The CLI and desktop share MCP configuration. Check `codex mcp --help` if your version differs.
- **Claude Code:** `claude mcp add --transport http --scope user donezo https://donezoinbox.com/mcp` then `claude mcp login donezo`, or authenticate through `/mcp` inside Claude Code. Check `claude mcp add --help` if your version differs.
- **Grok Build:** `grok mcp add --transport http donezo https://donezoinbox.com/mcp`. On first use, authenticate in the browser. `grok mcp doctor donezo` checks configuration and connectivity. A live Donezo OAuth login with Grok Build has not yet been verified.
- **Cursor:** Customize → MCPs → add a remote HTTP server named `donezo` with URL `https://donezoinbox.com/mcp`. For a personal configuration, use `~/.cursor/mcp.json`, not a repository file. A live Donezo OAuth login with Cursor has not yet been verified.
- **ChatGPT:** Plugins → Add custom MCP server; enter `https://donezoinbox.com/mcp` and choose OAuth. A real ChatGPT account connected successfully on 21 October 2026; menu names may change.
- **Claude web / desktop:** Customize → Connectors → Add custom connector; enter `https://donezoinbox.com/mcp`, then Connect. A real Claude connection has not been documented in Donezo's test record.
- **Grok:** `https://grok.com/connectors` → New Connector → Custom → enter the MCP URL. A Grok Business admin may need to provision it. A live Donezo OAuth login has not yet been verified.
- **Meta Muse:** ask Muse to create a custom remote Streamable HTTP MCP connector at the endpoint above. Its pre-registered public OAuth client ID is `donezo-muse` (no secret). Pause for the person to complete Donezo sign-in and choose Read only and inboxes, then call `list_accounts`. If Muse cannot start OAuth, guide the person to create a dedicated Read only key under Donezo → Settings → AI Agents → Keys for scripts (advanced), with selected inboxes and expiry. The person enters that key in Muse's Secure Credentials Store, never in chat; Muse sends it as `Authorization: Bearer <key>`. Meta's guide: https://www.meta.com/help/superintelligence/1687253048996149/. Donezo's OAuth path passes local tests, but a live Muse sign-in remains unverified.
- **Grok Bot:** add a custom Remote HTTPS MCP plugin. For a shared bot, prefer each person's OAuth sign-in over one bot-wide script key. A live Donezo connection has worked.

For hosted clients whose OAuth redirect host is not yet on Donezo's allowlist, setup may stop at registration with a “redirect address is not accepted” error. Report the exact host to Donezo support. Do not bypass this by putting credentials in a URL or using a shared bot key.

Donezo's consent defaults to a level that requires approval for sensitive changes, and lets the person restrict the connection to chosen inboxes. Connections can be changed or revoked in Settings → AI Agents. The MCP endpoint requires an authorized user; simply adding the URL does not grant access.