Config Export

Export your Clevername MCP configuration for Claude Code, VS Code, Cursor, or any generic MCP client. OAuth-capable clients should use the exported gateway URL and sign in in the browser.

Key Concepts

Export

Exporting generates a JSON configuration snippet for your MCP client. It always includes the Clevername gateway entry (which relies on MCP OAuth and embeds no token), 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.

Exporting Your Configuration

Open the export dialog

Navigate to Dashboard → Integrations → Installed and click Export Config.

Installed page with the Export Config button highlighted

The Export Config button generates a JSON snippet for your client.

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.

Tip

The gateway entry is the important part — it automatically picks up new server installations, and OAuth-capable clients can use it without adding any bearer header.

Copy and place the snippet

Click Copy to Clipboard and paste the snippet into your client's config:

Claude Code: a project .mcp.json at the repo root, or run claude mcp add --transport http clevername-mcp https://clevername.net/api/hub/mcp/gateway instead
VS Code: .vscode/mcp.json in your project
Cursor: ~/.cursor/mcp.json, or Settings → MCP

Important

Claude Code does not read mcpServers from ~/.claude/settings.json and does not use claude_desktop_config.json (that file belongs to Claude Desktop).

Integrations Overview IDE Gateway MCP Connections Integration Directory