Raycast

Since each MCP server is just running locally on your host machine (computer) whether through Claude Desktop, your editor, or /raycast, here are reasons you want to setup Installs and configurations separately.

note: But in reality, you could have a single server and have each client call it.

- Each app manages its own MCP server lifecycle
- No conflicts between different apps trying to use the same process
- If one app crashes, it doesn't affect the other 
- Each app can use different versions or configurations if needed

Yeah I need it; one wrapper for all my mcp tools for all clients and possibly all devices ! I asked skeet.build guys too

software artist | building /outpaint | ex: @coinbase ex: bisontrails | seeker of the flow state | artivilla.com

Something about me does not want to go through Skeet. I'm aware that MCP servers locally are currently are more like prototyping servers but I think it works fine for single user on a personal machine. I'm hoping the MCP team comes up with some novel way to reference your servers in a single path all your apps can point to.

what is skeet's business model? how do they stay in business? Do they have access to my data flow? Doesn't using Skeet add more latency to their centralized servers? 

Currently in Zed, I can't toggle on/off the number of tools and Having too many tools actually degrades the agent. This might be on the Zeplin client, but I'd want to enable/disable which tools I need per project.

I am kinda bullish on cli tools; now that agents can call them atleast in zed, Claude code etc!!! 

GitHub CLI is way more powerful that GitHub mcp wrappers !!