feat(mcp): add Claude Desktop/Web to mcp add#517
Merged
Conversation
Adds a "Claude Desktop/Web" option to `mcp add` that opens the PostHog connector directory page (https://claude.ai/directory/connectors/posthog) in the browser, since PostHog ships there as a hosted connector rather than a local config. The browser-connector trait is a duck-typed capability (BrowserFinishable + isBrowserFinishable), mirroring the existing PluginCapable pattern — the URL and instruction live on the client, the TUI renders them generically. The Done screen shows the connector URL and "Sign in and click Connect to finish" instead of falsely claiming it's installed, and the feature picker is skipped when only a browser connector is selected (features are configured online). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
joshsny
approved these changes
Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
mcp addlets users wire the PostHog MCP server into local editors (Cursor, VS Code, Zed) or via a CLI plugin (Claude Code, Codex), but there was no path for Claude Desktop / Claude.ai (web), where PostHog ships as a hosted connector the user adds from the Claude connector directory — not as a local config.Changes
mcp add. Selecting it openshttps://claude.ai/directory/connectors/posthogin the browser (opn, same pattern as the OAuth flow).BrowserFinishablecapability +isBrowserFinishableguard (browser-client.ts), mirroring the existingPluginCapablepattern — the connector URL and instruction live on the client, soMcpScreenrenders them generically with no Claude-specifics in the TUI.isServerInstalled()returns false, so it stays out ofmcp remove. The dormant file-basedClaudeMCPClientis left untouched (it's aDefaultMCPClienttest reference).How did you test this code?
claude-web.test.ts(client behavior, opn invocation, browser-finishable detection) and an added case inmcp-installer.test.ts(thefinishnote is surfaced only for browser connectors).pnpm build && pnpm test— 768 tests pass (50 suites);pnpm lint— 0 errors.pnpm try— "Claude Desktop/Web" appears in detected clients; selecting it (alone or alongside an editor) opens the connector page and the Done screen shows the finish instructions; picking only the connector skips the feature prompt.Publish to changelog?
no