Before We Begin
Gather the following information, which you’ll need regardless of client.Name
This is just a name you want to give your MCP server. Make sure it is unique to other MCP servers you’re using, and is human readable so you can easily keep track of what each server does.
URL
For the Xano MCP Server
Each instance has its own unique connection URL. The URL can be found inside of your Instance Settings panel from the instance selection screen by clicking the icon next to the instance you want to connect to.
When creating a URL, you’ll need to choose the scope of tools the URL provides. Each client will have its own limits on how many tools can be available at once, so make sure to consult your client’s documentation for more information.For an MCP Server you built in Xano
Click the button next to the MCP server you want in the > screen.
Token
For the Xano MCP Server
The Xano MCP Server token can be found in the same place you retrieved your URL. See Generating an Access Token for more information.For an MCP Server you built in Xano
The token for a custom MCP server is generated the same way your other auth tokens are generated, usually as part of yoursignupandloginAPI logic.
Most clients authenticate to Xano MCP servers with a Bearer token sent in an
Authorization header. Clients that can’t send a header — like Claude Desktop and Claude Web — can still connect by placing a token in the URL and validating it server-side. See Clients without header support below.Claude Code
Cursor
Windsurf
Antigravity
VS Code
Raycast
Warp
Claude Desktop / Web
Claude Code
In your terminal, run the following command, replacing <name>, <url>, and <token> with your server’s details:

Cursor
Cursor supports one-click MCP server installation via install links, with your token sent as an Authorization header. Use the generator below to create yours.

Windsurf
Access your Windsurf settings
Head to Windsurf Settings > Cascade and click MCP Marketplace.Click the icon to access your
mcp_config.json file directly.
Antigravity
Access your Antigravity MCP settings
- Open the MCP store via the ”…” dropdown at the top of the editor’s agent panel.
- Click on “Manage MCP Servers”
- Click on “View raw config”
- Modify the mcp_config.json with your custom MCP server configuration.
VS Code
These instructions may work for other VS Code-based IDEs, but we recommend consulting that client’s official documentation for more specific instructions.
Per-project: Create or open .vscode/mcp.json in your workspace and add the configuration generated below.
Across multiple projects:
- Run the MCP: Open User Configuration command, which opens the
mcp.jsonfile for your user profile. Add the configuration generated below.
Raycast
Raycast connects to remote MCP servers through its built-in Install MCP Server form, which supports custom HTTP headers. Native MCP support requires Raycast 1.98 or later.
- Run the Install MCP Server command, or run Manage MCP Servers and choose Install New Server.
- Set Transport to HTTP and enter your MCP server’s URL.
- Under HTTP Headers, add a header with the key
Authorizationand the valueBearer <token>. Leave the OAuth fields empty — Xano MCP servers authenticate with a static bearer token, not OAuth. - Press ⌘ + Enter to install. Raycast connects to the server and loads its tools, which you can then @-mention in AI Chat.
Warp
- Access Warp Drive and click MCP Servers in your Personal settings.
- Click + Add and add the configuration generated below.
Clients without header support
Some MCP clients — including Claude Desktop and Claude Web — can only authenticate by putting credentials in the connection URL. Their Add custom connector flow accepts a URL but has no field for anAuthorization header, so Xano’s native, header-based MCP authentication won’t work for them.
You can still connect these clients securely: put a token in the URL and validate it yourself with an MCP server trigger.
Get your server's streaming connection URL
Retrieve the streaming connection URL for your MCP server (see Before We Begin). It looks like this, with
mcp appearing twice:https://your-instance.xano.io/x2/mcp/{server-id}/mcp/streamingPut your token in the URL
Replace the second
mcp with your token:https://your-instance.xano.io/x2/mcp/{server-id}/{token}/streamingThis is the value you paste into the client’s Add custom connector URL field. Server-side, the token is exposed as the token variable.Do not enable native authentication on your tools in Xano
Native MCP authentication expects an
Authorization header, which these clients can’t send. Leave Authentication turned off on the tools — you can enforce access with middleware or a trigger instead, so an unauthenticated client can’t reach your tools without a valid URL token.Validate the token with an MCP server trigger or middleware
Add an MCP server trigger that runs on connection and rejects anyone whose URL token isn’t valid. The token arrives on the trigger’s special
toolset object as toolset.token. If the trigger throws an accessdenied error, the connection is refused and no tools run.On a valid token, the trigger must return the toolset and tools objects — that’s what hands the available tools back to the client — so pass them through unchanged once the check passes.You can also use middleware for more precise control over the user experience, but triggers are a better option if you have a mix of tools that do and do not require auth.Please note that if a tool is not using native authentication, it will appear in the list of tools when connected to the MCP server (unless modified via a trigger). We recommend if at all possible, use headers instead.