Config Export
Export your Clevername MCP configuration for Claude Code, VS Code, Cursor, or any generic MCP client. Add your own cn-live-* key as an Authorization header to the gateway entry before you use it.
Export
Exporting generates a JSON configuration snippet for your MCP client. It always includes the Clevername gateway entry (which embeds no token: you add your own key), plus your installed HTTP servers and custom connections in the client's expected format — mcpServers for Claude Code and Cursor, servers for VS Code.
Import
There is no import flow. Custom HTTP servers from an existing local config are added one at a time from Dashboard → Integrations → Tools → Custom → + Add Custom Server; see MCP Connections. Servers using stdio transport (local command execution) cannot be registered with the cloud gateway.
Open the export dialog
Navigate to Dashboard → Integrations → Installed and click Export Config.
Choose your client
Pick the client you are configuring: Claude Code, VS Code, Cursor, or Generic. The snippet updates to that client's config format.
"headers": { "Authorization": "Bearer ${CLEVERNAME_API_KEY}" } to it (Claude Code's syntax; Cursor reads ${env:CLEVERNAME_API_KEY} and VS Code prompts with ${input:...}), and put the key in your environment, not the file: export CLEVERNAME_API_KEY=cn-live-YOUR_KEY with a personal access key from Settings → Keys → Personal Access Keys (snippets per client: IDE Gateway).Copy and place the snippet
Click Copy to Clipboard and paste the snippet into your client's config:
- Claude Code: a project
.mcp.jsonat the repo root, or add it withclaude mcp add-jsonand${CLEVERNAME_API_KEY}(see Connecting your IDE) - VS Code:
.vscode/mcp.jsonin your project - Cursor:
~/.cursor/mcp.json, or Settings → MCP
mcpServers from ~/.claude/settings.json and does not use claude_desktop_config.json (that file belongs to Claude Desktop).