The intended order is discover, inspect, then query — connectors, then fields to validate the ids, then the data — which is what stops a query failing on a field name the model invented. The write path is deliberately separate and narrow: the action list tells you exactly what a connector will accept, with a schema, before anything executes, and a read-only connector answers with an empty list rather than a plausible-looking error.
A hosted server from Windsor.ai fronting its connector catalogue — ad platforms, analytics, CRM, e-commerce, payments, databases and warehouses. Discover which sources a user has connected, inspect their fields, run queries, and on connectors that expose them, execute write actions. It is listed as a native connector in the Claude and ChatGPT directories, so on those clients it is an enable-and-sign-in job.
- get_connectors lists the sources this user has connected and their accounts, and can also show the ones they could still set up — the call to make first.
- get_options returns the fields, valid date-filter columns and connector-specific options such as attribution windows, and get_fields returns descriptions, types and tables so metrics and dimensions can be told apart before a query is written.
- get_data runs the query, with date ranges or presets, account filtering, and nested filter conditions across the usual comparison, containment and null operators.
- list_actions returns the write actions a connector exposes, each with a schema for its parameters — a read-only connector returns an empty list — and execute_action runs one against a connected account.
- Write actions exist today on the ad platforms, Instagram, Google Business Profile, Klaviyo, Salesforce, Amazon and WordPress: pausing and enabling campaigns, changing budgets and bidding, adding negative keywords, replying to reviews, publishing posts, setting a flow live.
- get_connector_authorization_url and get_connector_connect_info handle a source that is not connected yet, including the credential fields a manual connector needs — without connecting anything.
- Scheduled exports from chat: get_destinations lists what can receive data, get_destination_setup_info returns the requirements and allowed schedules, create_destination_task sets up the recurring export, and get_destination_tasks lists what is already running.
- get_current_user is the quick check that authentication works, and get_windsor_login_url, get_subscription_url and contact_windsor cover account errands without leaving the conversation.
A Windsor.ai account, authorised over OAuth on the first connection — nothing to install and no key to manage, though a client that only supports API keys can send a Windsor key as a bearer token. There is a free-forever Windsor plan, but some AI providers require their own paid plan before you can use connectors at all. Write actions change external state, and the documentation expects the client to confirm intent with the user before invoking one. A handful of warehouse connectors need an explicit date-filter argument when you filter by date.
One command plus a key — claude plugin install windsor-ai, then supply credentials