Claude Windsor.ai connectorWhat Claude can do in your Windsor.ai account.
The Claude Windsor.ai connector exposes 5 tools. 4 of them read the marketing, analytics and sales data you already sync into Windsor.ai, 0 write, and 1 is described by no official source. Below: what Claude can query, what it cannot, and where Windsor's docs go further than the directory.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can reach your Windsor.ai data
Instead of exporting a report from each ad platform and stitching the columns together in a spreadsheet, you ask Claude a question in plain words. Through Windsor.ai, which already collects data from more than 325 sources such as Google Ads, Meta, GA4, Shopify or HubSpot, it finds the right source, checks which metrics exist, and runs the query itself.
See what is plugged in. Before anything else, Claude calls get_connectors to learn which sources and accounts you have linked in Windsor.ai, and can also show the ones you could still add.
Ask for the right numbers. With get_options and get_fields, Claude checks what a source actually offers, which columns work as date filters, and whether a field is a metric that adds up or a dimension to group by. That keeps it from requesting a figure the source does not have.
Get the answer, not an export. get_data runs the query with a date range, account filter and conditions, so a question such as spend by channel over the last three months comes back as a table Claude can comment on.
What it will not do, as listed: the directory sheet shows no tool that pauses a campaign or changes a budget, even though Windsor's own guide says otherwise (see the limits section). Nothing runs on a schedule either; Claude queries only while it answers you. For recurring reports that land somewhere on their own, look at automation platforms from the Integrations hub, which do a different job.
Five words before you connect
The vocabulary Claude uses around this connector, in one minute.
- Connector
- A link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude picks the tools it needs on its own, and the directory lists each by name.
- Authorization
- The Windsor.ai sign-in screen where you grant the access Claude will use later. Given once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes an account, shown in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Windsor.ai.
Connect Windsor.ai to Claude in three steps
- 01
Find Windsor.ai in Claude
Open Claude's settings, go to Customize then Connectors, and look up Windsor.ai in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before members can each sign in.
- 02
Start the connection
Click Connect on its row, then log in to Windsor.ai in the window that Windsor.ai opens itself. If the link breaks at some point, Disconnect and connect again to reset it.
- 03
Read the authorization screen
Check the authorization screen before you accept. It belongs to Windsor.ai, not to Claude, and it is what sets the scope of the access. You can also withdraw that access later from your Windsor.ai account.
The 5 tools, split by what they do
Windsor.ai gives Claude 5 tools: 4 that read your account, 0 that change something in it, and 1 no official source describes.
Two groups here: what Claude reads, and one name no official text explains. The directory sheet lists no writing tool. Names stay exactly as Claude shows them.
- 4 read
- 1 not documented
What Claude reads (4)
4 toolsFour tools that look up your sources and data without changing anything.
get_connectors
Returns the data sources you have linked in Windsor.ai along with their accounts. On request it also shows the sources you could still connect. Windsor asks Claude to start here before any query.
get_fields
Explains specific fields: their description, type and table. Numeric and percentage fields count as metrics that get summed, everything else as dimensions to group by. Claude runs it before a query to check the field names are valid.
get_options
For a given source and set of accounts, lists the fields on offer, the columns that accept a date filter, and settings specific to that platform, such as Meta Ads attribution windows.
get_data
Runs the actual query against a source and hands the rows back to Claude. It takes a date range or a preset period, account filters, platform options and nested filter conditions.
Undocumented (1)
1 toolThe directory publishes this name and nothing more. No official source says what it does, and we will not guess it from its name.
get_accounts
This name appears in the directory's tool list and that is all. Neither Windsor.ai's README, nor its Claude guide, nor any Claude page describes it under this name, so this page adds nothing about it.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account for someone. The prompt appears in the conversation when it matters.
On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked every time. They can also cap what a connector may do across the organization, for example keeping reading on and writing off, and that choice binds everyone. Claude works with the rights of the person who connected and nothing beyond: it sees the Windsor.ai sources your own login reaches. Windsor's guide also suggests choosing Always allow for quicker use; that trades the prompt for speed.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. Per connector, that answer is published nowhere, and it is a real hole in the catalog.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can each connect. For the live state of this one, its sheet in the official directory is the place to check. Everything specific here comes from Windsor.ai itself; no Claude help page covers this connector.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so no report goes out on its own when a campaign ends or a budget runs low.
By default, the directory sheet exposes only reading, and that is an observed floor, not a promise: an administrator can open actions that no public sheet shows. The partner badge is not a security audit, and Anthropic states on every sheet that it neither chooses the tools a publisher exposes nor guarantees they behave as announced. Connect only what comes from a publisher you trust. For a connector from another publisher with a different tool list, see the Claude airtable connector page.
Can the Claude Windsor.ai connector act on ad accounts, or only read them?
- Claude directory sheet ↗September 2026Five tools are listed, all for looking up sources, fields and data. None of them pauses, creates or edits anything.
- Windsor.ai guide for Claude ↗September 2026The publisher states its Claude connector reads and writes to connected accounts, for example to pause or launch campaigns and shift budgets.
- Windsor.ai README ↗August 2026The publisher documents two extra writing tools, one to discover actions and one to run them, and says clients should confirm intent before running them.
What this page followsNeither side is dated enough to call stale. The directory sheet, read on 30 September 2026, lists only reading tools, while Windsor.ai announces two writing tools that no Claude sheet shows. This page describes what the sheet exposes and reports the publisher's claim without endorsing it: the tool list Claude shows on your own account is what counts.
Need help connecting Windsor.ai to Claude?
A person reads every message.
