Connect
Connect Cursor to Ducto
Add Ducto to Cursor's MCP config and your agent can read accounts and draft governed writes from inside the editor.
auth: OAuth 2.1 sign-in · tokens available for headless
01
Create the config
Add Ducto to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for all projects):
{ "mcpServers": {
"ducto": { "url": "https://mcp.getducto.com/" }
} }
02
Enable and sign in
Open Cursor Settings → MCP. Enable ducto and complete the sign-in when prompted — Cursor walks the OAuth flow against Ducto's consent screen.
03
Headless alternative: bearer token
Prefer a static credential? Mint a token on the dashboard's MCP page and send it as a header:
{ "mcpServers": { "ducto": {
"url": "https://mcp.getducto.com/",
"headers": { "Authorization": "Bearer <your-token>" }
} } }
04
Use it in agent mode
In a chat, ask for account work: “Which campaigns spent the most last week?” Cursor lists Ducto's tools and calls them like any other MCP server.
When it doesn't work
The two things that actually go wrong
The server shows as disabled or errored
Check the URL has no trailing spaces and that you're signed in. Cursor surfaces server logs under Settings → MCP if the handshake fails.
Cursor warns about a large tool count
Use a per-platform mount (for example /google-ads) instead of the combined root — same governance, smaller tool list.
Other clients
Any MCP client over streamable HTTP works — tell us if yours needs a guide.