How to Use It Well
- Setup time ~8 minutes (npm install + connect one server)
- GitHub stars + forks (verified): see Source & Thanks
- Supports persistent named sessions (e.g.,
@test) for repeated tool calls
Use mcpc as the thin waist: everything agent-side is a Bash tool, everything server-side is MCP. That makes it easier to standardize sessions, auth, logging, and scripting patterns across teams.
FAQ
Q: Why a CLI for MCP? A: Agents already have a universal interface—shell access. A CLI lets agents use MCP without custom function wiring.
Q: Is it interactive or scriptable? A: Both. It has an interactive shell mode and a JSON output mode for pipelines.
Q: How do I keep credentials safe? A: Use OAuth profiles as described in the README and run MCP proxying/sandboxing if you share a machine with multiple agents.