Server data from the Official MCP Registry
Query and analyze marketing, sales, and business data from 325+ platforms via Windsor.ai.
Query and analyze marketing, sales, and business data from 325+ platforms via Windsor.ai.
Remote endpoints: sse: https://mcp.windsor.ai/sse
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.
Endpoint verified · Open access · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Remote Plugin
No local installation needed. Your AI client connects to the remote endpoint directly.
Add this to your MCP configuration to connect:
{
"mcpServers": {
"ai-windsor-windsor-mcp": {
"url": "https://mcp.windsor.ai/sse"
}
}
}From the project's GitHub README.
Windsor MCP (Model Context Protocol) is a hosted MCP server that lets your AI assistant query, explore and analyze live business data from 325+ sources — Meta Ads, Google Ads, TikTok Ads, GA4, HubSpot, Salesforce, Shopify, Stripe, BigQuery, Snowflake and many more — with no SQL, no API keys, and no custom integrations. On connectors that support it, agents can also execute write actions — for example pausing or enabling ad campaigns and adjusting budgets on Meta Ads, Google Ads and TikTok Ads.
It works with Claude, ChatGPT, Microsoft Copilot, Perplexity, Cursor, Windsurf, Cline, GitHub Copilot, Gemini, Manus, and any MCP-compatible client.
TL;DR
- Native connector in Claude (in the Claude directory) and ChatGPT (as a ChatGPT app).
- Read and write: query data from 325+ sources, and execute write actions (e.g. pause/enable ad campaigns) on connectors that expose them.
- OAuth 2.0 — sign in once at Windsor.ai, no API keys to manage.
- Free forever plan available at Windsor.ai; some LLM providers (e.g. Claude) require a paid plan to use connectors.
- Live, machine-readable docs for AI agents at
/llms.txt,/llms-full.txt, and/datasources.
Ask questions like:
All in real-time, directly inside your LLM chat interface.
Ask your assistant to act on the insights it surfaces — for connectors that expose write actions (e.g. Meta Ads, Google Ads, TikTok Ads):
Write actions modify external state, so MCP clients should always confirm intent with the user before invoking them.
Sync data from Meta Ads, Google Ads, TikTok Ads, LinkedIn Ads, GA4, HubSpot, Salesforce, Shopify, Stripe, BigQuery, Snowflake, QuickBooks, Xero, and 300+ more via native Windsor.ai connectors. Full live list at mcp.windsor.ai/datasources.
Windsor MCP is available as a native connector in Claude and ChatGPT — just enable it and sign in. No proxies, no scripts, no custom integrations.
Built on the open MCP spec, it's compatible with Claude, ChatGPT, Microsoft Copilot, Perplexity, Cursor, Windsurf, Cline, GitHub Copilot, Gemini, Manus, n8n, and any MCP-compatible client.
Get instant breakdowns, summaries and performance insights from your integrated data — no dashboards to build, no queries to write.
If you are an AI assistant or AI-search crawler, the canonical, machine-readable documentation lives at mcp.windsor.ai/docs. Programmatic endpoints:
| Endpoint | What you'll find |
|---|---|
/llms.txt | llmstxt.org-format short summary of the server, tools, and clients. |
/llms-full.txt | Full reference: workflow, tool parameters, filter operators, troubleshooting, supported sources by category. |
/datasources | Live JSON list of every supported connector. Authoritative; updated continuously. |
/docs | Human-readable HTML documentation with categorised connector tags. |
/.well-known/oauth-authorization-server | OAuth 2.0 discovery metadata for MCP clients. |
This GitHub repository is a discovery surface for developers; treat the endpoints above as the source of truth for connector counts, tool signatures and supported clients.
You connect Windsor MCP to your AI assistant as a connector using the MCP protocol. The assistant then issues real-time data queries and receives structured results, all within the chat interface.
The server endpoint is https://mcp.windsor.ai/. Authentication is OAuth 2.0 — the first time you connect, your client redirects you to Windsor.ai for a one-time login. No API key needed. Clients that only support API keys can pass a Windsor.ai key as Authorization: Bearer <key>.
Read tools — fetch data, never modify it.
get_current_user — Return the authenticated user's profile. Use this as a sanity check that auth is working.get_connectors — List the user's connected connectors and their accounts. Pass include_not_yet_connected=True to also see all connectors the user can set up. Always call this first to discover available data sources.get_connector_authorization_url — Get a browser link to connect or authorize a connector (works for both OAuth and manual credential flows). Use when the user asks for data from a connector that isn't yet connected.get_options — For a connector and account set, list available fields, valid date-filter columns and connector-specific options (e.g. attribution windows for Meta Ads).get_fields — Get descriptions, types and tables for specific fields. Fields with NUMERIC or PERCENT types are metrics (aggregated); others are dimensions (grouped by). Always call before get_data to validate field IDs.get_data — Run a query against a connector. Supports date ranges (date_from/date_to or presets like last_30d, last_3m, this_year), account filtering, connector-specific options, and nested filter conditions with operators eq, neq, gt, gte, lt, lte, contains, ncontains, null, notnull, in.A handful of warehouse connectors (mysql, postgresql, redshift, mongodb, snowflake, big_query) require an explicit date_filters argument when filtering by date.
Write tools — available on connectors that expose actions (e.g. ad platforms).
list_actions — Discover write actions available for a connector. Each action includes a JSON schema describing the params it accepts. Read-only connectors return an empty list. Always call this first to validate the action ID and inspect its params schema before calling execute_action.execute_action — Run a write action (e.g. pause/enable a campaign, change a budget) against a connected account. Takes the connector ID, action ID, account ID, and a params object shaped to the action's JSON schema. Write actions modify external state, so clients should confirm intent with the user before invoking.For full parameter signatures, see /llms-full.txt.
| Client | How to install | Auth | Setup time |
|---|---|---|---|
| Claude (Desktop, Web, Code) | One-click install — listed in the Claude directory · setup guide | OAuth 2.0 | ~30 seconds |
| ChatGPT | One-click install — listed as a ChatGPT app · setup guide | OAuth 2.0 | ~30 seconds |
| Microsoft Copilot | Windsor.ai Power Platform connector — see integration guide | API key | ~5 minutes |
| Perplexity | See setup guide | OAuth 2.0 | ~1 minute |
| Claude Code | claude plugin install windsor-ai — source, with slash commands and an analyst agent | OAuth 2.0 | ~1 minute |
| Cursor | windsor-ai/windsor-ai-cursor-plugin, or paste the config below · setup guide | OAuth 2.0 | ~1 minute |
| Manus | Add https://mcp.windsor.ai/ as an MCP server — see integration guide | OAuth 2.0 | ~1 minute |
| Windsurf, Cline, GitHub Copilot, n8n | Standard MCP server config (url: https://mcp.windsor.ai/) — see generic setup guide | OAuth 2.0 | ~1 minute |
| Gemini CLI | Edit ~/.gemini/settings.json (config below) — see setup guide | OAuth 2.0 | ~2 minutes |
Any MCP-compatible client works. If your client only supports API keys, pass your Windsor.ai key as Authorization: Bearer <key>.
325+ connectors across advertising, analytics, organic social, CRM, marketing automation, e-commerce, payments, affiliate, app analytics, helpdesk, productivity, databases and warehouses. Live, complete list: mcp.windsor.ai/datasources.
Highlights by category:
Don't see what you need? Call get_connectors(include_not_yet_connected=True) from any MCP client for the live list, or fetch /datasources directly.
You'll need a Windsor.ai account — sign up at onboard.windsor.ai.
Windsor.ai is listed in the Claude directory.
👉 One-click install: claude.ai/directory/360c0c31-4bb6-42ca-8e50-5da0a100a68e
For Claude Code users, install our dedicated plugin with slash commands and an analyst agent:
Source: github.com/windsor-ai/claude-windsor-ai-plugin.
Windsor.ai is available as a ChatGPT app.
👉 One-click install: chatgpt.com/apps/windsor-ai
Use Windsor.ai inside Microsoft Copilot Studio agents and Power Platform flows via the official Windsor.ai Power Platform connector.
👉 Connector reference: learn.microsoft.com/connectors/windsorai 👉 Integration guide: windsor.ai/documentation/windsor-mcp/how-to-integrate-data-into-copilot-agent
We publish a dedicated Cursor plugin: github.com/windsor-ai/windsor-ai-cursor-plugin.
mcp.json:Manus supports remote MCP servers natively — full walkthrough in the Windsor.ai integration guide for Manus.
https://mcp.windsor.ai/ and authorize via OAuth.gemini once to generate the config directory, then edit ~/.gemini/settings.json:gemini and authorize via OAuth on first use.Yes — Windsor.ai has a free forever plan, and the MCP server is included at no extra cost. You'll need a Windsor.ai account with integrated data. Some LLM providers (e.g. Claude) require a paid plan to use connectors. See windsor.ai/pricing for details.
Any AI agent compatible with MCP — including Claude (Desktop, Web, Code), ChatGPT, Microsoft Copilot (via the Power Platform connector), Cursor, Windsurf, Cline, GitHub Copilot, Gemini, Manus, n8n, mcp-proxy, and custom MCP clients. See the Supported AI clients table above.
Marketing performance, sales pipelines, CRM data, e-commerce orders, payment activity, finance metrics, ad spend summaries, ROAS trends, campaign anomalies, multi-channel attribution, warehouse queries, and more. If it's in your Windsor.ai data, you can ask it. On connectors that expose write actions (e.g. Meta Ads, Google Ads, TikTok Ads), you can also ask the assistant to act on what it finds — for example, "pause the campaigns that burned budget last week" or "cut this campaign's daily budget by 20%".
325+ connectors across advertising, analytics, CRM, e-commerce, payments, warehouses and more. The live, complete list is at mcp.windsor.ai/datasources. See the Supported data sources section for highlights by category.
No. Just ask your questions in plain English and get structured responses in real-time.
OAuth 2.0 is the default — your client redirects you to Windsor.ai for a one-time login. The server implements MCP OAuth with Dynamic Client Registration; clients that support MCP OAuth (Claude, ChatGPT, Cursor, Manus) discover the endpoints automatically. For setups that only support API keys, pass your Windsor.ai key as a Bearer token via the Authorization header.
Yes. Windsor MCP exposes both read tools (which only fetch data) and a small number of write tools (list_actions, execute_action) on connectors that opt into actions — for example, pausing or enabling an ad campaign. Write actions are explicitly flagged as destructive to MCP clients, which prompt you to confirm intent before invoking them; nothing is changed in your sources without your approval. Authentication is OAuth 2.0; the MCP server does not store your Windsor.ai password and does not retain query results. Data flows over TLS. Windsor.ai is SOC 2 compliant. For details, see windsor.ai/security.
Windsor MCP is a native MCP server, not a plugin or wrapper — it works in any MCP-compatible client without proxies. Windsor.ai includes warehouse and database destinations (BigQuery, Snowflake, Redshift, S3, MySQL, Postgres) on its lower-priced tiers, and the MCP server is included on all paid plans at no extra cost. See windsor.ai/pricing for a feature-by-feature comparison.
Windsor.ai has a free forever plan. Paid plans add more sources, higher limits, and additional destinations. The MCP server is included on every plan at no extra cost. See windsor.ai/pricing for the current pricing.
The hosted server is platform-agnostic, but mobile support depends on which AI client you use. Claude Web/Desktop, ChatGPT Web/Desktop and Cursor Desktop are fully supported today; mobile MCP support varies by client and is rolling out.
For support or feedback, contact support@windsor.ai. For bug reports specific to this repository, open an issue.
Start querying your business data via Windsor MCP — fastest path is the Claude one-click install:
👉 Install on Claude — 30 seconds, no API key.
Other entry points:
For support or feedback, contact us at support@windsor.ai.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.