Windsor.ai

Query marketing data from 356 connected 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 Windsor.ai connector does

The Windsor.ai MCP server connects a marketing-data aggregator to Claude, ChatGPT and any MCP-compatible agent. Four of its five tools describe the surface; one, get_data, queries every field of every platform you have synced. Windsor's live connector list carries 356 sources, so the tool count measures the dispatcher, not the reach.

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.

Windsor.ai tools (5)

  • get_connectors
  • get_fields
  • get_accounts
  • get_options
  • get_data

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

Limits

  • The tool count does not measure the surface. Five tools front 356 data sources, counted from Windsor's live connector list on 2026-08-19, each with its own field catalogue. Facebook Ads alone documents 561 metrics and 150 dimensions.
  • Read-shaped names hide a write connector. All five tools begin with get_, the directory carries no permissions field, and the vendor documents pausing campaigns and changing budgets. Never infer this connector's posture from its tool names.
  • No read-only grant exists. The advertised scopes are create and delete. There is no published way to connect this server without granting write.
  • We could not verify tool behaviour ourselves. The endpoint returned HTTP 401 to an anonymous request on 2026-08-19, so no schemas and no safety annotations were readable, and Windsor publishes no tool table anywhere we could find.
  • The write tools are unaccounted for. Windsor markets actions with no matching tool name in the directory snapshot. Either an argument carries them or the listing is incomplete; we could not tell without authenticating.
  • Field selection is not yours to make. Windsor states all available fields are sent, so you cannot narrow what the agent sees except by choosing which sources to sync.
  • Customer-level data is not ruled out. Windsor's source list includes CRM, helpdesk, payment and lead-form connectors whose records concern individuals. No Windsor page states whether the MCP path filters them.
  • Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, and the gated endpoint blocked our own prompts/list.
  • Rate limits are shared with the API. 600 requests per minute and 10,000 per day, returning HTTP 429 with quota and reset headers. Windsor publishes no separate MCP quota, so agent traffic competes with your pipelines.
  • The free plan sees only 30 days. Windsor documents a 30-day history limit on the Free plan, one data source and one account after the first 30 days.
  • Windsor's own sources disagree on plan gating. Its docs index describes MCP as available on every paid plan from $19/month; its MCP FAQ and pricing FAQ say the free plan includes it, writes included. Both were fetched 2026-08-19; the FAQ pages are the more specific claim.
  • The listed documentation URL is a blog post. Anthropic's directory points at /introducing-windsor-mcp/, which is thinner than the docs site Windsor also runs. We used both and say which claim came from which.

Frequently asked questions

How many data sources can the Windsor.ai MCP server reach?

356, counted directly from Windsor's own machine-readable connector list on 2026-08-19. That endpoint returns one identifier per source, covering Google Ads, Facebook Ads, GA4, TikTok, LinkedIn, HubSpot, Salesforce, Shopify, Stripe and hundreds more. Windsor's marketing pages say 350-plus and its docs index says 339, so the live list is the figure to trust.

Is the Windsor.ai connector read-only?

No, despite all five tool names starting with get. Windsor's own Claude setup guide states the connector reads and writes to your connected accounts, and lists pausing campaigns, reallocating budgets and pushing negative keywords as things you do from the chat. The server's OAuth descriptor advertises exactly two scopes, create and delete, both write-shaped.

Does Windsor.ai MCP cost anything to use?

No, it works on the free-forever plan. Windsor's own MCP FAQ says the server is available with no credit card required, and its pricing FAQ says read and write functions including pausing campaigns are available on every plan. Windsor's docs index disagrees, describing MCP as a paid-plan feature. Nothing is metered per query.

What data can Windsor.ai read from my ad accounts?

Every field of every source you connect, without a field-selection step. Windsor's Claude guide states you do not choose fields manually because all available fields are sent. For Facebook Ads alone Windsor publishes 561 metrics and 150 dimensions, including age, gender, region and country breakdowns. Windsor does not publish which of the 356 sources carry customer-level records.

What rate limits apply to Windsor.ai MCP queries?

Windsor publishes 600 requests per minute and 10,000 requests per day, returning HTTP 429 with headers naming your remaining quota and reset time. Those are documented as API limits on the pricing page rather than MCP-specific ones, and Windsor publishes no separate MCP quota. The free plan additionally caps data retrieval to the past 30 days.

Do you need a Windsor.ai admin to add the connector in Claude?

Only inside a managed workspace. Windsor's Claude setup guide notes that corporate environments require you to request access from an administrator. On a personal account you install it yourself from the Claude connectors directory and complete the Windsor sign-in. One data source must already be synced to your Windsor account before the connector returns anything.

Sources

  • Windsor MCP announcement — https://windsor.ai/introducing-windsor-mcp/ (fetched 2026-08-19; this is the documentation URL Anthropic's directory publishes, minus its #method-1-using-claude-desktop-3 fragment. It is a blog post, not a docs page, and names no tools) · retrieved 2026-08-19
  • Windsor MCP product page — https://windsor.ai/destinations/windsor-mcp-for-ai-insights/ (fetched 2026-08-19; campaign pause/enable feature claim, MCP FAQ including free-plan availability) · retrieved 2026-08-19
  • Windsor Claude setup guide — https://windsor.ai/documentation/windsor-mcp/how-to-integrate-data-into-claude/ (fetched 2026-08-19; prerequisites, "reads and writes", all-fields-sent statement, admin requirement) · retrieved 2026-08-19
  • Windsor docs machine index — https://windsor.ai/llms.txt (fetched 2026-08-19; 339-connector figure, 561 metrics/150 dimensions for Facebook Ads, REST API parameters, security and compliance summary) · retrieved 2026-08-19
  • Windsor live connector list — https://connectors.windsor.ai/list_connectors (fetched 2026-08-19; 356 identifiers, the count used on this page) · retrieved 2026-08-19
  • Windsor pricing — https://windsor.ai/pricing/ (fetched 2026-08-19; 600 req/min and 10,000 req/day limits, 30-day Free-plan history limit, and the FAQ stating read and write functions are on every plan) · retrieved 2026-08-19
  • Windsor documentation index — https://windsor.ai/documentation/ (fetched 2026-08-19; used to find the MCP section the blog post does not link directly) · retrieved 2026-08-19
  • windsor.ai/robots.txt allows the pages used here — it disallows /ppc/, /forum/, /wp-admin, query strings and feeds only — and carries no Content-Signal header on any axis (fetched 2026-08-19). Sitemap declared at https://windsor.ai/sitemap_index.xml · retrieved 2026-08-19
  • Live RFC 9728 protected-resource descriptor — https://mcp.windsor.ai/.well-known/oauth-protected-resource (fetched 2026-08-19; scopes_supported = ["create","delete"]. The path-append form is the same URL because the endpoint has no path; both /mcp/.well-known/… and /.well-known/…/mcp return 404) · retrieved 2026-08-19
  • Live RFC 8414 authorization-server metadata — https://mcp.windsor.ai/.well-known/oauth-authorization-server (fetched 2026-08-19; issuer https://mcp.windsor.ai/, PKCE S256, dynamic registration. openid-configuration returns 404) · retrieved 2026-08-19
  • Live anonymous probe — 2026-08-19: POST to https://mcp.windsor.ai returns HTTP 401 {"error": "invalid_token"} with www-authenticate: Bearer … resource_metadata="…" · retrieved 2026-08-19
  • Anthropic connector directory — https://claude.ai/directory/360c0c31-4bb6-42ca-8e50-5da0a100a68e (snapshot 2026-08-16; five tool names, no permissions field, no prompt names) · 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 Windsor.ai to work.

Connect Windsor.ai 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