feat: add built-in MCP client, Shortcuts and command line entries

[datlechin]

Entry

• claude-desktop, claude-code, cursor, zed: one per IntegrationClient case on TablePro main, all through the bundled tablepro-mcp bridge.
• shortcuts: the three App Intents actions in the iPhone and iPad app.
• command-line: the tablepro command and database URLs.
• All Official, install.type built-in, docs links on the /integrations/... and /developers/... paths. Every URL answers 200 with no redirect.

minTableProVersion:

• MCP clients, macOS 0.37.0: v0.37.0 is the first tag that embeds Contents/MacOS/tablepro-mcp (0.36.0 shipped the bridge as mcp-server). CHANGELOG 0.37.0: "External API for Raycast, Cursor, Claude Desktop, and other MCP clients". The 0.37.0 docs already covered Zed; the setup sheet added it in 0.40.0.
• command-line, macOS 0.57.0: CHANGELOG 0.57.0 (#1486). CommandLineToolInstaller.swift first ships in v0.57.0.
• shortcuts, iOS and iPadOS 1.0: the iOS app's only public version (App Store, 2026-09-22). The insert actions need build 17 (2026-08-19); main was on build 22 from 2026-09-19.

Icons:

• No vendor logos. The Anthropic, Cursor and Zed logo terms are not checked yet, so the four MCP clients share a TablePro-made plug placeholder. Replace it with each vendor's logo once its terms allow.
• Shortcuts and command line get TablePro-made glyphs (bolt, >_), since Apple's guidelines forbid its icons.
• All six: Ink #1F1B16 tile, Paper #F5F1EA glyph, 512x512, drawn with Pillow.

Changes from the design drafts:

• MCP writes includes schema: the bridge token is Read & Write, which reaches create_database and non-destructive DDL through execute_query (docs developers/mcp-tools, Scopes and gates).
• No settings pane named in the text. Setup steps stay behind the docs link.
• command-line source.path is the folder that holds CommandLineToolInstaller.swift. The schema expects a folder, and a file path redirects on GitHub.
• Claude Desktop host URL is claude.com/download. claude.ai/download answers 301.

Checklist

• I read the listing policy and the entry follows it.
• python3 scripts/validate.py passes on my machine (also with --online --scan-sources --base origin/main).
• I am the publisher, a member of the publishing organization, or a major contributor.
• The integration uses only documented TablePro interfaces.
• The name does not include TablePro, and the icon is not the TablePro app icon.
• The disclosures are true: what it reads and writes, Safe Mode, network, account, payment.
• I own the icon and screenshots, or may use them, and I let TablePro show them in the directory and its published data.
• I wrote this pull request myself. If an AI tool helped, I say how below and I checked every claim.

Consent or notes

• Six entries in one maintainer PR, as the registry design allows for the seed.
• Drafted with an AI agent. Facts checked against TablePro main, CHANGELOG, release tags and the live docs.