Windsor.ai offers per-connector MCP servers

Windsor.ai, which moves marketing and advertising platform data into warehouses, BI tools and AI assistants, began offering per-connector MCP servers on June 19, 2026. The change lets users install only the data sources they actually use, such as Facebook Ads alone, as a separate MCP server in Claude and other large language model clients. The company's changelog says the goal is a leaner tool context inside those AI clients, with fewer unused data sources loaded.

The details

• The June 19, 2026 changelog entry lists per-connector Windsor.ai MCP servers, with Facebook Ads given as an example of a single-source install.
• On June 5, 2026, Windsor.ai launched OpenAI Ads, Readpeak and Hawk DSP connectors and added MCP budget updates for Facebook Ads and Google Ads.
• On June 26, 2026, the company added MCP write actions to create campaigns, ad sets and ads in Facebook Ads and to enable, pause and change budgets in LinkedIn Ads.
• The same June 26 entry raised the MCP request timeout to 3 minutes and added Triple Whale and Leadinfo connectors.
• A July 24, 2026 entry states that all write actions executed through Windsor.ai MCP are now recorded in an audit log.

Context

Windsor.ai publishes a weekly changelog, and the per-connector servers sit between two sets of MCP write-action releases. Earlier in June the company let AI clients change Facebook Ads and Google Ads budgets, and later in June it extended write actions to campaign creation and LinkedIn Ads controls. In July it began logging every MCP write action. The changelog also records a steady pace of new data connectors across the same weeks. In October 2026 Windsor.ai added Gemini Enterprise as a destination for its data, extending the list of AI clients it supports beyond Claude and ChatGPT.

Not disclosed

• Pricing for MCP access
• Which plans include per-connector servers