MCP server

PerSQL hosts a Model Context Protocol server at https://mcp.persql.com. Any MCP-aware runtime (Claude Desktop, Cursor, Cline, Continue, OpenAI Agents SDK, …) can be pointed at it with a single config block. The agent gets typed SQL tools immediately — no SDK install, no per-runtime adapter.

OAuth-capable runtimes negotiate access automatically — the URL alone is enough. Older runtimes pass a psql_live_… bearer header; the same token authenticates against the /v1 REST API.

Endpoint

Stack	URL
Production	https://mcp.persql.com
Staging	https://mcp-staging.persql.com

Transport: streamable-HTTP MCP (JSON-RPC 2.0 over HTTPS POST). Stateless — each tool call is independent, no Mcp-Session-Id required.

Authentication

Two paths, picked automatically by the runtime:

1. OAuth 2.1 with PKCE + dynamic client registration (MCP authorization spec). On a 401, the server returns WWW-Authenticate: Bearer resource_metadata=…. The runtime fetches the metadata at /.well-known/oauth-protected-resource, registers a public client at /oauth/register, opens the browser to console.persql.com/oauth-consent, you pick a workspace, the runtime stores the issued token. No copy-paste step.
2. Static bearer token as fallback for runtimes without OAuth support (Authorization: Bearer psql_live_…). Create one under console.persql.com → API tokens.

Configuration

Claude Code

One command, no file editing:

claude mcp add persql --transport http https://mcp.persql.com

The server registers in the current Claude Code session immediately. Use claude mcp list to verify and claude mcp remove persql to undo.

If your Claude Code build doesn’t speak MCP OAuth, append a bearer header:

claude mcp add persql \
  --transport http https://mcp.persql.com \
  --header "Authorization: Bearer psql_live_…"

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "persql": {
      "url": "https://mcp.persql.com"
    }
  }
}

Restart Claude Desktop. The first tool call opens the browser to the PerSQL consent screen; pick a workspace and you’re in. Tools appear under the 🔌 plug icon.

Bearer fallback:

{
  "mcpServers": {
    "persql": {
      "url": "https://mcp.persql.com",
      "headers": { "Authorization": "Bearer psql_live_…" }
    }
  }
}

Cursor

Edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):

{
  "mcpServers": {
    "persql": {
      "url": "https://mcp.persql.com"
    }
  }
}

Same fallback shape with a headers block if needed.

Other runtimes

Any MCP runtime that speaks streamable-HTTP works. URL alone if it supports OAuth; URL + bearer header if not. Cline, Continue, Sourcegraph Cody, Codeium — the config block is the same.

Tools

All tools are scoped to the workspace your token (or OAuth grant) belongs to.

Query

• query(database, sql, params?) — single statement, ? placeholders, returns { rows, rowsRead, rowsWritten }.
• batch(database, statements, transaction?) — up to 100 statements; set transaction: true to wrap in a transaction.
• validate_sql(database, sql, params?) — parse + bind-check without executing. Cheaper than running the query just to find a typo.

Schema and docs

• list_databases — slug, name, status for every database in the workspace.
• describe_database(database) — one-call descriptor: every table’s columns, foreign keys, and stored semantic descriptions. The first call to make on a fresh database.
• list_tables, describe_table, sample_table — the per-table variants when you don’t want the full graph.
• search_schema(database, query, limit?) — natural-language ranked search across table + column names and stored descriptions.
• schema_doctor(database) — lints the schema; flags missing primary keys, unindexed foreign keys, ambiguous columns. Read-only.
• get_docs — read the workspace’s stored schema descriptions. (Write them from the console or the /v1 REST API.)
• ask(database, question) — plain English → SQL with a budget cap.

Agent-shape primitives

• claim_branch(database, ref, ttlSec?, role?) — one-shot lease that creates or resets a branch and creates a scoped token. Per-agent-run sandboxes.
• propose_mutation / apply_mutation — pre-flight a write, inspect the rowcount, redeem with a single-use token.
• claim_handoff(token, name?) — sub-agent side; redeems a phand_… for a regular bearer token scoped to one (database, branch, role).
• query_log(database, ...) / recent_actions(database, ...) — replay what changed. Also exposed inside the DB as _persql_meta_query_log so an agent can JOIN against its own audit.

Provisioning

• create_database({ name, slug, region?, ttlDays? }) — spin a new SQLite database in the workspace. ttlDays (1–30) creates a self-deleting DB — useful when you want a sandbox without managing cleanup. Requires an unscoped admin-role token.

Schedules and webhooks

Not exposed as MCP tools. Configure scheduled queries and webhooks from the console or the /v1 REST API — the features themselves are unchanged.

Spend introspection and self-funding

• whoami — workspace, role, scopes, plus live spend counters: balanceUsdMicros, graceFloorUsdMicros, and unbilledUsdMicros (debited since the last hourly flush). Self-throttle on these before the gate returns 402.
• topup_balance({ amountUsd, returnUrl? }) — create a Stripe Checkout URL to fund the workspace. Requires an unscoped admin-role token. Returns { url, amountUsd, sessionId, expiresAt }. Under an MPP-capable runtime (Stripe Machine Payments Protocol, x402) the runtime can drive Checkout end-to-end; otherwise hand the URL to a human.

Endpoints, branches, snapshots, migrations

The rest of the surface mirrors the console: list_branches, create_branch, delete_branch, merge_branch, preview_branch_merge, branch_diff, list_snapshots, create_snapshot, restore_snapshot, restore_to_time, list_endpoints, create_endpoint, publish_endpoint, endpoint_logs, list_migrations, create_migration, apply_migration, rollback_migration. Roughly forty-five tools total — list them at runtime via your MCP client’s tools panel.

Telemetry

Every query and batch invocation through MCP records the same query event in PerSQL’s analytics dataset as the /v1 REST path. Customer usage dashboards aggregate both surfaces — there’s no separate “MCP usage” view.

ask additionally records an ai_call event with the model used and the tokens consumed — the same event used to bill the AI-tokens meter.

Spending controls

MCP shares the same model as /v1: the prepaid workspace balance is the only spend control. A token spends as fast as you call it until the balance returns 402. The 402 response carries an x402-compatible body (x402Version, accepts[]) so MPP-capable runtimes can complete a top-up programmatically; non-MPP runtimes use topup_balance to create a Checkout URL.

If you want a tighter blast-radius for a single key, create a separate workspace with its own balance and scope the token to it.

AI-powered tools (ask) also drain the balance via the AI-tokens meter — see Pricing for the rate.

Idempotency keys for safe retry are not yet exposed via MCP — use the SDK or raw HTTP if you need them.