botz-mcp — a living skill & subagent platform for your AI agents
botz-mcp gives every AI agent in your organisation a shared, governed corpus of Agent Skills and subagent definitions, delivered over the Model Context Protocol (MCP). Your agents discover capabilities they don't have, download them on demand, and — when nothing fits — ask the platform to author a new one, conversationally.
What it offers
| Capability | What your agents get |
|---|---|
| Semantic discovery | Describe a need in plain language; get the best-matching skills or subagent roles, plus a clear verdict on whether the need is already covered. |
| On-demand skills | Full skill instructions load only when needed, served as compact CRUX documents that keep your agents' context windows small. |
| Skill creation | When a need isn't covered, the platform authors a new skill from your agent's brief — asking clarifying questions mid-request when the brief is thin, and optionally letting the requester review the draft before it is published. |
| Subagent definitions | Reusable specialist personas your agent can install and spawn — rendered automatically for your client (Cursor, Claude Code, or a neutral format) with the exact file path to install them at. |
| Zero-drift pinning | Every artifact has a permanent id and immutable version history. Your agents pin what they use; nothing changes underneath them without notice. |
| Quality that compounds | Agents report whether a skill worked, optionally with measured cost and speed. Rankings improve for everyone — and search can optimise for quality, speed, or cost. |
How consumption works
- Search — the agent describes the capability it needs.
- Get — it downloads the best match and applies it.
- Feedback — it reports the real outcome.
- Request — if nothing covered the need, it briefs the platform and a new skill is created for the whole organisation.
All of this is orchestrated invisibly by the botz-mcp client skill — you install it once and simply ask your agent for work. Start with Install & connect.
Enterprise operator? SSO (GitHub, Google, Microsoft Entra
ID), roles, teams, and configuration delegation are covered in the
enterprise documentation (sign-in required
when SSO is configured).