> For the complete documentation index, see [llms.txt](https://inflight.dope.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inflight.dope.security/dope-mcp-server.md).

# Dope MCP Server

### INSTRUCTIONS:

### 1. Clone the mcp open source repo

```
git clone https://github.com/dopesecurity/darkai-dope-mcp.git
cd darkai-dope-mcp
```

### 2. Get your credentials

You'll need a `DOPE_CLIENT_ID` and `DOPE_CLIENT_SECRET` from your dope console. Keep these out of chat/email. You can get the details on this here: <https://inflight.dope.security/dope.console/settings/api-client-credentials>

### 3. Find your MCP client's config file

Each option below gives you a JSON snippet. You paste that snippet into your AI client's MCP config file. If the file already has an `"mcpServers"` block, add the `"dope-security"` entry alongside the existing ones (don't create a second `"mcpServers"` key).

Common locations:

* **Claude Desktop**
  * macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
  * Windows: `%APPDATA%\Claude\claude_desktop_config.json`
  * In the app: *Settings → Developer → Edit Config*
* **Cursor**
  * Project-scoped: `<your-project>/.cursor/mcp.json`
  * Global: `~/.cursor/mcp.json`
  * In the app: *Settings → MCP → Add new MCP server*
* **VS Code (Copilot Chat / MCP)**
  * Workspace: `.vscode/mcp.json`
  * Or *Command Palette → "MCP: Add Server"*
* **Amp**: `~/.config/amp/settings.json` under the `"amp.mcpServers"` key.
* **Other clients**: look for a "MCP servers", "Tools", or "Extensions" settings page; the shape of the JSON is the same.

If the file doesn't exist yet, create it with just the snippet from your chosen option below. **Restart the client after saving.**

### 4. Install as follows

Install from <https://docs.astral.sh/uv/>. No extra setup needed — just point your MCP client config at the checkout:

{\
&#x20; "mcpServers": {\
"dope-security-mcp": {\
&#x20;     "command": "X:\\\darkai-dope-mcp\\\\.venv\\\Scripts\\\dopesecurity-mcp-server.exe",\
&#x20;     "env": {\
&#x20;       "DOPE\_CLIENT\_ID": "",\
&#x20;       "DOPE\_CLIENT\_SECRET": "",\
&#x20;       "DOPE\_ENABLE\_MUTATIONS": "true",\
&#x20;       "DOPE\_TLS\_VERIFY": "false"\
&#x20;     }\
&#x20;   }\
&#x20; }\
}

### For up to date information check out this repo

<https://github.com/dopesecurity/mcp>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://inflight.dope.security/dope-mcp-server.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.