Donezo Inbox docs

Start here

• Press ? in Donezo for the live shortcut sheet. Press ⌘K on Mac or Ctrl+K on Windows to search commands by name.
• Shortcuts are on by default. Keys that type letters work when focus is outside a draft, search field or other text box. Press Esc to leave one.
• The table shows Mac keys. On Windows and Linux, use Ctrl in place of ⌘. Some keys only work in a conversation, list, calendar or draft.
• By default, shortcuts follow the letters printed on your keyboard. Settings → General → Keyboard can switch to QWERTY key positions.

On mobile touchscreens, use the on-screen controls. These shortcuts require a hardware keyboard.

Keyboard shortcuts

The reference below is generated from Donezo's keyboard binding table. Where a key has several jobs, its current context decides which one runs; for example, R opens a conversation in a list and replies inside one.

The account shortcuts switch between accounts 1–9. ⌘1–9 is reserved for browser tabs on the web; use the Ctrl variant there. Calendar editing shortcuts need calendar edit access.

Connect an AI agent

Use Donezo's remote MCP server at https://donezoinbox.com/mcp. Add it inside the agent's MCP or connector setup. Opening that address in a normal browser returns an expected 401; it is not a sign-in page. The agent's MCP client starts OAuth, after which you select inboxes and a permission level in Donezo.

1. Choose your agent below and add the server.
2. Complete browser sign-in yourself. Start with Read only and select only the inboxes that agent needs.
3. Ask the agent to call list_accounts to check the connection. This does not read messages.
4. Manage or revoke access later in Donezo → Settings → AI Agents.

Connect my Donezo Inbox. Read https://donezoinbox.com/agents.md and follow the setup for this client. Let me complete sign-in and choose Read only and the inboxes to share. Then call list_accounts to verify. Do not read, change or send email.

Claude and Claude Code

In Claude web or desktop, open Customize → Connectors → Add → Custom → Web, name it Donezo, enter https://donezoinbox.com/mcp, choose sign-in, then authorize in your browser. Claude's connector instructions describe the current menus.

claude mcp add --transport http --scope user donezo https://donezoinbox.com/mcp
claude mcp login donezo

Claude web and Claude Code use different setup screens. A live Donezo sign-in on Claude has not been verified in this docs update.

Codex

Add the remote server in Codex CLI or desktop; both use the same MCP configuration. Complete the browser sign-in when prompted.

codex mcp add donezo --url https://donezoinbox.com/mcp
codex mcp login donezo
codex mcp list

OpenAI’s Codex MCP instructions show the same CLI setup pattern. A successful Donezo connection should expose list_accounts.

ChatGPT

On ChatGPT web, open Plugins → Add custom MCP server. Enter a name and https://donezoinbox.com/mcp as the Server URL, then use OAuth sign-in. Workspace settings can affect availability. OpenAI's setup guide has the current screen.

A Donezo connection in ChatGPT was verified on 21 October 2026. Your workspace may show different menus or permissions.

Grok, Grok Bot and Grok Build

For Grok, open grok.com/connectors → New Connector → Custom, enter https://donezoinbox.com/mcp, and sign in. Grok's connector guide describes the flow. A Grok Business team may need its admin to add the server first.

For Grok Bot, ask it to add Donezo as a Remote HTTPS MCP plugin with https://donezoinbox.com/mcp and to pause for your OAuth sign-in and Read only choice. A real Grok Bot connection has worked; do not give a shared bot a personal script key.

grok mcp add --transport http donezo https://donezoinbox.com/mcp
grok mcp doctor donezo

Grok's custom connector is documented, while a Donezo sign-in on Grok and Grok Build has not yet been verified.

Meta Muse

Muse's custom connector flow needs a client ID supplied in advance. Donezo provides the public client ID donezo-muse for Muse's OAuth sign-in; it has no client secret. Start by asking Muse to build a custom connector, as Meta's Muse connector help describes.

Create a custom remote Streamable HTTP MCP connector for Donezo Inbox at https://donezoinbox.com/mcp. Use OAuth with the pre-registered public client ID donezo-muse; there is no client secret. Pause for me to sign in to Donezo and choose Read only and my inboxes. Then call list_accounts. Do not read, change or send mail. If you cannot start OAuth, tell me the exact error and redirect host; do not ask for a key in chat.

If Muse offers only a Secure Credentials Store form and OAuth still fails, you can use a dedicated key: in Donezo → Settings → AI Agents → Keys for scripts (advanced), choose Read only, the inboxes and an expiry, then Create key. Enter it only in Muse's Secure Credentials Store and tell Muse to send it as Authorization: Bearer <key> to the MCP address. Never paste the key into chat or the URL. Revoke it in Donezo when finished.

The OAuth path passes Donezo's local end-to-end check, but a live Muse sign-in is still unverified. Muse's generic “Something went wrong” screen does not identify whether Muse contacted Donezo. If either route fails, send the exact error and the step where it stopped to Donezo support.

Troubleshooting

• A plain browser visit to /mcp shows 401: add it through your agent's MCP connection screen instead.
• If a key does nothing, press Esc, click the message list, then try again. If the cursor is in the draft, letter keys type text.
• If OAuth says a redirect address is not accepted, send the exact redirect host to Donezo support. Do not put a token in the URL or paste it into chat.
• If list_accounts is unavailable, check that the connector is enabled for the current conversation and that browser sign-in finished.
• For scripted integrations, create a key in Settings → AI Agents and send it only as an Authorization header; browser sign-in is easier for a person.

Need help? Contact support with your client name, the exact error and what step failed. Never send a password or access token.