feat: setup mcp server automatically on install#48
Conversation
|
|
||
| Get started with some prompts like: | ||
|
|
||
| - What feature flags do I have active? |
daniloc
left a comment
daniloc
left a comment
There was a problem hiding this comment.
Very, very cool!
one thought:
Would it be valuable to extract ALL the configuration paths here into a separate file? as is they're kind of buried in the code and I suspect we should prepare for them to change from time to time, given the state of flux we're in. then we could audit them all at a glance.
So right now all of these clients have different ways of adding servers, some use yaml files, others use different configs etc. Probably makes sense to standardize this as it coalesces into a standard format. |
|
@daniloc I've moved the API key stuff to be more explicit since it feels off to create a broadly scoped API key for the user without them doing it themselves. Will ship this flow and we can start testing it and see what the feedback is... |
* feat: add mcp client support, add cursor client * feat: automatically add mcp servers + mcp client support for cursor * fix: remove spare arg * feat: add client for claude desktop * fix: import correctly * chore: add some tests * chore: remove testing defaults * feat: ask for personal api keys, redirect to api key preset * chore: add mcp setup to all frameworks * fix: remove dead test
2 participants
This adds support on the wizard for setting up the PostHog MCP server after an install happens.
If the
/wizard/dataendpoint returns a personal API key than we will use that to setup the MCP clients on the users computer by adding the MCP server to their application config.It adds support for Claude Desktop and Cursor as MCP clients.
This also adds two new commands
npx @posthog/wizard mcp addandnpx @posthog/wizard mcp removefor dealing with mcp servers only.