Does Windsor.ai have an MCP server?
Windsor.ai maintains an official MCP server.
- Access
- Remote server
- Endpoint
- https://mcp.windsor.ai/
- Category
- Data Platforms
A remote server run by Windsor.ai itself — nothing to install. Documented at windsor.ai.
Hosted by the vendor — no install, connect over HTTP with OAuth or a token.
Add it from the terminal, then restart your session:
claude mcp add --transport http windsorai https://mcp.windsor.ai/Add --scope user to make it available in every project.
- Open Settings → Connectors
- Click Add custom connector
- Paste
https://mcp.windsor.ai/ - Finish the sign-in prompt, then enable it in the chat's tools menu
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"windsorai": {
"url": "https://mcp.windsor.ai/"
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"windsorai": {
"type": "http",
"url": "https://mcp.windsor.ai/"
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
- Enable Developer mode under Settings → Apps & Connectors → Advanced
- Choose Create and paste
https://mcp.windsor.ai/ - Complete sign-in, then enable the connector in a new chat
Does Windsor.ai have an official MCP server?
Yes. Windsor.ai maintains an official MCP server, hosted at https://mcp.windsor.ai/.
How do I connect Windsor.ai to Claude?
Add https://mcp.windsor.ai/ as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http windsor-ai https://mcp.windsor.ai/" in Claude Code.
Do I need to install anything to use the Windsor.ai MCP server?
No. It is a remote server hosted by Windsor.ai, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.
How is this verdict verified?
Published to the MCP Registry under Windsor.ai's verified namespace ai.windsor; windsor.ai's documentation gives the hosted endpoint mcp.windsor.ai (OAuth or API-key bearer), which answers MCP initialize with 401 and OAuth resource metadata (the registry's /sse path redirects to the same server). GitHub metadata is refreshed every six hours.
Published to the MCP Registry under Windsor.ai's verified namespace ai.windsor; windsor.ai's documentation gives the hosted endpoint mcp.windsor.ai (OAuth or API-key bearer), which answers MCP initialize with 401 and OAuth resource metadata (the registry's /sse path redirects to the same server).
- github data refreshed 2026-09-29, then every 6 hours
- vendor docs verified on 2026-09-29
Spotted something out of date? Tell us — corrections ship same-day.