Skip to main content
Deep links drive the GUI. MCP moves data. That one split decides which page you need, and pairing is the step in front of MCP that gets a client its token.

URL scheme

tablepro:// deep links open connections, tables, and queries in the GUI.

MCP server

JSON-RPC tools, resources and prompts for AI clients, over stdio or local HTTP.

Pairing

One-click flow that issues a scoped token to an extension.
Two surfaces build on those. macOS hands TablePro plain database URLs (mysql://…) and .sql files, which is what the Terminal and DDEV integration rides on. On iPhone and iPad, App Intents put three actions in Shortcuts.

​
Quick start

Opening something in the GUI needs no setup at all:
Reading data back needs a token. Install the Raycast extension and run Pair with TablePro, or wire stdio MCP into your own MCP client and skip the extension.

​
Security model

The MCP server binds 127.0.0.1, and on stock settings every request carries a token. A call is allowed only where the token’s scope, the token’s connection allowlist, and the connection’s own External Clients level all permit it; the effective permission is the lowest of them. Tokens has the full model. On top of that, an AI policy of Never refuses the connection outright, and Safe Mode still holds destructive statements behind a confirmation. Each request lands in the activity log with the token behind it, and a statement is stored as a SHA-256 digest rather than as text. Open Settings > Integrations and click View Activity to read it.

​
Versioning

Paths, tools and result fields are additive within a major version, and the app is still on 0.x. See Versioning for what that means for a client you have to keep working.