Claude Code
Claude Code is usually configured from the CLI first. The cleanest setup is to register the hosted Zephex endpoint once and then verify it inside a fresh session.
WHAT IS DIFFERENT HERE
Editor-specific MCP wiring
Claude Code can run multiple MCP servers at the same time, so adding Zephex does not interfere with your other MCP entries.
CONFIG LOCATION
Use the Claude Code CLI to add the server, or edit ~/.claude.json or claude_desktop_config.json depending on your version.
Keep the server name stable as zephex and swap only the key between environments.
PREREQUISITES
- Claude Code installed and working normally.
- An active Zephex API key.
- Access to your terminal so you can register the MCP server entry.
CONFIG
- Run the command below to register the hosted server quickly.
- If you maintain config manually, place the server inside the mcpServers object alongside your existing entries.
- Keep the server name as zephex so prompts and screenshots stay consistent.
terminal
claude mcp add --transport http --header "Authorization: Bearer YOUR_API_KEY" zephex https://zephex.dev/mcpRESTART
- Close Claude Code completely.
- Reopen Claude Code.
- Run /mcp in a fresh session to inspect connected servers.
VERIFY
- Use /mcp to confirm the zephex server is connected.
- Ask Claude Code which tools are available before doing normal prompt work.
- If needed, run a direct tools/list curl request to isolate auth from editor UI.
COMMON ISSUES
- The CLI command used the wrong API key or an expired one.
- A stale global config is shadowing the new server entry.
- Claude Code was not fully restarted after registration.
If the editor still does not connect, return to Quickstart or check Connection Issues.