Replies: 1 comment 4 replies
-
|
I've added two new components to my custom build: a separate daemon that handles multiple projects and a PROXY stdio mcp server that connects to the daemon. Usage: I spin up the daemon in advanced (from within a dedicated terminal tab or LaunchAgent) and add the PROXY to Claude Code's user-level mcp server settings. Each session, when it starts, creates a PROXY process that knows which project it's dealing with based on the working directory. I no longer have to worry about which project is currently active. Asking @opcode81 for PR eligibility. Does this design sound ok to you? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I typically manage multiple Claude Code sessions across multiple work trees of multiple Git repos. I added the Serena MCP client to the user-level Claude Code config and ended up facing the limitation that one Serena MCP server can have at most one "active project" at a time.
What is the recommended Serena setup for my use case? Is it the only way to run one Serena MCP server process per working tree, or is there an alternative approach?
Beta Was this translation helpful? Give feedback.
All reactions