> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mcpcore.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting AI Clients

> Add your MCPCore server to any MCP-compatible AI client in under a minute.

## How connecting works

Every MCPCore server has a permanent subdomain endpoint:

```
https://your-subdomain.mcpcore.io/mcp
```

You copy the ready-to-use config snippet from the server's **Integration** tab and paste it into your AI client's config file. The client connects, discovers your tools, and is ready to use them.

***

## Supported clients

<CardGroup cols={2}>
  <Card title="Claude Desktop" icon="robot" href="/connect/claude-desktop">
    Anthropic's desktop app. Config file at `~/Library/Application Support/Claude/claude_desktop_config.json`.
  </Card>

  <Card title="Cursor" icon="code" href="/connect/cursor">
    AI-powered code editor. Direct HTTP transport — no `npx` needed.
  </Card>

  <Card title="VS Code" icon="code" href="/connect/vscode">
    Native MCP support via `.vscode/mcp.json` or User Settings.
  </Card>

  <Card title="Windsurf" icon="wind" href="/connect/windsurf">
    Codeium's AI editor. Config at `~/.codeium/windsurf/mcp_config.json`.
  </Card>

  <Card title="Cline" icon="terminal" href="/connect/cline">
    VS Code extension with MCP support. Config via the Cline extension UI.
  </Card>
</CardGroup>

***

## Config formats at a glance

Most clients use a **command-based** config that runs `mcp-remote` to bridge HTTP/SSE:

```json theme={null}
{
  "mcpServers": {
    "your-server-code": {
      "command": "npx",
      "args": ["-y", "mcp-remote@latest", "https://your-subdomain.mcpcore.io/mcp"]
    }
  }
}
```

**Cursor** and **VS Code** support native HTTP transport and don't need `npx`:

```json theme={null}
{
  "mcpServers": {
    "your-server-code": {
      "url": "https://your-subdomain.mcpcore.io/mcp"
    }
  }
}
```

***

## Auth headers by security mode

| Security mode | What to add to the config                                                                     |
| ------------- | --------------------------------------------------------------------------------------------- |
| Public        | Nothing extra                                                                                 |
| Unlisted      | Use the full URL with the embedded key                                                        |
| API Key       | Add `--header "Authorization: Bearer <key>"` (command) or `headers.Authorization` (URL-based) |
| OAuth         | Not yet supported in all clients — check client-specific docs                                 |

***

## The Integration tab

The easiest way to get the right config is to use the **Integration** tab on your server's detail page. Select your client, and the tab generates the correct snippet with your subdomain and API key pre-filled — just copy and paste.