Client Integrations # Cursor & Other IDEs AI-native IDEs like Cursor, Zed, and Windsurf all expose an MCP panel. The configuration shape is nearly identical across them: a friendly name, the Vectoralix URL, and an Authorization header for private servers. This page covers the common case for each. **IDE MCP UIs change frequently:** Each IDE owns the look and labels of its MCP settings panel; field names below describe the canonical shape, not a specific UI revision. If a label has moved, the underlying entry — name, URL, header — is the same. ## Before you start - The IDE installed and signed in. - A Vectoralix MCP server you have permission to view, with at least one published version. - The server's endpoint URL, plus the endpoint token if private. - An IDE that supports remote (HTTP) MCP servers — see the caveat at the bottom of this page if yours only supports local stdio servers. ## Cursor 1. Open the Cursor Settings panel and find the MCP section (in recent releases this lives under Features → MCP, or via a global ~/.cursor/mcp.json file). 2. Add a new server. Provide a friendly name, paste the Vectoralix endpoint URL, and add an Authorization header set to "Bearer <endpoint-token>" if the server is private. 3. Save and reload the window. The server should appear in the MCP list with a green status indicator and its tool count. If you prefer the JSON config form, the entry shape mirrors Claude Desktop's mcpServers block — keyed by friendly name, with url and a headers object carrying Authorization for private servers. ## Zed Zed registers MCP servers (called "context servers" in some Zed releases) through its main settings file. Open the command palette, run "zed: open settings", and add an entry under the appropriate context-servers or mcp\_servers key. The minimum fields are a friendly name, the URL, and Authorization for private servers — matching the same canonical shape. ## Windsurf Windsurf exposes an MCP panel inside Cascade. Open the Cascade settings, navigate to the MCP section, and add a new server entry with a friendly name, the Vectoralix URL, and the Authorization header for private servers. Reload the panel — the server's tools should appear as attachable actions. ## What to expect after connecting - Vectoralix tools surface as callable actions from the in-IDE chat. - Resources (content files exposed by the server) appear as attachable context, when the IDE supports the resources side of MCP. - Every invocation lands in the per-server request log in the Vectoralix dashboard, so you can verify the IDE actually reached the endpoint. ## Verification prompt In the IDE's chat panel, ask a question that requires a tool call — "Search my Vectoralix docs for X" for File Search, or "Run my <tool name> with these parameters" for a Code Execute or API URL tool. Confirm the assistant references the tool by name and that the call appears in the request log. ## IDEs that only support local stdio MCP Some IDEs still support only local stdio MCP servers and cannot speak Streamable HTTP directly. The pragmatic workaround is a thin local proxy: a small script built on the official MCP SDK that exposes a stdio interface to the IDE and forwards every JSON-RPC message to the Vectoralix HTTP endpoint. The Custom Clients page covers the SDK shape that this proxy uses.