Detectify MCP Server

Claude Code

1. Register the server

claude mcp add --transport http detectify \
  https://mcp.detectify.com/mcp \
  --callback-port 54321 \
  --client-id=5aaebbc4-eeca-4ede-a03e-682a495082f6

2. Authenticate

Inside a Claude Code session run /mcp, pick detectify from the list, and choose Authenticate. Claude Code opens a browser where you log in to Detectify, consent, and pick your team.

Verify with /mcp — the server should show as connected.

Codex

1. Register the server

codex mcp add detectify \
  --url https://mcp.detectify.com/mcp \
  --oauth-client-id 5aaebbc4-eeca-4ede-a03e-682a495082f6

2. Pin the callback and scopes

Edit ~/.codex/config.toml: add the two mcp_oauth_callback_* keys at the root of the file (not inside any table), and add a scopes line to the [mcp_servers.detectify] block that codex mcp add just created.

mcp_oauth_callback_port = 54321
mcp_oauth_callback_url = "http://127.0.0.1:54321/"
 
[mcp_servers.detectify]
url = "https://mcp.detectify.com/mcp"
scopes = ["mcp:read", "offline_access"]
 
[mcp_servers.detectify.oauth]
client_id = "5aaebbc4-eeca-4ede-a03e-682a495082f6"

3. Authenticate

codex mcp login detectify

Codex opens a browser where you log in to Detectify, consent, and pick your team.

Copilot CLI

Copilot CLI supports a pre-registered public client, but its copilot mcp add command has no flag for the OAuth client ID or the callback port. Set those by editing ~/.copilot/mcp-config.json directly. Two fields are required beyond what the CLI writes:

• oauthClientId — the pre-registered client (dynamic client registration is disabled).
• auth.redirectPort — pins Copilot’s loopback callback port.

1. Register the server

copilot mcp add --transport http detectify https://mcp.detectify.com/mcp

2. Add the OAuth fields

Edit ~/.copilot/mcp-config.json and add oauthClientId and auth.redirectPort to the detectify entry:

{
  "mcpServers": {
    "detectify": {
      "type": "http",
      "url": "https://mcp.detectify.com/mcp",
      "oauthClientId": "5aaebbc4-eeca-4ede-a03e-682a495082f6",
      "auth": { "redirectPort": 54321 },
      "tools": ["*"]
    }
  }
}

Or, to add it non-destructively in one step (requires jq):

jq '.mcpServers.detectify = {
  "type":"http",
  "url":"https://mcp.detectify.com/mcp",
  "oauthClientId":"5aaebbc4-eeca-4ede-a03e-682a495082f6",
  "auth":{"redirectPort":54321},
  "tools":["*"]
}' ~/.copilot/mcp-config.json > /tmp/mcp.tmp && mv /tmp/mcp.tmp ~/.copilot/mcp-config.json

3. Authenticate

Start a Copilot CLI session; it detects the unauthenticated server and opens a browser (“Opening browser for detectify authentication…”). Complete the OAuth flow and pick your team. To confirm the port is pinned, check that the browser’s authorize URL contains redirect_uri=http://127.0.0.1:54321/ — a random port means auth.redirectPort was not applied.

Cursor

Cursor’s UI has no field for a pre-registered OAuth client ID — Settings → Customize → MCP only lets you add a server by name and URL. Add the auth block (client ID and scopes) by editing mcp.json directly.

1. Register the server

Edit ~/.cursor/mcp.json (create it if it doesn’t exist) and add the detectify entry:

{
  "mcpServers": {
    "detectify": {
      "url": "https://mcp.detectify.com/mcp",
      "auth": {
        "CLIENT_ID": "5aaebbc4-eeca-4ede-a03e-682a495082f6",
        "scopes": ["mcp:read", "offline_access"]
      }
    }
  }
}

The scopes field matters: if it’s omitted, Cursor discovers scopes from the authorization server’s project-wide metadata, which advertises an offline scope this client isn’t allowed to request — the request is then rejected with invalid_scope. Pinning scopes to the resource-level set above avoids that.

2. Authenticate

Restart Cursor (or reload the MCP config) so it picks up the file change. Open Settings → Customize → MCP — the detectify server appears with a Needs login button. Click it. Cursor opens a browser at one of two fixed redirect URLs (https://www.cursor.com/agents/mcp/oauth/callback for web/Agents, http://localhost:8787/callback for desktop) — both are already registered on this client. Complete the OAuth flow. The button changes to a connected indicator and the tool list populates.

OpenCode

The interactive opencode mcp add flow does not let you specify a pre-registered client ID or pin the redirect URI, so OAuth fails. Edit the config file directly instead.

1. Register the server

Add the following entry to ~/.config/opencode/opencode.json (merge mcp.detectify into your existing config if you already have one):

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "detectify": {
      "type": "remote",
      "url": "https://mcp.detectify.com/mcp",
      "oauth": {
        "clientId": "5aaebbc4-eeca-4ede-a03e-682a495082f6",
        "redirectUri": "http://localhost:54321/callback"
      }
    }
  }
}

clientId is the pre-registered Detectify MCP client; redirectUri must match a redirect URI registered for that client.

2. Authenticate

opencode mcp auth detectify

OpenCode opens a browser for the OAuth flow and caches tokens.

Pi

pi mcp add has no flags for the callback URL or the scopes, so edit the config file directly.

1. Register the server

Add the detectify entry to ~/.pi/agent/mcp.json (merge it into mcpServers if the file already exists):

{
  "mcpServers": {
    "detectify": {
      "url": "https://mcp.detectify.com/mcp",
      "description": "Detectify - go hack yourself",
      "oauth": {
        "clientId": "5aaebbc4-eeca-4ede-a03e-682a495082f6",
        "callbackUrl": "http://localhost:54321/callback",
        "scope": "mcp:read offline_access"
      }
    }
  }
}

callbackUrl must match a redirect URI registered for the client. scope limits the request to the resource-level scopes this client is allowed to request.

2. Authenticate

pi mcp login detectify

Or, inside a Pi session, run /mcp login detectify, or open /mcp, select detectify, and choose Sign in. Pi opens a browser where you log in to Detectify, consent, and pick your team. A running session picks up the new credentials on its next turn; run /reload if the session started before you edited mcp.json.

Verify with pi mcp list — detectify should show as connected with its tools listed.

VS Code

VS Code (v1.102+) has native MCP + OAuth support. Unlike the CLIs and Cursor, VS Code does not read the client ID from mcp.json — it prompts for it interactively on first authentication. Register the server with just transport and URL, then supply the pre-registered client ID when VS Code asks and leave the client secret blank (this is a public client).

1. Register the server

Create ~/Library/Application Support/Code/User/mcp.json (macOS user profile; on Windows/Linux use the equivalent Code/User/mcp.json, or add a workspace-scoped .vscode/mcp.json) and add the detectify entry:

{
  "servers": {
    "detectify": {
      "type": "http",
      "url": "https://mcp.detectify.com/mcp"
    }
  }
}

Alternatively, run MCP: Add Server from the Command Palette (⇧⌘P), choose HTTP, name it detectify, and paste the URL — VS Code writes the same entry for you.

2. Authenticate

Open the Command Palette (⇧⌘P) → MCP: List Servers → select detectify → Start Server. VS Code detects that the server needs auth and prompts for a Client ID — enter 5aaebbc4-eeca-4ede-a03e-682a495082f6 — followed by a Client Secret, which you leave blank. VS Code opens a browser where you log in to Detectify, consent, and pick your team. The MCP output shows success and the server shows as Running.

Verify with a tool call: open Copilot Chat in Agent mode, enable the detectify tools (🛠 icon), and prompt e.g. “Using the detectify tools, what team am I connected to?”. A successful GetCurrentTeam response confirms the connection end-to-end.