MCP Overview — WoWSQL Docs

Model Context Protocol (MCP)

WoWSQL — connect AI assistants to your projects

What it is: MCP is an open standard for connecting assistants (Cursor, Claude Desktop, VS Code, etc.) to tools and data. WoWSQL hosts an HTTP MCP endpoint so your assistant can list projects, run SQL, search docs, and more — using OAuth 2.0 (no long-lived API keys pasted into JSON for the default flow).

How it works

You add the WoWSQL MCP URL to your client (see client setup).
On first use, the client obtains an access token via OAuth (browser consent in the WoWSQL app).
Requests to MCP use Authorization: Bearer <token> against the WoWSQL API behind the scenes.
Optional URL query parameters scope which project and which tools are available (e.g. read-only SQL).

Hosted MCP URL

Production MCP base (Streamable HTTP — clients use POST with JSON-RPC):

https://mcp.wowsql.com/mcp

For self-hosted development, run the MCP package from the repo and point clients at http://localhost:8787/mcp (see mcp/README.md).

URL query parameters

Append these to the MCP URL to scope behavior (same pattern as Supabase-style MCP):

Parameter	Meaning
`project_ref`	Project UUID or slug — required for database/storage tools when you want a fixed project.
`read_only=true`	Blocks mutating SQL (INSERT/UPDATE/DELETE/DDL) in `execute_sql`.
`features`	Comma-separated: e.g. `account,database,docs,storage`. Controls which tool groups are registered.

Example scoped URL:

https://mcp.wowsql.com/mcp?project_ref=YOUR_PROJECT_SLUG&read_only=true&features=database,docs

Authentication

WoWSQL MCP is a protected resource: unauthenticated POST /mcp returns 401 with WWW-Authenticate metadata so the client can start OAuth. You complete login/consent in the browser; the client stores refresh/access tokens per its implementation.

Dashboard

Use the WoWSQL dashboard for OAuth consent flows tied to your account. Project-scoped URLs reduce what the assistant can touch.

Next steps

Static page: sdk/Docs updates/mcp-overview.html