# droPrompt MCP Server

https://droprompt.com/mcp.html

Connect droPrompt to ChatGPT, Claude, Claude Code, Cursor, Codex, Gemini CLI, Windsurf, Zed, or any MCP client that supports Streamable HTTP.

## Connection

- Endpoint: `https://mcp.droprompt.com`
- Transport: **Streamable HTTP** (sometimes labeled **HTTP**)
- Do not append `/sse`; legacy SSE clients are not compatible with this endpoint.
- Authentication: OAuth 2.1 is preferred. Clients that support custom headers can instead send `Authorization: Bearer dp_live_...`.
- Usage requires an eligible droPrompt Pro or Max account.

## Tool

The server exposes one MCP tool:

- `droprompt`: generate or refine a model-ready prompt using the supplied task and context.

## Create an API key

1. Sign in at [droprompt.com/mcp.html#api-key](https://droprompt.com/mcp.html#api-key).
2. Enter a key name and select **Generate API key**.
3. Copy the `dp_live_...` value immediately; it is shown only once.
4. Store it in a secret manager or environment variable such as `DROPROMPT_API_KEY`. Never commit it to source control.

API keys are for clients that accept custom Authorization headers. ChatGPT web and Claude web/Desktop should use OAuth.

## ChatGPT web

1. Open **Settings → Security and login → Developer mode** and enable Developer mode.
2. Open **Settings → Plugins** (or `chatgpt.com/plugins`) and select **+**.
3. Add `https://mcp.droprompt.com`, choose **Streaming HTTP** and **OAuth**, then finish sign-in.
4. In a conversation, choose **Developer mode** from the Plus menu and enable droPrompt.

ChatGPT web does not read local MCP configuration files and does not need an API key for this connection.

## Claude web and Desktop

1. Open **Customize → Connectors → + → Add custom connector**.
2. Name it `droPrompt` and enter `https://mcp.droprompt.com`.
3. Select **Add**, then **Connect**, and complete OAuth.
4. Enable droPrompt from **+ → Connectors** in a chat.

Use Connectors for this remote server; do not add it to `claude_desktop_config.json`.

## Claude Code

```sh
claude mcp add --transport http --scope user droprompt https://mcp.droprompt.com
claude mcp list
```

Open Claude Code, run `/mcp`, select droPrompt, and complete OAuth in the browser. For headless API-key use, export `DROPROMPT_API_KEY`, then add the server with the header:

```sh
claude mcp add --transport http --scope user \
  --header "Authorization: Bearer ${DROPROMPT_API_KEY}" \
  droprompt https://mcp.droprompt.com
```

## Cursor

Add this to the global `~/.cursor/mcp.json` or the project-local `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "droprompt": {
      "url": "https://mcp.droprompt.com"
    }
  }
}
```

Cursor will offer OAuth. For API-key mode, add `"headers": { "Authorization": "Bearer ${env:DROPROMPT_API_KEY}" }` to the server object.

## ChatGPT desktop, Codex CLI, and IDE extension

Add this to `~/.codex/config.toml`:

```toml
[mcp_servers.droprompt]
url = "https://mcp.droprompt.com"
# bearer_token_env_var = "DROPROMPT_API_KEY"
```

Leave `bearer_token_env_var` commented out for OAuth, then run `codex mcp login droprompt`. Uncomment it for API-key mode after exporting `DROPROMPT_API_KEY`. Use `/mcp` to inspect the connection.

## Gemini CLI

For OAuth:

```sh
gemini mcp add --transport http --scope user droprompt https://mcp.droprompt.com
gemini mcp list
```

For API-key mode, export `DROPROMPT_API_KEY`, then run:

```sh
gemini mcp add --transport http --scope user \
  --header "Authorization: Bearer $DROPROMPT_API_KEY" \
  droprompt https://mcp.droprompt.com
```

In manual JSON, use `"httpUrl": "https://mcp.droprompt.com"`, not `url`; Gemini reserves `url` for legacy SSE.

## Windsurf

Add this to `~/.codeium/windsurf/mcp_config.json`:

```json
{
  "mcpServers": {
    "droprompt": {
      "serverUrl": "https://mcp.droprompt.com"
    }
  }
}
```

Refresh the MCP list and complete OAuth. For API-key mode, add `"headers": { "Authorization": "Bearer ${env:DROPROMPT_API_KEY}" }` to the server object.

## Zed

Add this to Zed's `settings.json`, or use **Settings → AI → MCP Servers → Add Remote Server**:

```json
{
  "context_servers": {
    "droprompt": {
      "url": "https://mcp.droprompt.com"
    }
  }
}
```

With no Authorization header, Zed starts the MCP OAuth flow.

For API-key mode, add this to the server object and replace the placeholder locally. Zed does not document environment-variable interpolation for this header, so protect the settings file.

```json
"headers": {
  "Authorization": "Bearer dp_live_YOUR_KEY"
}
```

## Any other MCP client

```json
{
  "mcpServers": {
    "droprompt": {
      "url": "https://mcp.droprompt.com",
      "transport": "streamable-http"
    }
  }
}
```

This JSON is illustrative because MCP clients do not share one universal configuration schema. Adapt the field names while keeping Streamable HTTP, the root endpoint, and OAuth or a Bearer header.

Allow the client to discover OAuth automatically. If it cannot, but supports custom headers, send:

```text
Authorization: Bearer dp_live_your_key_here
```