Resources · Claude connector

Claude Coupler.io desktop extensionWhat Claude can do with your Coupler.io data in Claude Desktop.

This Claude Coupler.io connector is the desktop extension, and it exposes 4 tools. 3 read your data sets and flows, 0 write, and 1 has a name but no description. It runs only in Claude Desktop, unlike the web connector of the same name.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

Why a desktop extension of Coupler.io exists

The directory lists two Coupler.io entries. One is a web connector that follows you across Claude's apps. This one is an extension installed on your computer, and it works only in Claude Desktop. Coupler.io's documentation says local use through a desktop extension is possible, then describes the web connector in detail.

Ask about a data set from your desk. An analyst preparing a board pack asks for spend by country, and get-data runs the SQL query on Coupler.io's servers before returning only the answer.

Make sense of a table you did not build. get-schema lays out column names, types, descriptions and saved business notes, so Claude knows which field holds net revenue before it computes anything.

Spot a stale report. get-dataflow shows the sources, destinations and last run of a flow, which tells you whether this morning's numbers really are this morning's.

The limits are the publisher's: queries are read-only and cannot alter imported rows, and Claude only sees flows that list Claude as a destination. The listing adds that Coupler.io lets Claude handle large data sets without hitting conversation length limits. Nothing triggers on a schedule from Claude's side: if a figure should land in a channel every Monday, that is an automation tool's job, and the Integrations hub covers that route.

Vocabulary

Five terms, one minute

What the Claude words on this page mean.

Connector
The bridge you set up once between Claude and an account you own. This one is installed on your computer as a desktop extension.
Tool
A single named capability the connector hands to Claude. Claude decides which to call, and the directory sheet names each one.
Authorization
The service's sign-in step, where you grant Claude the access it will use. You give it once and can withdraw it later.
Approval
The yes Claude waits for before an action that would modify your account, asked inside the conversation when it arises.
MCP
The shared standard behind connectors and extensions, the piece that lets Claude exchange with an outside service like Coupler.io.
Connect

Set up the Coupler.io extension in three steps

  1. 01

    Open Claude Desktop's connectors

    In Claude Desktop, go to settings, then Customize and Connectors, and find the Coupler.io extension. Desktop extensions install on Claude Desktop only. On Team or Enterprise, an Owner or Primary Owner enables it first.

  2. 02

    Add it and sign in

    Use Connect on its entry and sign in to Coupler.io when the service asks. The sign-in belongs to Coupler.io, not Claude. If the extension stops answering, Disconnect it and set it up again.

  3. 03

    Read what access you grant

    Look over the authorization screen before you accept it, since that screen decides what the access covers. Access granted there can be withdrawn later.

Tools

The 4 tools the extension lists

Coupler.io gives Claude 4 tools: 3 that read your account, 0 that change something in it, and 1 no official source describes.

Three read and one is a bare name. The labels stay exactly as Claude Desktop shows them.

  • 3 read
  • 1 not documented

What Claude reads (3)

3 tools

These look at data sets and flows and leave them untouched.

get-data

Runs a SQL query against one data set and hands back the rows that answer it. Coupler.io does the computing, so even a very large table never has to be loaded into the chat.

When it helps
a finance lead wants last month's refunds broken down by payment method.

Sourcedocs.coupler.io · October 1, 2026 ↗

get-schema

Lays out a data set's columns with their types, descriptions and any business notes saved on them, which Claude reads before it builds a query.

When it helps
a CRM export has both a created date and a closed date, and the question is about deals won.

Sourcedocs.coupler.io · October 1, 2026 ↗

get-dataflow

Reports on one flow: where its data comes from, where it goes and when it last ran. Freshness questions get a factual answer instead of a guess.

When it helps
a weekly total jumped and you want to rule out a failed refresh first.
Watch out
on large data sets, Coupler.io reports occasional timeouts with this tool.

Sourcedocs.coupler.io · October 1, 2026 ↗

Undocumented (1)

1 tool

Only its name is published. Coupler.io's tool reference skips it, so we say nothing about what it does.

list-dataflows

No official source documents this tool: the directory gives its name and stops there, and it is absent from Coupler.io's published tool list and from every Claude page. Its effect is therefore unknown to us. Claude's general approval rule, described below, is what covers it by default.

Approvals

Confirmations and who controls them

Claude's default is to pause and ask before each action it carries out on an account for someone.

No source describes a confirmation for any specific tool of this extension, so that default is the rule to rely on. On Team and Enterprise, owners decide whether members can let certain actions run without being asked each time, and they can restrict what a connector may do across the organization; nobody lifts that from their own account. Claude acts with the rights of the person who set the extension up and nothing beyond them.

Plans

Plan availability

No official source publishes which plans include a given connector. The gap is in the catalog itself, not in our research.

The general rule is the only published one: desktop extensions install on Claude Desktop, remote connectors are open to all users across Claude's apps, and on Team and Enterprise an Owner or Primary Owner opens a connector for the organization before members use it. The extension's sheet in the official directory is the only place that shows its live state, so look there from your own account.

Limits

What the extension will not do

An extension is not an automation either. Claude calls these tools while it replies, and nothing fires when a flow refreshes overnight.

Only Coupler.io documents it, and no page of its documentation walks through installing the desktop extension. By default its sheet shows reading only, an observed floor rather than a guarantee, because an administrator can open actions that no public sheet lists. The directory badge is not a security audit, and Anthropic reminds readers on every sheet that it does not choose a publisher's tools or vouch for their behavior. For a connector from another field, see the Claude activecampaign connector.

Need help

Need help connecting Coupler.io to Claude?

A person reads every message.

FAQ

Questions about the Claude Coupler.io desktop extension

01What can Claude do with the Coupler.io desktop extension?
Claude can query the data sets your Coupler.io flows produce, from Claude Desktop on your computer. It reads a data set's columns and saved business context, runs a SQL query on Coupler.io's side and returns the answer, and reports a flow's sources, destinations and last run. A fourth tool is listed by name only. The directory describes this entry as a local extension, distinct from the web connector with the same name.
02Can Claude edit or delete data through the extension?
Not with the tools the directory lists: the three documented ones only read. Coupler.io states that queries are read-only and cannot edit, delete or overwrite the rows it imported. Its documentation mentions other tools that change flows and settings, but none of them appears on this extension's sheet. Treat the sheet as an observed floor, though, since an administrator can open actions that no public page shows. That is what the public sheet shows today.
03Will Claude ask before using the Coupler.io extension?
By default, Claude asks for confirmation before each action it takes on an account for someone. No official source describes a specific prompt for any of the four tools in this extension, so that default is the reference. On Team and Enterprise workspaces, owners can let members skip prompts for certain actions or restrict what the extension may do for the whole organization, and members cannot override that. Nobody can lift that from a personal account.
04Which Claude plans support the Coupler.io extension?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule says desktop extensions install on Claude Desktop, and that on Team and Enterprise an Owner or Primary Owner enables a connector before members can use it. The extension's sheet in the official directory is the only place that shows its current state for your account. Look it up there from your own account.
05Does the extension see everything in my Coupler.io workspace?
No. Coupler.io says Claude only reaches data sets from flows that have Claude as a destination. Adding Claude as a destination makes a flow available in Claude only, not in other AI tools. A flow sent only to a spreadsheet stays out of reach until you add Claude to its destinations. Within a Claude workspace, the extension also works with the rights of the person who installed it, never more. Nothing outside those flows is exposed.
06Should I install the extension or the web connector?
It depends on where you work with Claude. The directory marks this extension as working with Claude Desktop only, while the web connector of the same name covers Claude on the web and other surfaces. Both list the same four tools. Coupler.io's documentation is written around the web connector and only mentions the desktop extension in passing, so the web route is the better documented of the two. Pick the one that matches the app you open every day.
07The Coupler.io extension or an automation tool?
They do different jobs, so choose by use. The extension lets you question data already collected, from your desktop, the moment a question comes up. An automation tool acts without being asked, for example to post a weekly summary or alert a team when a threshold is crossed. Coupler.io's schedules keep the data fresh; acting on it at fixed times is automation work, not something this extension does. That split keeps each tool to its own trade.