Coupler.io

Query data Coupler.io imported from 400+ marketing, sales and finance platforms.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Coupler.io connector does

The Coupler.io MCP server lets Claude, ChatGPT or any MCP-compatible agent query business data Coupler.io has imported from marketing, sales and finance platforms. The agent reads a data set's schema, then runs SQL against it. Sign-in is OAuth 2.1 with a single mcp scope, and the agent sees only data flows naming that AI tool as a destination.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Coupler.io tools (4)

  • get-data
  • get-schema
  • list-dataflows
  • get-dataflow

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The directory's documentation link is dead. It names a local MCP server and 301-redirects to the docs home. No local-server article remains in Coupler.io's documentation index.
  • The directory tool list is twenty short. Coupler.io documents 24 tools; Anthropic's 2026-08-16 snapshot names four.
  • One listed tool name is not in the vendor's documentation. list-dataflows appears nowhere in Coupler.io's tool tables; list-datasets covers that job.
  • The "Read" label is falsified. Twelve documented tools create, update or run something. The read-only guarantee Coupler.io states covers the imported rows, not the workspace configuration.
  • An agent can trigger a data flow run. run-dataflow pulls fresh data from the connected platform and replaces the destination's contents. Append mode is not supported for Custom MCP.
  • get-data runs SQL. The read surface is bounded by which data sets are shared, not by the tool's shape. Every column in a shared data set is reachable.
  • Column exclusion is the customer's job. Coupler.io documents filters and column management as the way to keep sensitive fields from an AI tool, and states nothing is shared by default — but documents no automatic detection or filtering of personal data.
  • Customer-level data can appear. Sources like HubSpot and Salesforce are record systems; a flow built from a CRM object carries customer fields unless someone removed them.
  • One security claim is in tension with the tool documentation. The security page says the AI receives aggregated and processed outputs, never raw underlying data, while get-data runs SQL against imported rows.
  • Whether MCP queries consume plan quota is undocumented. Row limits are stated per run, which describes the import rather than a query.
  • Whether an agent can burn source-platform API quota unattended is undocumented. No rate limit, confirmation gate or per-day cap on agent-triggered runs is published.
  • A single OAuth scope covers everything. mcp does not separate reading from writing, so an approver cannot decline the write tools.
  • No tool annotations are published or readable. The endpoint is gated and Coupler.io ships no annotation table, so nothing is vendor-labelled read-only in machine-readable form.
  • Scoping is per AI tool. A flow shared with Claude is not shared with ChatGPT; each costs a destination slot.
  • One Coupler.io account per Claude account. Coupler.io states this is a platform limitation on Claude's side, and switching accounts requires disconnecting and reconnecting.
  • Nothing was verified past the auth gate. Tool schemas, annotations, prompts and actual permission enforcement are all documented rather than observed by us.
  • The vendor's own user count is inconsistent. Coupler.io's security page states 200K+ users in one place and 1M+ in another, on the same page.

Frequently asked questions

Does the Coupler.io MCP server only read data?

No. Anthropic's directory labels it Read and lists four read-shaped tools, but Coupler.io's documentation describes 24 tools and twelve of them write. The AI can create data flows, add sources and destinations, change a schedule, rewrite SQL and trigger a run. Coupler.io states queries against imported rows are read-only, and separately that the AI can change your configuration.

How many tools does the Coupler.io MCP server have?

Anthropic's 2026-08-16 snapshot lists four. Coupler.io's own MCP page documents 24, so the listing is twenty short. The listing is also inaccurate rather than merely incomplete: three listed names are documented, but `list-dataflows` appears nowhere in the vendor's tool tables, which document `list-datasets` for that job instead.

What does the Coupler.io get-data tool accept?

SQL. Coupler.io documents `get-data` as running a SQL query against a data set and returning the result, with the query executing on Coupler.io's side so large data sets need not fit the AI's context. That makes the read surface bounded by the data rather than by the tool: any column in a shared data set is reachable by query.

Which of my data can Claude see through Coupler.io?

Only data sets from data flows that name that specific AI tool as a destination. Coupler.io states adding Claude as a destination does not make a flow available in ChatGPT, so each tool is added separately. Coupler.io's in-app AI Agent is the exception — it sees every data set in the workspace with no destination step.

Can an AI agent trigger a Coupler.io data flow run?

Yes. Coupler.io documents `run-dataflow` as refreshing a data flow from its source, adding that the AI only does this when you ask. That is a real action, not a read: a run pulls from your connected Google Ads, HubSpot or Stripe accounts against their API quotas and replaces the destination's contents under the platform's replace mode.

Does the Coupler.io MCP server cost extra?

Coupler.io publishes no separate MCP charge, and its plans bill by accounts, destinations and refresh frequency rather than by query. The constraint that bites is destinations: each AI tool is one destination, and the Starter plan at $32 monthly allows a single one. Whether MCP queries consume plan quota is not documented anywhere we found.

Why does the Coupler.io connector documentation link go to the wrong page?

Because it points at a retired help-center article. The directory's documentation URL names a local MCP server, but it now 301-redirects to the Coupler.io docs home and no local-server article remains in the site index. The current documentation for the listed hosted endpoint lives at docs.coupler.io/ai/mcp instead.

Which Coupler.io plan do I need for the MCP connector?

Coupler.io does not gate MCP by plan in its published pricing — all four tiers list AI data analysis. The gating is on destination count and on the Claude side: Coupler.io states Claude users on a Team or Enterprise plan must have admin access to connect a new connector, so an ordinary member of a Team workspace cannot enable it alone.

Sources

  • Coupler.io MCP documentation — https://docs.coupler.io/ai/mcp.md (fetched 2026-08-19 as Markdown via the .md suffix; the canonical page is https://docs.coupler.io/ai/mcp) · retrieved 2026-08-19
  • Claude as a Coupler.io destination — https://docs.coupler.io/destinations/categories/ai/claude.md (fetched 2026-08-19) · retrieved 2026-08-19
  • Claude destination FAQ — https://docs.coupler.io/destinations/categories/ai/claude/faq.md (fetched 2026-08-19) · retrieved 2026-08-19
  • Custom MCP destination — https://docs.coupler.io/destinations/categories/ai/custom_mcp.md (fetched 2026-08-19) · retrieved 2026-08-19
  • Custom MCP FAQ — https://docs.coupler.io/destinations/categories/ai/custom_mcp/faq.md (fetched 2026-08-19) · retrieved 2026-08-19
  • Coupler.io security — https://www.coupler.io/security.md (fetched 2026-08-19) · retrieved 2026-08-19
  • Coupler.io pricing — https://www.coupler.io/pricing.md (fetched 2026-08-19) · retrieved 2026-08-19
  • Coupler.io documentation index — https://docs.coupler.io/llms.txt (fetched 2026-08-19, 205 KB). docs.coupler.io/robots.txt publishes Content-Signal: ai-train=yes, search=yes, ai-input=yes and allows all crawlers · retrieved 2026-08-19
  • Coupler.io marketing-site index — https://www.coupler.io/llms.txt (fetched 2026-08-19, 276 KB); www.coupler.io/robots.txt disallows only /tests/* and publishes no Content-Signal axes · retrieved 2026-08-19
  • Dead documentation link — https://help.coupler.io/article/592-coupler-local-mcp-server (fetched 2026-08-19; returns HTTP 301 to https://docs.coupler.io/ with the article path discarded) · retrieved 2026-08-19
  • Live anonymous probe — 2026-08-19: an initialize POST to https://mcp.coupler.io/mcp/ returns HTTP 401 with www-authenticate: Bearer error="invalid_token", scope="mcp", resource_metadata="https://mcp.coupler.io/.well-known/oauth-protected-resource/mcp". The slashless form returns the same 401 · retrieved 2026-08-19
  • Live RFC 9728 check — all three protected-resource path forms probed 2026-08-19: root, path-append and path-append-with-slash return byte-identical 205-byte JSON descriptors naming mcp; path-insert returns HTTP 401 from the MCP handler · retrieved 2026-08-19
  • Live RFC 8414 authorization-server metadata — https://auth.coupler.io/.well-known/oauth-authorization-server (fetched 2026-08-19 via a 301 from the resource host; S256 only, scopes_supported: ["mcp"], public clients). https://auth.coupler.io/.well-known/openid-configuration returns HTTP 404 · retrieved 2026-08-19
  • Anthropic connector directory — https://claude.ai/directory/dba65f24-3bd2-4d72-a86c-62b7c5290a5f (snapshot 2026-08-16) · retrieved 2026-08-16

More Sales & CRM connectors

  • Abency

    Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.

  • Actively

    Read per-account sales intelligence — agent memory, decisions, signals — from an AI agent.

  • Adobe Journey Optimizer

    Inspect campaigns, journeys and channel configurations in Adobe Journey Optimizer from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Coupler.io to work.

Connect Coupler.io once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio