diff --git a/developers/submit.mdx b/developers/submit.mdx index 11fd4e0..42e232f 100644 --- a/developers/submit.mdx +++ b/developers/submit.mdx @@ -131,8 +131,8 @@ is the full reference. This table covers what it leaves to you. | `license` | The repository's SPDX license. Required for a `github` source, left out for `closed` | | `install` | Where the install button goes. Use the store the integration ships in: `raycast-store`, `vscode-marketplace`, `alfred-gallery`, `app-store`, or `homebrew` for a formula or cask in Homebrew's own repositories. Otherwise `github-release`, or `ships-with-host` when the other product includes it. `page`, a plain download page, needs a maintainer's approval | | `host` | The other product: `name`, `url`, `minVersion`, and a `note` for a paid tier it needs | -| `platforms` | The TablePro apps it works with: `macos`, `ios`, `ipados` | -| `minTableProVersion` | Optional. The oldest TablePro release it works with, per platform | +| `platforms` | The TablePro apps it works with: `macos`, `linux`, `ios`, `ipados` | +| `minTableProVersion` | Optional. The oldest TablePro release it works with, per platform. A beta is written as `0.1.0-beta.1` | | `categories` | One or two of `ai-clients`, `automation`, `cloud-hosting`, `command-line`, `editors`, `launchers`, `local-development`, `other` | | `surfaces` | The TablePro interfaces it calls: `url-scheme`, `database-url`, `applescript`, `mcp`, `pairing`, `cli`, `shortcuts` | | `disclosures` | What it reads, writes and sends, covered in [Disclosures](#disclosures) | diff --git a/docs.json b/docs.json index 78185dc..1c755cd 100644 --- a/docs.json +++ b/docs.json @@ -44,6 +44,10 @@ } }, "redirects": [ + { + "source": "/linux", + "destination": "/linux/install" + }, { "source": "/development/setup", "destination": "/development/overview" diff --git a/integrations/mcp-clients.mdx b/integrations/mcp-clients.mdx index 1d59eaf..11ffe58 100644 --- a/integrations/mcp-clients.mdx +++ b/integrations/mcp-clients.mdx @@ -17,6 +17,10 @@ Paste one absolute path into your client's MCP config and stop there. `tablepro- For an install outside `/Applications`, use your own bundle's path. **Connect a Client…** in **Settings > MCP** shows snippets with it filled in. + +TablePro for Linux has no bridge. Its clients take an address and a token instead: see [TablePro for Linux](#tablepro-for-linux). + + ## Clients that take the JSON above Only the config file differs. @@ -116,6 +120,42 @@ Two installs share that one handshake file, so the bridge reaches whichever Tabl For a narrower scope than `readWrite`, or a connection allowlist, use the [HTTP transport](#http-transport) with a token you mint yourself. +## TablePro for Linux + +TablePro for Linux has no `tablepro-mcp` bridge. A client reaches its server over HTTP on `127.0.0.1` with an access token, and the server runs only while TablePro is open. + +1. Turn on **Preferences > MCP > Enable MCP Server**. +2. Under **Client Setup**, click **Copy Address**, then **Copy Access Token**. +3. Give both to the client. + +Claude Code: + +```bash +claude mcp add --transport http tablepro http://127.0.0.1:23508/mcp \ + --header "Authorization: Bearer tp_your_token_here" +``` + +`claude mcp list` should show it as connected. + +Zed, in `~/.config/zed/settings.json`: + +```json +{ + "context_servers": { + "tablepro": { + "url": "http://127.0.0.1:23508/mcp", + "headers": { + "Authorization": "Bearer tp_your_token_here" + } + } + } +} +``` + +Claude Desktop starts MCP servers only as commands, so it needs a stdio-to-HTTP bridge of its own to reach this server. + +The Linux server has nine tools: `list_connections`, `connect`, `list_schemas`, `list_tables`, `describe_table`, `get_table_ddl`, `browse_table`, `count_rows` and `execute_query`. Each connection's **External Clients** level decides what a client may do there: **Blocked**, **Read Only** (the default) or **Read & Write**. A write runs only after you click **Run** in the connection's window. **Regenerate Access Token…** turns the old token away at the next request, so paste the new one into every client. + ## HTTP transport Use HTTP when the client cannot spawn a local process. Mint a token in **Settings > MCP > Authentication** and point the client at the server: