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, 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 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.

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.

1. Open the custom connector form

   In Grok on the web, open Skills & Connectors → Connectors → New Connector → Add Custom.

2. Fill in the details

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

3. Add and connect

   Click Add Connector. On the next tool call, OAuth opens a sign-in window — sign in with your ZopNight account and approve.

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 the MCP servers panel

   Click your profile → Settings → Plugins → MCP → Add → Add MCP Server.

2. Fill in the form

   • Name: zopdev
   • Type: Streamable HTTP
   • URL: https://api.zop.dev/mcp-server

   Click Save.

3. Authenticate

   Back on the MCP list, find the zopdev entry and click Authenticate. A browser window opens for OAuth sign-in — approve to finish.

1. Open the Plugins page

   Sign in to ChatGPT on the web, then go to Settings → Plugins and click Add (labelled New plugin in connections on some plans).

2. Fill in the plugin form

   Paste your ZopNight MCP server URL and name the plugin.

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

   ChatGPT will show one or more “I understand” security acknowledgements — tick every one before continuing.

3. Add and sign in

   Click Add. On the next new chat, OAuth opens a sign-in window — sign in with your ZopNight account and approve.

1. Open the MCP config file

   Launch Antigravity IDE with a workspace open (a “No workspace window available” error means you need to open a folder first). Go to Settings → Open Antigravity IDE User Settings → Customize, find the Installed MCP Servers section, and click Open MCP Config — Antigravity opens its raw JSON config file for editing.

2. Paste the config

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

   {
     "mcpServers": {
       "zopdev": {
         "serverUrl": "https://api.zop.dev/mcp-server"
       }
     }
   }

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

   The field must be serverUrl — Antigravity does not accept url or httpUrl. For PAT, swap MCP_PAT for the token you copied at Developer Settings → API Tokens.

3. Save and refresh

   Save the JSON file. Go back to the Installed MCP Servers panel and click Refresh. Antigravity does not hot-reload — a correct-but-unrefreshed config looks identical to a wrong one.

4. Authenticate

   OAuth users: Antigravity displays a code — sign in and paste that code into the Antigravity prompt to complete authentication. PAT users skip this: the header authenticates every call.

1. Add the server

   Pick OAuth (recommended) or a Personal Access Token — the tabs below toggle the command. Use --scope user so the server survives across projects.

   gemini mcp add --scope user --transport http zopdev https://api.zop.dev/mcp-server

   gemini mcp add --scope user --transport http zopdev https://api.zop.dev/mcp-server --header "Authorization: Bearer MCP_PAT"

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

2. Start Gemini

   Launch a session with gemini. From an untrusted workspace, add --skip-trust — Gemini 0.58+ suppresses MCP servers (even user-scoped ones) in untrusted folders otherwise.

3. Authenticate

   In the session, run /mcp auth zopdev. OAuth opens a browser window to sign in — approve to finish. PAT users skip this: the header authenticates every call. Alternatively, just invoke a zopdev tool (“using zopdev, list my organizations”) — Gemini fires the same OAuth flow on the first call.

1. Open the Devin MCP marketplace

   Click your profile → Devin Settings → Configuration → MCP Servers to open the Devin MCP Marketplace.

2. Add a custom MCP

   Click Add Custom MCP and paste one of these configs. Pick OAuth (recommended) or a Personal Access Token — the tabs below toggle the config.

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

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

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

3. Connect

   Go back to Devin Customization → MCP → Installed, find the newly-added zopdev entry, and click Connect. OAuth opens a browser window to sign in — approve to finish. PAT users skip this: the header authenticates every call.

1. Open the MCP settings

   In GitHub Copilot Desktop, go to Customization → MCP → Add.

2. Add the server

   Click Add MCP Server, then fill in:

   • Name: zopdev
   • URL: https://api.zop.dev/mcp-server
   • Type: HTTP

   Click Add Server.

3. Sign in

   Back on the MCP page, find the zopdev row and click Sign in. A browser window opens to sign in — approve immediately and switch straight back to Copilot Desktop; the local callback listener is short-lived. Copilot’s row flips to signed-in once the code is delivered.

1. Add the server

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

   grok mcp add --transport http zopdev https://api.zop.dev/mcp-server

   grok mcp add --transport http zopdev https://api.zop.dev/mcp-server --header "Authorization: Bearer MCP_PAT"

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

2. Restart Grok

   Quit Grok and start a fresh session with grok. 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. Add the server

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

   copilot mcp add --transport http zopdev https://api.zop.dev/mcp-server

   copilot mcp add --transport http zopdev https://api.zop.dev/mcp-server --header "Authorization: Bearer MCP_PAT"

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

2. Restart Copilot

   Quit Copilot and start a fresh session with copilot. 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 MCP servers panel

   Click your profile → Settings → Agents → MCP Servers → Add.

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"
       }
     }
   }

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

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

3. Save and connect

   Save the server. OAuth opens a browser on the first tool call — approve to finish. PAT users skip this: the header authenticates every call.

1. Install Goose and pick an LLM provider

   If you don’t have Goose yet:

   curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh | bash

   Then run goose configure and choose Configure Providers — Goose can’t start a goose session until it has at least one LLM provider (Anthropic, OpenAI, Databricks, Google Gemini, Ollama, etc.). Skip this if Goose is already set up.

2. Add the extension (pick one path)

   Either run goose configure → Add Extension → Remote Extension (Streamable HTTP) and fill in:

   • Name: zopdev
   • URI: https://api.zop.dev/mcp-server
   • Timeout: 300
   • Environment variables: No

   or edit ~/.config/goose/config.yaml directly and add:

   extensions:
     zopdev:
       name: ZopDev
       type: streamable_http
       uri: https://api.zop.dev/mcp-server
       enabled: true
       timeout: 300

   Goose uses OAuth with Dynamic Client Registration for remote extensions — no PAT/header field is needed (or supported today).

3. Authenticate on first tool call

   Start a session with goose session. The first time the model calls a zopdev tool, Goose opens a browser to sign in — approve to finish. Tokens are refreshed automatically after that. The OAuth callback uses an ephemeral 127.0.0.1 port; set GOOSE_OAUTH_CALLBACK_PORT to pin it if your authorization server requires a fixed redirect URI.

1. Open the MCP config file

   In Kiro, 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 at ~/.kiro/settings/mcp.json (labelled something like MCP: Open User Configuration). To scope the server to one project instead, create .kiro/settings/mcp.json in the workspace root — Kiro silently ignores any other filename or location.

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"
       }
     }
   }

   {
     "mcpServers": {
       "zopdev": {
         "url": "https://api.zop.dev/mcp-server",
         "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. Back in Kiro, click Kiro in the sidebar, expand MCP Servers, find the zopdev entry, and click Authenticate. A browser window opens for OAuth sign-in — approve to finish. PAT users skip this: the header authenticates every call.

1. Open the MCP servers panel

   Click your profile → Settings → General → MCP Server → Configure → Add Server → Add Remote Server.

2. Fill in the details

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

   Click Save.

3. Authenticate

   Back on the MCP Server panel, find the zopdev entry and click Authenticate. A browser window opens for OAuth sign-in — approve to finish.

1. Open the MCP settings

   In Trae, go to Settings → MCP → Add → Create Manually.

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"
       }
     }
   }

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

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

3. Authenticate

   Back on the MCP page, find the zopdev entry and click Authenticate. A browser window opens for OAuth sign-in — approve to finish. PAT users skip this: the header authenticates every call.

1. Use the plugin builder

   In Kimi Code Desktop, start a new chat and paste this prompt (swap https://api.zop.dev/mcp-server for the URL from Settings → Organisation → MCP Server in the ZopNight app):

   /plugin-builder connect the zopdev plugin with https://api.zop.dev/mcp-server

   Kimi adds the plugin automatically.

2. Install and authorise

   Go to Plugin → Personal → zopdev, click Install, then click Authorize. A browser window opens for OAuth sign-in — approve to finish.

1. Add the server

   In your terminal, pick OAuth (recommended) or a Personal Access Token — the tabs below toggle the command.

   vibe mcp add zopdev --transport streamable-http --url https://api.zop.dev/mcp-server

   # 1. Export your PAT
   export ZOPDEV_MCP_TOKEN="MCP_PAT"
   
   # 2. Register the server, telling Vibe which env var holds the token
   vibe mcp add zopdev --transport streamable-http --url https://api.zop.dev/mcp-server --api-key-env ZOPDEV_MCP_TOKEN

   For PAT, swap MCP_PAT for the token you copied at Developer Settings → API Tokens. Vibe writes the config to ~/.vibe/config.toml.

2. Authenticate

   Start a Vibe session with vibe, then run /mcp login zopdev. OAuth opens a browser window to sign in — approve to finish. PAT users skip this: the env var authenticates every call.

1. Install OpenCode (if you haven't)

   curl -fsSL https://opencode.ai/install | bash

   Installs to ~/.opencode/bin/opencode; the script updates your shell PATH. Open a new terminal after installation.

2. Add the server

   In a regular terminal (not inside the opencode TUI — that treats the line as a chat message and sends it to the model instead of running the CLI), pick OAuth (recommended) or a Personal Access Token — the tabs below toggle the command.

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

   opencode mcp add zopdev --url https://api.zop.dev/mcp-server --header "Authorization=Bearer MCP_PAT"

   For PAT, swap MCP_PAT for the token you copied at Developer Settings → API Tokens. The config is written to ~/.config/opencode/opencode.jsonc.

3. Authenticate

   OAuth users: in the same regular terminal, run:

   opencode mcp auth zopdev

   A browser window opens to sign in — approve to finish. Running opencode mcp auth … INSIDE the opencode TUI chat prompt won’t work — OpenCode treats it as a message for the LLM and returns a provider-key error; the CLI subcommand must be invoked from the shell. Verify with opencode mcp list — status flips to ready. PAT users skip this: the header authenticates every call.

1. Install the Droid CLI (if you haven't)

   curl -fsSL https://app.factory.ai/cli | sh

   Factory’s installer drops droid in ~/.local/bin/ and updates PATH. Factory Desktop bundles the same binary if you already have that.

2. Add the server

   In a regular terminal (not inside the droid session — the droid REPL doesn’t run CLI subcommands), pick OAuth (recommended) or a Personal Access Token — the tabs below toggle the command.

   droid mcp add zopdev https://api.zop.dev/mcp-server --type http

   droid mcp add zopdev https://api.zop.dev/mcp-server --type http --header "Authorization: Bearer MCP_PAT" --no-oauth

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

3. Authenticate

   Start a session with droid, then run /mcp and pick zopdev → Authenticate. A browser window opens to sign in — approve to finish. PAT users skip this: the header authenticates every call. Run droid mcp list in the outer shell to confirm status flipped to ready.

1. Add the server

   In LM Studio: ⚙ Settings → Connected MCP Servers → Add Custom MCP. Fill in:

   • Name: zopdev
   • Connection: Web address
   • Server address: https://api.zop.dev/mcp-server
   • Authentication: Automatic (OAuth, recommended) or Access token (PAT — paste the token you copied at Developer Settings → API Tokens)

   Click Add MCP.

2. Complete authentication

   OAuth users: LM Studio opens a browser window to sign in — approve to finish. Access-token users skip this: the token authenticates every call. The zopdev entry flips from “Sign-in failed” to a green Connected dot; hit Try again if it doesn’t refresh automatically.

1. Install Kimi Code (if you haven't)

   curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash

   Installs to ~/.kimi-code/bin/kimi; the script updates your shell PATH. Sign in with /login on first launch (Moonshot account or Kimi Platform API key) — Kimi Code CLI needs an LLM provider before any tool call.

2. Add the server

   Create ~/.kimi-code/mcp.json (or edit the project-level .kimi-code/mcp.json) and add:

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

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

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

3. Authenticate

   Start Kimi with kimi, then in the TUI run /mcp-config login zopdev — a browser window opens to sign in, approve to finish. PAT users skip this: the header authenticates every call. Verify with /mcp — the zopdev entry flips to connected.

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": {
       "zopnight": {
         "url": "https://api.zop.dev/mcp-server",
         "transport": "streamable-http"
       }
     }
   }

   {
     "mcpServers": {
       "zopnight": {
         "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.