Windsor.ai
Marketing data integrationIndependent review. Unpaid; no partnership with Windsor.ai. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Connects marketing, CRM and warehouse data for reporting. Its MCP server is included on all plans; it can query data and perform supported account changes when write actions are enabled for the team.
The five-point review
Judgment, not a score. Documentation checked 2026-10-18.
- Value
- Connects marketing, CRM and warehouse data for reporting. Its MCP server is included on all plans; it can query data and perform supported account changes when write actions are enabled for the team.
- Differentiation
- Documented fit: Marketers combining reports across ad platforms; Teams feeding dashboards or querying connected warehouse data. Uniqueness is not established.
- Replaceability and switching
- No substitute or migration assessment recorded. Check export and switching costs.
- Ease and technical aptitude
- Consider the fit limits: Reports that require guaranteed instant freshness without checking source refresh and attribution settings. Setup effort has not been scored.
- Interoperability and portability
- See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.
Connections: MCP connections · APIs · Portability and vendor lock-in.
- Marketers combining reports across ad platforms
- Teams feeding dashboards or querying connected warehouse data
- Reports that require guaranteed instant freshness without checking source refresh and attribution settings
Top use cases
- Combine connected marketing and warehouse data for reporting source ↗
- Discover supported account actions before enabling campaign changes source ↗
In depth
Plans and refresh limits
Annual-billing monthly equivalents are Basic $19, Standard $99, Plus $249 and Professional $499; month-to-month prices are $23, $118, $299 and $598. Enterprise is quoted. The 30-day Free trial falls back to one user, source and account. MCP is included on all plans; connector, account and export frequency limits still apply. source ↗
Read and write access
OAuth is recommended, with Bearer API-key authentication also documented. MCP can query data, create calculated fields, and configure recurring exports. Supported connector actions can change campaigns or budgets; the API documentation requires write actions to be enabled in team settings. Review the specific account and proposed change before execution. Recurring export tasks can replace matching destination rows. source ↗
Verify the report scope
The API can ignore unconnected account IDs when a request also includes connected ones. Check returned account coverage, refresh timing and source-specific attribution settings before treating a report as complete. Keep API keys out of shared report URLs. source ↗
How to use it with AI
How Windsor.ai connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.
| Platform | MCP / connector | API (agent-written code) | Browser | Upload / export |
|---|---|---|---|---|
| Claude (incl. Claude Code) | Not documented Vendor documents Claude Desktop, web and Code. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Windsor.ai named integration docs ↗Claude (incl. Claude Code) MCP docs ↗ | Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands Windsor.ai publishes an API, but this pairing still needs network, authentication and execution-scope checks. Windsor.ai API ↗Claude (incl. Claude Code) docs ↗ | Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). Windsor.ai is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Windsor.ai's recorded upload/import status is to-verify; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. Claude (incl. Claude Code) file docs ↗ |
| OpenAI Codex | Not documented Windsor.ai has an official MCP server and OpenAI Codex supports MCP, but Windsor.ai's docs don't name this pairing. Auth setup may differ. Windsor.ai MCP docs ↗OpenAI Codex MCP docs ↗ | Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Windsor.ai publishes an API, but this pairing still needs network, authentication and execution-scope checks. Windsor.ai API ↗OpenAI Codex docs ↗ | Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Windsor.ai is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Windsor.ai's recorded upload/import status is to-verify; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. OpenAI Codex file docs ↗ |
| Google Antigravity | Not documented Windsor.ai has an official MCP server and Google Antigravity supports MCP, but Windsor.ai's docs don't name this pairing. Auth setup may differ. Windsor.ai MCP docs ↗Google Antigravity MCP docs ↗ | Not documented Google Antigravity: Agents edit code and run tasks Windsor.ai publishes an API, but this pairing still needs network, authentication and execution-scope checks. Windsor.ai API ↗Google Antigravity docs ↗ | Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Windsor.ai is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ | Not documented Verify which side exports and which imports, supported formats and permissions. Windsor.ai's recorded upload/import status is to-verify; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Google Antigravity file docs ↗ |
Windsor.ai's docs also name: ChatGPT, Gemini, Perplexity.
Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.
To verify Direct file upload/import was not verified; scheduled exports are a separate capability.
Agent compatibility
| Level | Status | Detail / source |
|---|---|---|
| Native connector / MCP | Yes | Official docs ↗ |
| API / CLI | Yes | Official docs ↗ |
| Browser / manual | No | Browser access is recorded alongside a documented programmatic route. |
| File upload / import | To verify | Scheduled connector exports are documented; direct file upload/import into Windsor was not verified. |
Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.
Appears in these proposed stacks
An official MCP server is documented for this tool. These platforms separately document MCP client support: ChatGPT, Claude, Cursor, Gemini (Google), Google Antigravity, Grok, Grok Bot, Lindy, LM Studio, Mistral Vibe, OpenAI Codex. This inventory does not establish compatible transport, authentication or actions for a pairing. Check the connection matrix and linked sources.
Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.
Workflows using this tool
Explained in the wiki
Review
No long-form review yet. Verdict is based on research, not hands-on testing.