| ▲ | thellimist 7 hours ago | |
Nice! Compared both --- TL;DR CLIHUB compiles MCP servers into portable, self-contained binaries — think of it like a compiler. Best for distribution, CI, and environments where you can't run a daemon. mcpshim is a runtime bridge — think of it like a local proxy. Best for developers juggling many MCP servers locally, especially when paired with LLM agents that benefit from persistent connections and lightweight aliases. --- https://cdn.zappy.app/b908e63a442179801e406b01cf412433.png (table comparison) --- | ||
| ▲ | thellimist 7 hours ago | parent | next [-] | |
I was happy with playwright like MCPs that require the daemon so didn't convert them to CLIs. My use cases are almost all 3rd party integrations. Have you seen any improvements converting on MCPs that require persistency into CLI? | ||
| ▲ | _pdp_ 7 hours ago | parent | prev [-] | |
Nice. Love it. One important aspect of mcpshim which you might want to bring into clihub is the history idea. Imagine if the model wants to know what it did couple of days ago. It will be nice to have an answer for that if you record the tool calls in a file and then allow the agent to query the file. | ||
