IDE Gateway
Connect your IDE to Clevername through a single MCP endpoint. Create a cn-live-* personal access key, add the gateway URL with the key as a bearer header, and your tools appear.
How the gateway works
The IDE gateway exposes a single MCP endpoint that aggregates all your installed integration directory servers, custom connections, and built-in tools. Your IDE connects to one URL with one key instead of configuring each server individually.
Authenticating with a personal access key
- One key per device or IDE — Create a
cn-live-*personal access key at Settings → Keys → Personal Access Keys and send it asAuthorization: Bearer cn-live-…(legacycnk_*keys are still accepted) - Scoped access — Keys can be restricted by tool allowlist, budget, and expiry
- One gateway URL — Every client connects to
https://clevername.net/api/hub/mcp/gateway
OAuth sign-in for MCP clients is coming. Until then, every client authenticates with a key.
Create a personal access key
Go to Settings → Keys → Personal Access Keys and create a key. Copy it when it is shown: it starts with cn-live- and is displayed once.
Every client below uses the same gateway URL and sends the key as a bearer header:
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.
To check the server into a project instead, add it to a .mcp.json file at the repo root (Claude Code does not read mcpServers from ~/.claude/settings.json):
{
"mcpServers": {
"clevername-mcp": {
"type": "http",
"url": "https://clevername.net/api/hub/mcp/gateway",
"headers": {
"Authorization": "Bearer ${CLEVERNAME_API_KEY}"
}
}
}
}${CLEVERNAME_API_KEY} from your environment, so the key stays out of the committed file. Run /mcp in Claude Code to confirm Clevername is connected.Configure VS Code (Copilot MCP)
In VS Code, open your .vscode/mcp.json or user settings and add:
{
"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.
Configure Cursor
In Cursor, open Settings → MCP Servers and add a new server:
{
"mcpServers": {
"clevername-mcp": {
"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
Restart or reload the client. Your Clevername tools appear in 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.