MCP server

Install in one click:

Or set it up manually:

1. Open the MCP servers panel

   In Cursor, open Customize → MCPs → New MCP server. Cursor opens ~/.cursor/mcp.json for editing.

2. Paste the config

   Pick OAuth (recommended) or a Personal Access Token — the tabs below toggle the config.

   {
     "mcpServers": {
       "zopdev": {
         "url": "https://api.zop.dev/mcp-server",
         "transport": "streamable-http"
       }
     }
   }

   {
     "mcpServers": {
       "zopdev": {
         "url": "https://api.zop.dev/mcp-server",
         "transport": "streamable-http",
         "headers": { "Authorization": "Bearer MCP_PAT" }
       }
     }
   }

   For PAT, swap MCP_PAT for the token you copied at Developer Settings → API Tokens.

3. Save and enable

   Save the file. Back on the MCPs panel, click the newly-added zopdev entry and turn the User (~/.cursor/mcp.json) toggle on.

4. Reload and authenticate

   Click Reload on the zopdev entry. OAuth opens a browser window to sign in — approve to finish. PAT users skip this: the token authenticates every call. The tools appear inside Cursor on the next call.

1. Add the server

   Inside a Claude Code session, pick OAuth (recommended) or a Personal Access Token — the tabs below toggle the command. The -t http flag is required, otherwise Claude records the URL as a program to execute.

   claude mcp add zopdev https://api.zop.dev/mcp-server -t http

   claude mcp add zopdev https://api.zop.dev/mcp-server -t http -H "Authorization: Bearer MCP_PAT"

   For PAT, swap MCP_PAT for the token you copied at Developer Settings → API Tokens.

2. Restart Claude

   Quit Claude Code and start a fresh session with claude. The new MCP server is picked up on startup.

3. Authenticate

   In the session, run /mcp, find the zopdev entry, and select Authenticate. OAuth opens a browser window to sign in — approve to finish. PAT users skip this: the header authenticates every call.

1. Open the custom connector form

   In Claude Desktop, click your profile → Settings → Connectors → Add → Add custom connector.

2. Fill in the details

   • Name: zopdev
   • Remote MCP Server URL: https://api.zop.dev/mcp-server

   Then click Continue.

3. Add and connect

   Claude Desktop shows a few security-verification prompts — accept each one, then click Add to save the connector. Finally click Connect: OAuth opens a browser window to sign in — approve to finish.

Install in one click:

Or set it up manually:

1. Open the MCP config file

   In VS Code (1.99+), open the Command Palette (Cmd + Shift + P on macOS, Ctrl + Shift + P on Windows/Linux), type MCP, and pick the command that opens your user MCP config file (labelled something like MCP: Open User Configuration). To scope the server to one project instead, create .vscode/mcp.json in the workspace root.

2. Paste the config

   Pick OAuth (recommended) or a Personal Access Token — the tabs below toggle the config.

   {
     "servers": {
       "zopdev": {
         "url": "https://api.zop.dev/mcp-server",
         "type": "http"
       }
     }
   }

   {
     "servers": {
       "zopdev": {
         "url": "https://api.zop.dev/mcp-server",
         "type": "http",
         "headers": { "Authorization": "Bearer MCP_PAT" }
       }
     }
   }

   For PAT, swap MCP_PAT for the token you copied at Developer Settings → API Tokens.

3. Save and authenticate

   Save the file. VS Code starts the server automatically and shows a ✓ Running · Stop · Restart · More… inlay hint above the zopdev entry. On the first tool call, OAuth opens a browser window to sign in — approve to finish. PAT users skip this: the header authenticates every call.

   You can also manage the server from Extensions → MCP Servers - Installed → zopdev.

1. Add the server

   Inside a Codex CLI session, pick OAuth (recommended) or a Personal Access Token — the tabs below toggle the command.

   codex mcp add zopdev --url https://api.zop.dev/mcp-server

   export ZOPDEV_MCP_PAT=<your token>
   codex mcp add zopdev --url https://api.zop.dev/mcp-server --bearer-token-env-var ZOPDEV_MCP_PAT

   Grab <your token> from Developer Settings → API Tokens and export it in the shell before Codex launches — Codex reads the env var by name at connect time.

2. Authenticate

   Run codex mcp login zopdev and follow the prompts — OAuth opens a browser window to sign in, approve to finish. PAT users skip this: the bearer env var authenticates every call.

1. Open your client's MCP config

   Any client that speaks the standard MCP JSON config works. Find its config file or MCP settings UI in its docs.

2. Check the field names

   Some clients use serverUrl instead of url, or type instead of transport. The URL and header values below stay the same — only the surrounding key names change.

3. Paste one of these configs

   Pick OAuth (recommended) or a Personal Access Token — the tabs below toggle the config.

   {
     "mcpServers": {
       "zopday": {
         "url": "https://api.zop.dev/mcp-server",
         "transport": "streamable-http"
       }
     }
   }

   {
     "mcpServers": {
       "zopday": {
         "url": "https://api.zop.dev/mcp-server",
         "transport": "streamable-http",
         "headers": { "Authorization": "Bearer MCP_PAT" }
       }
     }
   }

   For PAT, swap MCP_PAT for the token you copied at Developer Settings → API Tokens.

4. Save and connect

   Save the config and restart the client. On the first tool call, OAuth opens a browser to sign in — approve to finish. PAT users skip this: the header authenticates every call.