feat: support API key from .env for MCP server configuration#356
Open
feat: support API key from .env for MCP server configuration#356
Conversation
When running `npx @posthog/wizard mcp add`, the wizard now checks for POSTHOG_PERSONAL_API_KEY in .env/.env.local and uses it to configure the MCP server with API key auth instead of OAuth. This enables Stripe Projects users to set up MCP entirely from the terminal. Co-Authored-By: Claude Opus 4.6 (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. |
Collaborator
|
/wizard-ci next-js |
🧙 Wizard CI ResultsTrigger ID:
Configuration
|
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
Stripe Projects users who provision PostHog get a Personal API Key synced to their
.envfile, but themcp addcommand always uses OAuth mode, requiring a browser login. This breaks the "everything from the terminal" experience.Changes
--api-keyflag tonpx @posthog/wizard mcp addPOSTHOG_PERSONAL_API_KEYfrom.env.localor.envin the project directoryaddMCPServerToClientsStep->addMCPServer->client.addServer) which already supports API key mode.envvalueNo changes to
defaults.tsor client implementations - they already handle API key vs OAuth mode.How did you test this code
pnpm run typecheckpasses.envreading utility works with sample.envfilesTest plan
npx @posthog/wizard mcp addin a project withPOSTHOG_PERSONAL_API_KEY=phx_xxxin.envnpx @posthog/wizard mcp add --api-key phx_xxxto verify CLI flag worksnpx @posthog/wizard mcp addwithout any key to verify OAuth mode still works🤖 Generated with Claude Code