Routing and destinations
MCP tool destinations
Invoke one approved remote MCP tool with reference-only Inbox notices.
When to use it
Choose a remote tool that can accept a notice under a documented handoff contract. Configure its authorization separately from the receiving agent's Doorbell connection.
Example
A notification tool accepts a mailbox reference and returns structured accepted true. Doorbell records handoff only when that approved value and any output schema match.
Set it up
- Open Integrations > Destinations and choose MCP tool. Save its public HTTPS Streamable HTTP endpoint and outbound authentication in secure website settings. Open Destinations.
- For OAuth, use a configured client or supported CIMD enrollment. Start consent and review the remote account and scopes. The callback is this deployment's /api/destinations/mcp/callback.
- Discover tools without invoking them. Review one tool's schemas, separate live and synthetic argument bindings, and explicit acceptance rule. Approve the binding on the website.
- Preview the arguments, prepare an exact synthetic invocation, and acknowledge that this real call may execute actions or wake an agent. Submit that intent once and refresh Doorbell history for its outcome.
- Require accepted handoff for the current version and no activation block. Add an Inbox trigger using the saved destination. Grant the receiving agent mailbox access separately before testing fresh matching mail.
Important limits
- Setup, credentials, consent, discovery, binding approval, previews, and synthetic submission are website-only. Public MCP exposes redacted saved destinations for selection, not remote credentials or bindings.
- Bindings allow nonsecret constants, typed $notice references, and fixed $template substitutions. Live notices carry mailbox and activity references only. Synthetic notices expose only version, type, and deliveryId. Neither grants mailbox access.
- A successful HTTP response or remote prose does not prove acceptance. Require a valid correlated MCP result, any approved output schema, and the approved structured-value or documented-success contract. Handoff is not execution.
- Only proven pre-invocation failures retry. After possible dispatch, uncertainty records acceptance_unknown and stops automatic and manual resend. Recover the same valid test intent or inspect its history instead of creating another test after a lost response.
- Pause every attached trigger before connection replacement, OAuth reconnect, or binding approval. These changes invalidate testing and pending configuration. Reconnect cannot prove the same remote principal or replay an uncertain invocation.
- Amp endpoints and recognized Puck bindings remain server-blocked for live activation, including manual generic setup and accepted tests. The preset sends to the authorized account's latest active conversation, not a dedicated thread or named agent. Production compatibility needs separate approval and implementation.
- Stdio, arbitrary scripts, tool chains, dynamic client registration, remote reply polling, and forwarding mailbox content are unsupported. A retired MCP pull queue is not an outbound destination.
Troubleshooting
- If the schema changes, pause attached triggers, discover again, review and approve a new binding, and retest. No changed schema is silently accepted.
- For unknown acceptance, correlate the delivery identity with the receiving service. Do not resend. Refreshing history reads Doorbell records without invoking the remote tool.
- If OAuth needs attention, pause attached triggers and reconnect through the website. A successful callback neither resumes triggers nor proves mailbox access.