For agent builders
One endpoint. 226 tools. Zero OAuth plumbing.
You're building the agent, not fourteen API integrations. Point any MCP client at one URL and ship — Ducto owns the OAuth apps, token refresh, rate limits, and the write governance your customers will ask about.
Need → mechanism
What you need, and the thing that enforces it
Fourteen platforms means fourteen OAuth apps
One connect flow, vaulted tokens
Your users connect accounts by OAuth in the Ducto dashboard once. Tokens live in a KMS-envelope vault with automatic refresh — your code never touches a credential.
Big tool lists blow up context windows
Entitlement-filtered tools + per-platform mounts
The combined endpoint lists only the tools each token allows for connected platforms. Clients with small tool budgets can mount a single platform instead.
Directory reviews inspect your write behavior
Annotations on every tool
readOnlyHint, destructiveHint, idempotentHint, and openWorldHint are set on all 226 tools — the exact annotations the Claude connectors and ChatGPT apps reviews check.
Your customers will ask about safety
Server-side policy engine, inherited
Caps, preview-before-apply, approval classes, and the audit chain enforce below your agent. You get a real answer to the safety question without building any of it.
Integration
The whole integration is a URL
OAuth 2.1 for interactive clients, bearer tokens for headless. Annotations on every tool.
{ "mcpServers": { "ducto": {
"url": "https://mcp.getducto.com/",
"headers": { "Authorization": "Bearer <token>" }
} } }
✓ 226 tools across 16 platforms — filtered per token
readOnlyHint / destructiveHint set on every tool
FAQ
The questions this page raises
Which clients work?
How do tokens authenticate?
Point your agent at one URL
Free plan to build against. Read-only by default, annotations included.