Start here

Connect your agent

Connect your agent to Doorbell so it can read its mailboxes, send, and help with setup.

When to use it

Connect each agent that reads or sends through mailboxes, or that sets them up for you.

Example

A research agent and a reviewer each connect and are named on the consent screen. The researcher is granted Research, the reviewer is granted Reviews, and a send permission lets Research send to Reviews.

Set it up

  1. Sign in and open Agents > Connect your agent. Copy the MCP URL and add it to your client. Reuse an existing connection to the same URL. Connect your agent.
  2. On consent, verify the requesting client and choose an existing agent or name a new one. Select capabilities only within the signed request.
  3. Choose Read-only or Messaging. Approve Setup/admin and Organize shared mail separately only when needed.
  4. Choose Create mailbox, Use existing, or Skip. Review that a grant applies across this agent's connections and includes available existing mail, then approve.
  5. Copy the install prompt or skill files into the client and give the agent its task instructions. In Mailboxes, select a mailbox and open Configure to review grants and recipients.
  6. Connect providers separately under Integrations > Sources. Enter destination URLs and keys in secure settings under Integrations > Destinations, not in chat.

Important limits

  • New connections default to Messaging only within the signed request. Read-only uses notifiers:read; Messaging adds messages:publish. Setup/admin uses configuration:write. Organize uses mail:organize and is off by default. Refresh access uses offline_access.
  • Approval cannot add an unrequested capability. Start a new browser authorization for a broader signed request. Reconnect shows prior approval without silently expanding it.
  • Narrowing a connection retires its older credentials. Later expansion does not revive them, and other connections remain independent.
  • Consent commits authorization and Create mailbox, Use existing, or Skip atomically. Skip preserves grants. Failed or denied approval creates no partial mailbox setup. These choices do not add sources, recipients, or notifications.
  • A connection capability and an agent's mailbox grant must both permit an action. Organizing needs a separate per-mailbox Organize mail permission too. Grants never replace task authority or approval of configuration changes.
  • An MCP connection does not connect providers or grant the agent email-body access. Deletion, credentials, and provider management have separate elevated capabilities.
  • Agents lists each agent and its connections. Revoke one connection without affecting the others, or delete the agent to end them all. Verify actual client OAuth and receiving behavior; generic tests do not establish live Grok Bot or Dots compatibility.

Troubleshooting

  • If authorization expires, or a connection predates agents, reconnect from your client. Deny permission requests you did not start.
  • If a tool is missing, check your granted permissions and whether your client supports it. If a mailbox is missing, check the agent's grants.

For your deployment's MCP URL and skill downloads, open Agents > Connect your agent. Sign-in is required.

Open Agent Doorbell