Claude Code should use the stdio MCP config in `~/.claude.json`, or the `claude mcp add` CLI command that writes the same entry for you.
OVERVIEW
Claude Code stores MCP configuration outside the repo in your user config. The key difference from repo-local editors is scope: once the entry is added, it is available across projects on that machine.
CONFIG FILE LOCATION
Create or edit this file: ~/.claude.json. Add the server under the mcpServers object.
Run the command below.
npx zephex setup --claudeClaude Code reads MCP servers from user-level config, so keep the entry clean and explicit. If you already have other MCP servers configured, add zephex alongside them instead of replacing the full object.
Replace `mcp_sk_your_key_here` with the real key from Dashboard -> API Keys.
{ "mcpServers": { "zephex": { "type": "stdio", "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" } } }}Claude Code should show the server from its MCP command flow before you ask it to use any tool.
Claude Code was usually not fully restarted. Close the app completely, reopen it, and run /mcp in a fresh session.
Check that the config uses `type: stdio`, `command: npx`, `args: ["-y", "zephex"]`, and the `ZEPHEX_API_KEY` env value exactly as shown.
Validate ~/.claude.json carefully. A missing brace, trailing comma, or duplicate mcpServers key will prevent Claude Code from loading the config.
Check that you edited the active user config file on the same machine Claude Code is running on. A common mistake is updating a different shell profile or a copied config file.
If the editor still does not connect, return to Quickstart or check Connection Issues.