Skip to main content
Windmill’s MCP server lets you interact with Windmill directly from AI coding tools like Claude Code, Claude Desktop, and Codex. Ask questions about your team, manage 1:1 agendas, check pulse results, look up feedback, and more — all from within your AI assistant.
MCP access uses your individual Windmill account. Every action exposed through MCP respects your Windmill permissions, but MCP doesn’t expose every action available in the Windmill Dashboard.
Each person connects individually in their own AI tool — follow the steps below for your tool of choice. On Claude Team and Enterprise plans, an Owner or Primary Owner must first add Windmill to the organization.

Connect with Claude Desktop

Individual Free, Pro, and Max plans

Add Windmill as a custom connector:
1

Open custom connector settings

In Claude Desktop, go to CustomizeConnectors. Click +, then select Add custom connector.
2

Enter details

Fill in the following and save:
  • Name: Windmill
  • URL: https://mcp.gowindmill.com/mcp
  • Leave OAuth Client ID and OAuth Client Secret empty
3

Connect

Click Connect next to Windmill. Your browser opens to complete sign-in.

Team and Enterprise plans

An Owner or Primary Owner must first add Windmill to the organization. Members can’t add an organization connector themselves. Once Windmill is available, go to CustomizeConnectors, find Windmill, and click Connect. Your browser opens to complete sign-in with your Windmill account.

Connect with Claude Code

Run this command in your terminal:
Or add this to your MCP configuration file:
Then run /mcp in a Claude Code session, select windmill, and authenticate.

Connect with Codex

Run these commands in your terminal:
Then authenticate:

Connect with Cursor

Add Windmill to your global Cursor MCP configuration at ~/.cursor/mcp.json:
Save the file, then complete the Windmill OAuth sign-in when Cursor prompts you.

What you can do

Once connected, you can ask your AI assistant questions and give it instructions that use your Windmill data. See Pulse Surveys for more on filtering and exporting Pulse results.

Authentication and permissions

Windmill’s MCP server uses OAuth for authentication. The first time your AI tool calls a Windmill tool, you’ll be redirected to your browser to log in with your Windmill account. Once authenticated, every action exposed through MCP runs through your Windmill account and respects its permissions. If you can’t see data in the Windmill Dashboard, you can’t access it through MCP. Having access to a Dashboard action doesn’t mean MCP exposes an equivalent action. MCP acts as the signed-in user. Windmill role-based access, org-chart scoping, connected-source permissions, and feature-specific privacy rules all apply. For example, if an Engineering manager asks an AI tool for People Team performance review results they can’t see in the Windmill Dashboard, the MCP server will not return that unauthorized data. Performance review visibility remains limited to the management chain and cycle admins. Data returned by Windmill passes through the connected AI tool’s model so the tool can generate an answer. Use AI tools that meet your company’s privacy and security requirements. Once you authorize the MCP server, the connection stays authenticated indefinitely — your AI tool refreshes its credentials silently in the background. There’s no scheduled re-authentication, unlike the Windmill Dashboard’s seven-day login window. You’ll only need to re-authenticate if you remove the MCP server, an admin revokes the connector, or your session is invalidated.

For admins: enable for your whole org (optional)

If you’re on a Claude Team or Enterprise plan, an Owner or Primary Owner can add the Windmill connector for the organization. This makes it available to members under CustomizeConnectors. Each person still authenticates individually with their own Windmill account. Members on Team and Enterprise plans can’t add an organization connector themselves. Individual Free, Pro, and Max users can follow the Claude Desktop steps above.
1

Open organization connector settings

2

Add a custom web connector

Click AddCustomWeb.
3

Enter details

Fill in the following and save:
  • Name: Windmill
  • URL: https://mcp.gowindmill.com/mcp
  • Leave OAuth Client ID and OAuth Client Secret empty

Advanced: use the Windmill plugin

On paid Claude plans, the Windmill plugin bundles the MCP connection with additional skills for managing 1:1s, creating pulses, and collecting feedback. Most users don’t need the plugin — the standard MCP connection above is enough.Claude Desktop
  1. In Claude or Claude Desktop, go to CustomizePlugins.
  2. Under Personal plugins, click +Add marketplace, then add windmill-dev/windmill-plugin from a repository.
  3. Find the Windmill plugin under Personal, click it, and click Install.
  4. Click ManageConnectorsConnect and authenticate in your browser.
Claude Code
  1. In a Claude Code session, run /plugin marketplace add windmill-dev/windmill-plugin.
  2. Run /plugin, tab to Marketplaces, select Windmill, install the plugin, then run /reload-plugins.
  3. Run /mcp, select plugin:windmill:windmill, and authenticate.

FAQs

Each person authenticates individually. On Claude Team and Enterprise plans, an Owner or Primary Owner must first add Windmill to the organization. Individual Free, Pro, and Max users can add Windmill themselves.
Every action exposed through MCP uses your Windmill account and respects its permissions. Role-based access, org-chart scoping, connected-source permissions, and feature-specific privacy rules all apply. MCP doesn’t expose every action available in the Windmill Dashboard.
When you ask a question, your AI tool calls Windmill’s MCP server to fetch the relevant data, then uses that data to answer your question. The data passes through your AI tool’s model to generate a response. Windmill’s MCP server itself does not send data to any AI model — it only responds to requests from your connected tool.
Windmill’s MCP server uses Streamable HTTP with OAuth authentication. Any compatible AI tool can connect using the URL https://mcp.gowindmill.com/mcp. The setup steps above cover Claude Desktop, Claude Code, Codex, and Cursor.
Remove the Windmill MCP server from your AI tool’s configuration. In Claude Code, run claude mcp remove windmill. In Claude Desktop, remove the connector from your Customization settings.
There’s no time-based expiry on an MCP connection. The OAuth refresh token rotates automatically in the background, so your AI tool stays connected indefinitely. You’ll only need to re-authenticate if you remove and re-add the server, revoke the connector, or are signed out by an admin. This differs from the Windmill Dashboard, where login sessions expire after about seven days.
Try removing and re-adding the MCP server, then authenticate again. Make sure you’re logging in with the same account you use to access the Windmill Dashboard.