Main
Use ShibaClaw when you want one operational surface for many channels/providers and an MCP plug-in ecosystem.
Start with Docker Compose, validate auth + runtime, then add MCP servers from the Settings flow.
Quantitative anchors from the README (22 providers, 11 channels) help gauge feature scope.
Source-backed notes
- README advertises 22 providers and 11 chat channels plus built-in WebUI, cron/heartbeat, and MCP support.
- Quickstart includes Docker Compose and a
pip install shibaclawpath. - Docs describe MCP tools being registered with an
mcp_<server>_<tool>naming pattern.
FAQ
- Do I need Docker?: No, but Docker Compose is the quickest path; the README also shows pip install.
- How does MCP help?: MCP lets you attach external tools/data sources without modifying core code.
- How do I debug?: Use container logs and the channel/status commands described in the docs.