Skip to content

feat(mcp): set up AI clients in one click from a shared catalog - #4211

Merged
datlechin merged 8 commits into
mainfrom
feat/mcp-connect-client
Nov 12, 2026
Merged

datlechin merged 8 commits into
mainfrom
feat/mcp-connect-client

Conversation

@datlechin

@datlechin datlechin commented Nov 11, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Connect a Client is rebuilt on a catalog both apps read, core/crates/mcp/clients.json: 21 clients on macOS, 19 on Linux, including ChatGPT, Codex, VS Code, Gemini CLI, Copilot CLI, Cline, Goose, LM Studio, Kiro, Warp, Junie and Raycast. Adding a client is a data change.
  • One-click install per client: deeplink when an app handles its scheme, else the client's CLI (argv, never a shell), else a text splice into its settings file that keeps comments and order, keeps symlinks and leaves <file>.tablepro-backup. Copy is always there.
  • Each row shows the client's state from its own settings: Not set up, Set up, Set up with a token, Turned off, TablePro moved, Uses another copy, Old setup in a project, Connected. Update rewrites only how the entry reaches TablePro and keeps the user's tools, disabled, env.
  • The sheet watches MCPServerManager.connectedClients and says " connected" in place (status text plus a VoiceOver announcement).
  • ChatGPT (the new app) installs through ~/.codex/config.toml, shared with Codex CLI. ChatGPT Classic is listed with the reason it cannot reach a local server.
  • Brand logos for MCP clients and AI providers (Simple Icons CC0, or the brand's own published file; notices added), in Settings > AI, the provider pickers and the chat model picker.
  • Token sheet: the snippet stays masked while the token is hidden, the client list comes from the catalog, and a note appears when the port is a fallback that changes on restart.
  • Connected Clients: one row per stdio client across bridge credential rotation, no phantom tablepro-mcp row, catalog names and logos, Connect a Client in the toolbar, Delete key. Disconnect on a stdio row cancels that client's requests only; it no longer locks every stdio client out.
  • MCP Activity Log records and filters by client; its CSV export neutralizes formulas.
  • Fixed: claude mcp add without --scope user, an unquoted bridge path, a Claude Desktop HTTP snippet Claude Desktop cannot use, Generate Token failing silently, the token list not refreshing, any number accepted as the port, "1 seconds" in pairing, a failed start reported by the bridge as "not running", in-flight requests of two stdio clients colliding, Claude Agent losing its tools silently when the Keychain refuses a write, pairing failures without a reason.
  • Linux: Preferences > MCP lists the catalog clients with status, install, update, remove and a per-client page; the server refuses loopback connections from other local accounts; copy gives the full Bearer header; Regenerate works while the server is off.
  • ADR core/docs/decisions/0023-mcp-client-setup-from-one-catalog.md.

What a client can do now that it could not before: nothing. Narrowed: another local account can no longer use a Linux token; a stdio client can no longer cancel another stdio client's request. New behavior a user starts: TablePro writes into the client's own settings file when Install, Update or Remove is clicked.

Tests that pin behavior this PR changes on purpose:

  • MCPIdentityLedgerTests "Two tokens on one machine are two clients" is now "Two HTTP tokens on one machine are two clients".
  • MCPBridgeIntegrationTests testAModernHostRequestIsForwardedByteForByte and testAModernMessageWithBigNumbersIsForwardedUntouched now allow exactly the app.tablepro/bridgeInstance key.
  • MCPClientStatusEvaluatorTests stdioStale, httpEntries, otherScopes, disabledEntries.
  • Linux: the_switch_and_port_edit_the_preferences, jsonc::an_existing_entry_is_replaced_in_place, toml_table::an_existing_server_table_is_rewritten_where_it_stands.

Test plan

  • macOS hosted: 300 tests in 23 suites, 0 failures (verify.sh test).
  • TableProMacCore package: 601 tests (TableProMCPTests 407, TableProMCPClientsTests 106, TableProCommandLineTests 88), 0 failures.
  • Rust tablepro-mcp: 111 unit + 28 integration, clippy -D warnings clean. The Linux peer-uid check also ran against a real Linux kernel in a container.
  • Linux GTK app: built and tested by CI (Flatpak Devel x86_64 and aarch64, deb and rpm packages, Docker tests). Screenshots below are CI's resolute .deb under Xvfb with an empty home.
  • Manual on a Debug build with a sandboxed home: a Claude Desktop entry pointing at a gone copy shows "TablePro moved"; Update rewrote command, kept its env and the other server, and left claude_desktop_config.json.tablepro-backup. Install for Zed added context_servers.tablepro to a settings.json with comments and kept every comment and key. Cursor with a current entry reads "Set up".
Before After
Before After
Before dark After dark

Linux, Preferences > MCP:

Before After
Linux before Linux after
Linux before dark Linux after dark

Linux, a client's page:

Linux Claude Code page

Docs: TableProApp/docs#204.

Fixes #4196

@datlechin
datlechin merged commit 89ae770 into main Nov 12, 2026
34 of 35 checks passed
@datlechin
datlechin deleted the feat/mcp-connect-client branch November 12, 2026 21:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MCP: Connect a Client requires manual setup and is missing clients (Codex, ChatGPT, …)

1 participant