dopesecurity-mcp-server

The Dope MCP is a local Model Context Protocol server that lets an AI assistant talk to your dope.security tenant — look at endpoints, read and tweak policies, and curate custom URL categories. It wraps most of the Flightdeck partner API, runs on your machine, and is read-only out of the box: nothing changes in your tenant until you explicitly turn writes on. It's currently in beta, we hope you enjoy using it.

Installation

Installation is via uvx.

Runs the server on demand. Nothing is installed globally.

Prerequisites

1. Install uv — see Astral's install guide.

2. Install a Python runtime with uv:

   uv python install 3.11
   

MCP client config

Add the server to your MCP client configuration:

{
  "mcpServers": {
    "dope-security": {
      "command": "uvx",
      "args": ["dopesecurity-mcp-server"],
      "env": {
        "DOPE_CLIENT_ID": "your-client-id",
        "DOPE_CLIENT_SECRET": "your-client-secret",
        "DOPE_ENABLE_MUTATIONS": "false",
        "DOPE_ENABLE_DESTRUCTIVE": "false"
      }
    }
  }
}

Three tiers of access

The tool surface is gated by two environment variables, both false by default. Tools that aren't enabled by the active combination are not registered at all — they don't exist on the MCP wire.

Flightdeck RBAC still applies on top of whichever tier you enable: even when a tool is registered, Flightdeck may reject the call because your OAuth client's role doesn't permit it. Start with read-only, flip to mutations when you trust the agent's workflow, and only enable destructive when you explicitly want the agent to be able to start over.

Configuration reference

DOPE_CLIENT_ID and DOPE_CLIENT_SECRET should be provided as environment variables. You can grab the credentials from the dope console.

Available tools

Endpoints (read-only)

Policies (read)

Policies (write — only when mutations enabled)

Policies (destructive — only when both mutations and destructive are enabled)

Custom categories (read)

Custom categories (write — only when mutations enabled)

Custom categories (destructive — only when both mutations and destructive are enabled)

Developing

Setup and verification

From the repository root:

make install      # uv sync --locked
make check        # lint + typecheck + unit tests
make integration-tests  # requires DOPE_MCP_TESTS_CLIENT_SECRET
uv run dopesecurity-mcp-server --help

Run make help to see all available targets.

Known limitations

• assign_policy_principals and unassign_policy_principals are read-merge-write on top of Flightdeck's overwrite-only assignments endpoint, so concurrent edits to the same policy may be clobbered.
• Pagination is cursor-based; the mcp server does not auto-fetch all pages.

Flightdeck routes deliberately omitted from MCP

Some Flightdeck partner API routes are intentionally not exposed as MCP tools and will not be added. This is the list — treat it as a "don't bother proposing this" register.

• PUT /custom_categories/{name}/urls — overwrite-all semantics. An agent calling this with a partial list silently destroys every URL it didn't mention. Use add_urls_to_custom_category, delete_single_url_from_custom_category, and delete_all_urls_from_custom_category instead, which force the agent to state intent explicitly.

Running a local checkout from an MCP client

To point an MCP client (Amp, Claude Desktop, etc.) at your local checkout instead of the published uvx package, replace the command/args so the client launches the server through uv run --directory:

{
  "mcpServers": {
    "dope-security-dev": {
      "command": "uv",
      "args": [
        "run",
        "--directory",
        "/absolute/path/to/dopemcp",
        "dopesecurity-mcp-server"
      ],
      "env": {
        "DOPE_CLIENT_ID": "your-client-id",
        "DOPE_CLIENT_SECRET": "your-client-secret",
        "DOPE_ENABLE_MUTATIONS": "true",
        "DOPE_ENABLE_DESTRUCTIVE": "true",
        "DOPE_LOG_LEVEL": "DEBUG"
      }
    }
  }
}

Replace /absolute/path/to/dopemcp with the path to your clone. The MCP client spawns the server over stdio on demand.