Client Integrations

Overview

An MCP client is any AI tool that speaks the Model Context Protocol — Claude Desktop, Claude Code, Cursor, Zed, Windsurf, and custom applications built on the official MCP SDKs. Vectoralix does not ship its own client; it exposes every MCP server as a Streamable HTTP endpoint that any compliant client can attach to.

What an MCP client is

A client is the AI tool on your side of the connection: it speaks JSON-RPC over the Model Context Protocol, lists the server's tools and resources, and invokes them on the model's behalf. Vectoralix is the server. Any client compliant with MCP's Streamable HTTP transport can attach to a Vectoralix endpoint without a custom plugin.

  • Claude Desktop — Anthropic's desktop app on macOS and Windows.
  • Claude Code — Anthropic's CLI assistant for project-scoped coding.
  • Cursor, Zed, Windsurf — AI-native IDEs with built-in MCP panels.
  • Custom clients — anything you build on the official @modelcontextprotocol/sdk (TypeScript) or mcp (Python) packages.

The Vectoralix MCP endpoint

Every MCP server you create is reachable at one canonical URL. The transport is Streamable HTTP — POST carries client-to-server JSON-RPC messages, GET opens an SSE stream for server-pushed events, and DELETE closes a session.

POST https://vectoralix.com/mcp/<serverUid>
  • serverUid is a stable, opaque identifier shown on the MCP server detail page.
  • The URL is the same whether the server is public or private — visibility is enforced server-side, not via separate hosts.
  • Version selection is server-side: the active version is served by default, with no version pin in the URL.

Where to copy the URL and token from

Open the MCP server you want to expose in the Vectoralix dashboard. The Connection panel shows the full endpoint URL with a copy-to-clipboard button. For private servers, the same panel exposes the endpoint token (a 64-character random string) — copy that and send it on every request as Authorization: Bearer <token>.

Public vs private auth, side by side

Server visibility Authorization header Endpoint behavior
Public None required Anonymous calls accepted; unknown serverUid returns 404.
Private Authorization: Bearer <endpoint-token> Wrong token, missing token, and unknown serverUid all return 401 to avoid UID enumeration.

Pick your client

I use… Go to
Claude Desktop on macOS or Windows Claude Desktop
Claude Code in a project directory Claude Code
Cursor, Zed, Windsurf, or another AI-native IDE Cursor & Other IDEs
a custom chatbot, agent, or CLI built on an MCP SDK Custom Clients (SDK)

Version selection is invisible to clients

You do not pin a version in the URL. The endpoint resolves the active version at request time, falls back to the default version when no active is set, and returns an error if neither exists. From the client's perspective, the server's tools and resources are simply what is live right now.

Common pitfalls

  • Wrong serverUid — the URL must end with the exact UID from the dashboard. Private servers return 401 (not 404) for unknown UIDs, so a typo looks like an auth failure.
  • Missing /mcp/ prefix — the endpoint is /mcp/<uid>, not /<uid>. Hitting the host root will not initialize an MCP session.
  • Public-vs-private mismatch — sending an Authorization header to a public server is harmless; omitting it from a private server returns 401.
  • Rate-limit 429s — every plan has a per-server monthly quota; the response includes the standard rate-limit headers so the client can back off.

Verify before you wire it up: Run the server through the in-dashboard Playground first. If the Playground sees the tools, every external client will too — anything that fails after that is configuration, not protocol.