- CollectionTool Access & Integration
- Classificationagent-native
- LicenseMIT
- MCPAvailable
- Agent SkillUnavailable
- InterfacesMCP · REST · http · API
What it does
Obot is a single deployable that bundles four MCP-related concerns into one stack: hosting (run MCP servers in a managed sandbox — Node.js, Python, or container-based), registry (catalog and discover MCP servers and their tools), gateway (front everything with a unified URL with OAuth, RBAC, and usage policies), and an optional chat client (a generic agent UI that consumes the gateway).
For teams that want a private, in-cluster MCP plane — instead of stitching together Smithery for the registry, ToolHive for the runtime, and a hand-rolled gateway — Obot gives them all four in one repo with Kubernetes-ready Helm charts and OAuth 2.1 baked in.
Agent-facing interfaces
- Catalog protocols: MCP, REST, http, API
- MCP: ✅ Available — Obot is an MCP platform; everything it does is exposed over MCP.
- Agent Skill: ⚠️ Not yet published.
- Onboarding type:
mcp
How agents onboard
# Self-hosted (Kubernetes / Docker):
helm install obot obot/obot
# or:
docker run -p 8080:8080 ghcr.io/obot-platform/obot:latest
# Then point any MCP-compatible agent at the gateway URL:
https://<obot-host>/mcp
See the full onboarding section in the dossier.
Protocol surface
| Interface | Detail |
|---|---|
| MCP (Streamable HTTP) | Unified gateway URL for tool discovery + invocation |
| REST admin API | Server registration, token issuance, policy management |
| OAuth 2.1 | Auth code + client credentials flows |
| Helm chart / Docker image | Kubernetes-native deploy |