Cursor should use the native stdio MCP configuration in `.cursor/mcp.json`.
OVERVIEW
Cursor uses `.cursor/mcp.json` or `~/.cursor/mcp.json` for MCP servers. For Zephex, the reliable setup is the stdio block below running `npx -y zephex` with `ZEPHEX_API_KEY` in the env block.
CONFIG FILE LOCATION
Create this file: .cursor/mcp.json in your project root directory. If the .cursor folder does not exist, create it.
Paste the JSON exactly as shown. Keep the server name as zephex so the connection is easy to verify in screenshots, support requests, and tool lists.
Replace `mcp_sk_your_key_here` with the real key from Dashboard -> API Keys.
{ "mcpServers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" } } }}After restart, verify the connection from Cursor itself before you start asking the agent to edit code.
You probably reloaded the window instead of fully quitting Cursor. Quit the app completely, reopen it, and start a new chat session.
Check that the config uses `command`, `args`, and `env` exactly as shown above instead of the older hosted HTTP fields.
Verify the file is exactly .cursor/mcp.json at the project root. Remove trailing commas and comments, then validate that the JSON parses cleanly.
The config file is usually in the wrong place. Make sure .cursor/mcp.json is inside the root of the project currently open in Cursor, not in a parent folder or sibling repo.
If the editor still does not connect, return to Quickstart or check Connection Issues.