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

# MCP Server

> Connect AI agents to Parse via the Model Context Protocol

Parse exposes a hosted MCP server that lets compatible AI agents find, build, manage, and call APIs.

## Connect your agent

### OAuth (recommended)

Add this to your MCP client config (`claude_desktop_config.json`, `.cursor/mcp.json`, `.claude/settings.json`, etc.):

```json theme={null}
{
  "mcpServers": {
    "parse": {
      "url": "https://api.parse.bot/mcp"
    }
  }
}
```

The client handles authentication automatically — it opens a browser window for you to sign in, then manages tokens in the background. No API key needed.

### API key

For clients that don't support OAuth, pass your key in headers:

```json theme={null}
{
  "mcpServers": {
    "parse": {
      "url": "https://api.parse.bot/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}
```

## How it works

The MCP server speaks JSON-RPC 2.0 over HTTP. When your agent connects, it gets a compact set of platform tools for finding, building, calling, and managing APIs:

| Tool | Description |
| - | - |
| `marketplace_search` | Search the public marketplace for an existing API |
| `marketplace_categories` | List marketplace categories |
| `marketplace_subscribe` | Add a marketplace API to your account (returns a callable scraper) |
| `marketplace_pin_version` | Pin a subscribed API to a specific version |
| `create_api` | Create a new API from a website URL |
| `list_apis` | List all your APIs (with optional status filter) |
| `get_api` | Get full details for an API by task ID |
| `revise_api` | Modify a completed API with natural language |
| `cancel_task` | Cancel an in-flight build or revision |
| `call_endpoint` | Call any endpoint by scraper ID + endpoint name |
| `fork_updates` | Check, preview, merge, or roll back updates for a forked API |
| `list_versions` | List an API's version history |
| `list_revisions` | List the revision history for a task |

> [!NOTE]
>
> APIs for sites that require a login can be created over MCP by passing `allow_auth: true` to `create_api` — after a one-time disclaimer acceptance in the [dashboard](https://parse.bot). The build pauses at `needs_input` for a person to sign in and answer its prompts in the web app; credentials are never supplied to a build through MCP chat. Calling a finished authenticated API with `call_endpoint` also works — see [Authenticated APIs](https://docs.parse.bot/authenticated-apis.md).

Inspect an account API with `get_api`, or a marketplace API with `marketplace_search` detail mode, then use the returned endpoint details with `call_endpoint`. Match `params` to the endpoint's advertised parameter schema.

Completed describe results also include a top-level `spec_url` for the complete OpenAPI 3.1 document. Fetch that URL with your `X-API-Key`; the document is not inlined into the MCP response. Account APIs point to the contract that produced their endpoints, while marketplace detail pins the canonical API's latest release. Add `?version=N` to an unpinned URL when you need a specific available version.

```bash theme={null}
curl -fsS "$SPEC_URL" \
  -H "X-API-Key: $PARSE_API_KEY"
```

## OAuth flow details

Parse implements OAuth 2.1 with PKCE. MCP clients handle this automatically, but if you're building a custom integration:

1. **Discovery**: `GET /.well-known/oauth-authorization-server` returns all endpoints
2. **Registration**: `POST /oauth/register` to get a `client_id`
3. **Authorization**: `GET /oauth/authorize` with PKCE challenge — redirects to consent page
4. **Token exchange**: `POST /oauth/token` with the authorization code + PKCE verifier
5. **Refresh**: `POST /oauth/token` with `grant_type=refresh_token` — tokens rotate automatically

Access tokens are JWTs that expire after 1 hour; the client uses the refresh token to get new ones. Refresh tokens are single-use (valid 7 days) and a fresh one is issued on every exchange.

## Protocol details

* **Endpoint**: `POST https://api.parse.bot/mcp`
* **Transport**: Streamable HTTP
* **Supported protocol versions**: `2025-03-26`, `2025-06-18`
* **Supported methods**: `initialize`, `notifications/initialized`, `tools/list`, `tools/call`, `ping`

> [!NOTE]
>
> Prefer code over an agent runtime? The same APIs are available as a typed [Python SDK](https://docs.parse.bot/sdk.md) and as plain [REST endpoints](https://docs.parse.bot/quickstart.md) — the MCP server is one of three surfaces over the same contract.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.