> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plungeai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PlungeAI MCP Server Quickstart

> Connect any MCP client to `https://mcp.plungeai.com/v1`.


The PlungeAI MCP server gives any MCP client the 20 `plungeai_*` tools: discover capabilities, run tools, agents, workflows and missions, schedule jobs and read results.

## When to use PlungeAI MCP?

All four surfaces use the same `ozk_` key, the same account and the same data.

| Surface | What it is | Use it when |
|---|---|---|
| MCP server, `https://mcp.plungeai.com/v1` | The 20 `plungeai_*` tools over MCP | An AI client operates PlungeAI live: discover, run, save, schedule, remember, with approvals and continuations |
| One API, `https://api.plungeai.com` | REST routes, OpenAPI at `GET /v1/openapi.json` | You write or generate code that calls PlungeAI |
| Skills, `https://skills.plungeai.com` | 31 instruction packs your AI client loads | Your client should already know PlungeAI's conventions; skills complement a connection |
| Ocean Studio, `https://studio.plungeai.com` | The browser app | A person builds visually, connects accounts and reviews runs |

<Note>
A docs MCP server that searches and reads these pages from your agent is planned, tracked as TI-35: see [Docs MCP](/developer-tools/mcp/docs-mcp).
</Note>

## Endpoint

| Item | Value |
|---|---|
| URL | `https://mcp.plungeai.com/v1` |
| Transport | Streamable HTTP, JSON-RPC 2.0 over `POST` |
| Authentication | `Authorization: Bearer $PLUNGE_API_KEY` or `X-API-Key: $PLUNGE_API_KEY` (an `ozk_` key); every request needs it, `tools/list` included |
| Responses | JSON; `tools/call` streams as server-sent events |

<Tip>
Create the key at **Dashboard → One API → Keys** (https://dashboard.plungeai.com/one-api?tab=keys) and export it as `PLUNGE_API_KEY` before you configure a client.
</Tip>

## Quick installation

### Let your agent install it

Paste this prompt into your coding agent; it reads the setup file and connects itself:

```text Onboard from /agents.md
Use curl to read https://docs.plungeai.com/agents.md and perform the setup to connect PlungeAI
```

Or name the server directly:

```text Add the PlungeAI MCP server
Add the MCP server https://mcp.plungeai.com/v1 named plungeai to my user-level client config, with the header Authorization: Bearer and the value of my PLUNGE_API_KEY environment variable, then call plungeai_whoami to confirm the connection.
```

### Client installation

Claude Code, one command:

```bash
claude mcp add --transport http plungeai https://mcp.plungeai.com/v1 \
  --header "Authorization: Bearer $PLUNGE_API_KEY" --scope user
```

Codex, which reads the key from `PLUNGEAI_API_KEY`:

```bash
export PLUNGEAI_API_KEY="$PLUNGE_API_KEY"
codex mcp add plungeai --url https://mcp.plungeai.com/v1 --bearer-token-env-var PLUNGEAI_API_KEY
```

A project `.mcp.json` that reads the key from each developer's environment, safe to commit:

```json
{
  "mcpServers": {
    "plungeai": {
      "type": "http",
      "url": "https://mcp.plungeai.com/v1",
      "headers": { "Authorization": "Bearer ${PLUNGE_API_KEY}" }
    }
  }
}
```

One-click installs open your client's install dialog with the URL filled in; add the key afterwards in the client's user-level config:

<CardGroup cols={3}>
<Card title="Add to Cursor" icon="plug" href="https://mcp.plungeai.com/install/cursor">
Opens Cursor's MCP install dialog.
</Card>
<Card title="Add to VS Code" icon="plug" href="https://mcp.plungeai.com/install/vscode">
Opens VS Code's MCP install dialog.
</Card>
<Card title="Add to Replit" icon="plug" href="https://mcp.plungeai.com/install/replit">
Adds the server to Replit Agent.
</Card>
</CardGroup>

Step-by-step pages per client:

<CardGroup cols={3}>
<Card title="Cursor" icon="book-open" href="/integrations/cursor">
User-level `~/.cursor/mcp.json`.
</Card>
<Card title="VS Code" icon="book-open" href="/integrations/vscode">
Copilot agent mode.
</Card>
<Card title="Replit" icon="book-open" href="/integrations/replit">
Integrations → MCP Servers.
</Card>
</CardGroup>

Verify in any client: ask it to use plungeai_whoami to confirm your identity.

<Note>
These docs use PLUNGE_API_KEY; the PlungeAI skills, the Claude Code plugin and the install page use PLUNGEAI_API_KEY; any name works if your config and shell agree.
</Note>