Connecting Your IDE
Create a cn-live-* personal access key, add the Clevername MCP gateway URL to your IDE with the key as a bearer header, and start using your tools.
IDE Gateway
The Clevername IDE Gateway is a single HTTP endpoint that any MCP-compatible client can connect to. It gives your IDE access to all your configured MCP tools, provider keys, and governance policies — the same ones you use in the browser. One endpoint, every tool.
Authenticate with a personal access key
Every MCP client authenticates with a cn-live-* personal access key, sent as Authorization: Bearer cn-live-…. Create one at Settings → Keys → Personal Access Keys. OAuth sign-in for MCP clients is coming.
Supported clients
- Claude Code (Anthropic CLI)
- VS Code with the MCP extension
- Cursor
- Any client that supports the MCP HTTP transport
Create a key and note the gateway URL
Create a personal access key at Settings → Keys → Personal Access Keys. It starts with cn-live- and is shown once, so copy it. Every client below uses:
URL: https://clevername.net/api/hub/mcp/gateway Header: Authorization: Bearer cn-live-YOUR_KEY
Configure Claude Code
The quickest way is one command in your terminal:
export CLEVERNAME_API_KEY=cn-live-YOUR_KEY
claude mcp add-json clevername-mcp --scope user '{
"type": "http",
"url": "https://clevername.net/api/hub/mcp/gateway",
"headers": { "Authorization": "Bearer ${CLEVERNAME_API_KEY}" }
}'The single quotes keep ${CLEVERNAME_API_KEY} a reference: Claude Code reads the key from your environment each time it connects, so the key is never stored in its config. Put the export line in your shell profile so every terminal has it. Passing the key itself with --header would store it in ~/.claude.json.
Then run /mcp inside Claude Code to confirm Clevername is connected. To check the server into a project instead, add it to a .mcp.json file at the repo root. Claude Code expands ${CLEVERNAME_API_KEY} from your environment, so the key stays out of the file:
{
"mcpServers": {
"clevername-mcp": {
"type": "http",
"url": "https://clevername.net/api/hub/mcp/gateway",
"headers": {
"Authorization": "Bearer ${CLEVERNAME_API_KEY}"
}
}
}
}mcpServers from ~/.claude/settings.json. Use claude mcp add-json, or a project .mcp.json.Configure VS Code
Create .vscode/mcp.json in your project and add the server:
{
"inputs": [
{
"type": "promptString",
"id": "clevername-api-key",
"description": "Clevername cn-live-* personal access key",
"password": true
}
],
"servers": {
"clevername-mcp": {
"type": "http",
"url": "https://clevername.net/api/hub/mcp/gateway",
"headers": {
"Authorization": "Bearer ${input:clevername-api-key}"
}
}
}
}VS Code asks for the key (stored securely) the first time the server starts, so it stays out of the file.
Then run MCP: List Servers from the Command Palette to confirm the connection.
Configure Cursor
Add the server to ~/.cursor/mcp.json, then open Settings → MCP to confirm it connected:
{
"mcpServers": {
"clevername-mcp": {
"type": "streamable-http",
"url": "https://clevername.net/api/hub/mcp/gateway",
"headers": {
"Authorization": "Bearer ${env:CLEVERNAME_API_KEY}"
}
}
}
}Cursor reads CLEVERNAME_API_KEY from its environment: set it in your shell profile or system environment, then restart Cursor (an app opened from the Dock may not see a variable set only in a terminal).
Confirm the connection
Reload the client and check its MCP tool list. A 401 means the key is missing, invalid, revoked or expired: check the Authorization header, or create a key at Settings → Keys → Personal Access Keys. A 403 means the key is valid but not allowed: the tool isn't in the key's scope, or the request came from outside its IP allowlist. A key whose agent is suspended, paused or pending review is refused too; the response message says why. Legacy cnk_* keys are still accepted.
Authorization header carries your key and that you have at least one MCP server activated in the Clevername dashboard.