Skip to main content
Parse supports two authentication methods. Use whichever fits your workflow. MCP clients like Claude Code and Cursor support OAuth 2.1 natively. Just set the MCP server URL — the client handles the rest via a browser login popup. 
{
  "mcpServers": {
    "parse": {
      "url": "https://api.parse.bot/mcp"
    }
  }
}
No API key needed. The client will:
  1. Discover the OAuth server via /.well-known/oauth-authorization-server
  2. Open a browser window for you to sign in to Parse
  3. Exchange the authorization code for an access token (PKCE)
  4. Automatically refresh tokens when they expire

​
Option 2: API Key

For REST API calls, scripts, or MCP clients without OAuth support, use an API key in the X-API-Key header: 
curl -H "X-API-Key: YOUR_API_KEY" https://api.parse.bot/dispatch/tasks

​
Getting your API key

Dashboard:
  1. Log in to parse.bot
  2. Go to Settings > API Key
  3. Click Generate API Key
  4. Copy the key immediately — it’s only shown once
API (requires JWT): 
# Generate a new key
curl -X POST https://api.parse.bot/account/api-key \
  -H "Authorization: Bearer YOUR_JWT_TOKEN"

# Check your current key
curl https://api.parse.bot/account/api-key \
  -H "Authorization: Bearer YOUR_JWT_TOKEN"

# Revoke your key
curl -X DELETE https://api.parse.bot/account/api-key \
  -H "Authorization: Bearer YOUR_JWT_TOKEN"

​
MCP with API key

If your MCP client doesn’t support OAuth, pass the key in headers: 
{
  "mcpServers": {
    "parse": {
      "url": "https://api.parse.bot/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}
Only one API key is allowed per account. To rotate your key, delete the existing one and generate a new one.

​
Key limits

  • One key per account — delete and regenerate to rotate
  • Key is shown once — store it securely when first generated
  • API key endpoints (GET/POST/DELETE /account/api-key) require JWT authentication, not API key auth