Cursor
Cursor supports native HTTP MCP configuration, so the cleanest setup is a direct hosted URL plus Authorization header in the project or global MCP config file.
WHAT IS DIFFERENT HERE
Editor-specific MCP wiring
Cursor does not need a bridge package for Zephex. Native URL plus headers is the correct setup and avoids extra transport problems.
CONFIG LOCATION
Create .cursor/mcp.json in the project root, or paste the same JSON into Cursor's global MCP settings.
Keep the server name stable as zephex and swap only the key between environments.
PREREQUISITES
- Cursor installed.
- An active Zephex API key.
- Write access to the project root if you want a per-project MCP file.
CONFIG
- Per-project config is the safest default because it keeps server scope local to the repo.
- Paste the JSON exactly as shown with the hosted endpoint and Authorization header.
- Do not use bridge-based npm packages when Cursor already supports the hosted HTTP transport directly.
.cursor/mcp.json
{ "mcpServers": { "zephex": { "url": "https://zephex.dev/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } }}RESTART
- Fully quit Cursor with Cmd+Q on macOS or Ctrl+Q on Windows/Linux.
- Reopen Cursor.
- Open a new chat instead of reusing one that was open before the config change.
VERIFY
- Open Settings -> Tools & MCPs and confirm zephex appears.
- Ask Cursor what tools are available and make sure the hosted tools are listed.
- Run a direct tools/list request if the UI still looks stale.
COMMON ISSUES
- A window reload was used instead of a full app quit and reopen.
- An older bridge-based config is still present and conflicts with the native HTTP setup.
- The Authorization header was pasted with the wrong casing or extra quotes.
If the editor still does not connect, return to Quickstart or check Connection Issues.