AI assistant and MCP server
Everything on this page is free.
Use the provider you choose
The assistant works with these providers: GitHub Copilot, ChatGPT, Cursor, Claude, Claude Agent, OpenAI, OpenRouter, Gemini, xAI, Ollama, llama.cpp, MLX, OpenCode Zen and OpenAI-compatible. Depending on the provider, you paste an API key, sign in with an account you already have, or run a model on your Mac. TablePro runs no AI service of its own: requests go straight to the provider, and nothing is sent until you add one.
Each message carries the structure of the connection’s tables, up to a limit you set, and the query in the editor. Result rows go only if you turn that on in Settings > AI. Each connection also has an AI policy, and Never keeps both the assistant and MCP clients away from it.
Review, explain, optimize and fix
Put the cursor in a statement and choose Review with AI (⌥⇧⌘L) for its correctness, cost and safety, Explain (⌘L) for what it does step by step, or Optimize (⌥⌘L) for a rewrite or an index; when a query fails, Fix with AI sits on the error banner. The request carries the structure of the tables the statement names, and the statement itself does not run. Apply to Editor replaces your statement only after you confirm.
Inline suggestions show ghost text as you type and are off by default. AI Rules pin plain-text notes to a connection, such as which column must never be selected, and go with every message.
Chat modes and Agent mode
The chat has three modes. Ask, the default, looks up the schema and runs nothing. Edit can also run queries, and Agent can also run DROP, TRUNCATE and other destructive statements. At Silent, the Safe Mode level new connections start at, writes in Edit and Agent run without asking; from Alert to Safe Mode (Full) each one waits for Run, and Read-Only refuses them. Destructive statements always wait for a click and can never be approved in advance.
Agent mode (⌥⇧⌘A) gives one session the whole window: the sessions on this connection, the conversation, and the SQL it proposed and ran. While it is on, the connection is held at Alert or stricter, so no write runs until you click Run. That is a reminder, not a lock: it is one keystroke from off. Sessions stay on this Mac.
The MCP server
The built-in MCP server lets AI clients work through the connections you saved in TablePro, without ever seeing a password. It listens on 127.0.0.1 only, with no remote mode, and it is off until you turn it on or a client you set up starts it.
Its tools cover connections, schema discovery, reading and writing data, databases and objects, server administration and the app’s own tabs and history, with prompts and resources built from your live schema. Every call goes into an activity log on your Mac, with statements recorded as a digest rather than text, and queries a client runs also appear in your query history.
Connect a client
Settings > Integrations has setup steps and a snippet to copy for Claude Code, Claude Desktop, Cursor and Zed. The bundled tablepro-mcp bridge also works with Claude Desktop, Claude Code, Cursor, VS Code, Cline, Continue, Zed, Windsurf, Antigravity and Goose: it starts TablePro when needed and finds the server, so the client’s config holds no port or token. The official Raycast extension pairs with the app instead, and you approve the pairing on your Mac.
A typical request: ask your client for users who share an email address. It can call list_tables and describe_table, see that the column is named email_address, and run one SELECT through your saved connection, without you pasting the schema into the chat.
What a client may do
Every call passes each of these checks, and the strictest one wins.
- Token scope: Read Only, Read & Write or Full Access, optionally limited to named connections. The bridge receives a Read & Write token by itself, so clients that use it cannot run destructive statements.
- External Clients, set per connection: Blocked, Read Only (the default) or Read & Write. A blocked connection is not even listed.
- Connection approval: the first time a client reaches a connection, a dialog on your Mac asks. You choose whether it asks every time, once per connection or never.
- AI policy: a connection set to Never refuses MCP clients too.
- Safe Mode: writes confirm at the connection’s level, and DROP or TRUNCATE needs a Full Access token and your approval every time. Statements that read or write files, or run code on the server, are refused.
Outside MCP servers
It also works the other way round: an AI session in TablePro can call tools on an MCP server you run, over Streamable HTTP, with HTTPS required unless the server is on this Mac. You choose the connections each server is offered on. Every call shows a card and waits for your click, and no standing approval covers them. The server’s address and token stay on this Mac.
Automation outside the chat
AppleScript can connect, run a query and open a table, within the connection’s External Clients level and Safe Mode. tablepro:// links open a connection, a table or a query tab; a query in a link is filled in after you confirm and never runs by itself. Database URLs such as postgresql:// open as connections.
The tablepro shell command opens those URLs and files in the app; it does not run queries from the terminal. The official Raycast extension searches your connections, tables and query history, and runs queries through the paired app.
Where your data goes
Prompts, the schema context and anything you attach go to the provider you picked, under your own account’s terms with that provider. With Ollama, llama.cpp, MLX or an OpenAI-compatible server you run yourself, they stay on your machine. TablePro receives none of it, and the Mac app’s daily usage report carries nothing about AI or MCP.
When you add GitHub Copilot, its option to send telemetry to GitHub starts switched on; turn it off where you set Copilot up.
Not on iPhone or iPad
The iPhone and iPad app has no AI assistant, Agent mode or MCP server. Everything on this page is in the Mac app.
Where it works
| Capability |
|---|
| AI chat with your own providerMac: FreeiPhone and iPad: Not available |
| Review, Explain, Optimize and Fix with AIMac: FreeiPhone and iPad: Not available |
| Inline suggestions and AI RulesMac: FreeiPhone and iPad: Not available |
| Agent modeMac: FreeiPhone and iPad: Not available |
| MCP serverMac: FreeiPhone and iPad: Not available |
| Outside MCP serversMac: FreeiPhone and iPad: Not available |
AppleScript and the tablepro shell commandMac: FreeiPhone and iPad: Not available |
| Raycast extensionMac: FreeiPhone and iPad: Not available |
Limits worth knowing
- Cursor cannot call TablePro’s tools, so with Cursor as the provider, Edit and Agent run no queries. Local models call tools only if the model supports it.
- Claude Agent uses your Claude Code login and reaches the schema through the MCP server, which has to be on. It depends on Claude Code and can break with a Claude Code release.
- The MCP server listens on 127.0.0.1 only. Reaching it from another machine means forwarding the port yourself, and owning what that exposes.
- The Mac app has no Shortcuts actions; automate it with AppleScript, links or the MCP server.
- Agent sessions and outside MCP servers stay on the Mac where you set them up and do not sync.
Get TablePro
macOS 13 Ventura or laterApple silicon or Intel
iPhone and iPadiOS and iPadOS 18 or later