obot README

项目的 README,来自 github.com/obot-platform/obot。合并为一个 markdown 文件:README.md。

Obot

Obot is an open-source platform for organizations to manage, secure, and govern their AI ecosystems. It provides shared infrastructure for connecting AI clients to models and tools, distributing approved MCP servers and skills, managing agent access and credentials, running hosted AI workloads, and recording activity across hosted services and user devices.

Obot does not require an organization to standardize on a single AI client, model provider, or tool ecosystem. Desktop agents and tools such as Claude Code, Codex, Cursor, VS Code, and other IDEs and CLIs can use the parts of the platform that apply to them.

Architecture

Obot Platform architecture

The Obot Platform connects AI activity on user devices with services managed by or proxied through Obot Server.

On user devices, desktop agents and tools connect to Obot gateways, while Obot Sentry scans, audits, and enforces policy on AI activity taking place on the device. The Obot CLI lets users and AI clients discover, install, and manage approved MCP servers and skills.

Obot Server provides:

Obot integrates with remote MCP servers, LLM providers, S3-compatible object storage, Git providers, and auth providers.

Core Capabilities

MCP Gateway

The MCP Gateway is a single governed entry point to every MCP server a user is allowed to reach.

LLM Gateway

The LLM Gateway presents provider-compatible endpoints that AI clients use to reach approved models.

Hosted MCP Servers

Obot can run MCP servers itself, in isolated execution environments outside the main Obot Server process.

Claude Environments

Claude Environments runs Claude cloud sessions on an organization's own Kubernetes infrastructure. Users keep working in Claude, while Obot controls who can start a session and what that session can reach. Claude Environments is experimental and disabled by default. Support for more agent platforms is planned.

MCP and Skills Registries

The MCP and Skills Registries centralize the discovery, installation, and management of MCP servers and Agent Skills.

Obot CLI and Skill

The Obot CLI brings approved MCP servers and skills to users and their local AI clients, and the Obot skill teaches an agent to use the CLI itself.

Obot Sentry

Obot Sentry extends Obot governance to AI activity occurring directly on user devices. Device Management is currently beta.

Identity and Access Control

Obot governs who can reach each part of the platform, and with which credentials.

Audit Logs and Visibility

Obot correlates activity across MCP servers, LLM providers, hosted workloads, and user devices.

Getting Started

For local development or evaluation, run Obot with Docker:

docker run -d \
  --name obot \
  -p 8080:8080 \
  -v obot-data:/data \
  -v /var/run/docker.sock:/var/run/docker.sock \
  -e OBOT_SERVER_ENABLE_AUTHENTICATION=true \
  -e OBOT_BOOTSTRAP_TOKEN=<token> \
  ghcr.io/obot-platform/obot:latest

The bootstrap token must be at least six characters. If you omit OBOT_BOOTSTRAP_TOKEN, Obot generates one and prints it in the container logs.

Open http://localhost:8080, sign in with the bootstrap token, and configure an authentication provider. For evaluation, the built-in Local provider lets you create user accounts without setting up an external identity provider. A model provider is required only when using the LLM Gateway. The UI is available in English, Japanese, Korean, and Simplified Chinese.

This Docker configuration mounts the host Docker socket so Obot can launch hosted MCP servers as sibling containers. Use it only for development, evaluation, or trusted single-tenant environments. Use the Kubernetes deployment for production or multi-tenant installations.

See the Installation Guide for Kubernetes, external PostgreSQL, encryption, authentication, and production configuration.

Design and architecture

Significant changes begin as Obot Design Proposals so the architecture can be discussed before implementation. Architectural decisions that ship are recorded as concise Architecture Decision Records in this repository.

An ODP captures the proposed design and the discussion that shaped it. An ADR records the durable decision reflected in the implementation.

Documentation and Community

License

Obot is licensed under the MIT License. Every edition, including Obot Community and Obot Enterprise, runs the same open source code from the same container image, and editions differ only in their license key. See Editions and licensing for user and device limits and what each edition includes.

obot (obot-platform/obot)

正在搜索数据库…

1.2K ·GitHub
这是什么?Obot 是一个开源平台,可帮助组织管理、保护并治理其整个 AI 生态系统,包括将 AI 客户端连接到模型和工具、分发已批准的 MCP 服务器和技能、管理智能体凭证,以及审计托管服务和用户设备上的活动。
Obot 是单一应用,还是一组服务?它是由多个相互连接的组件构成的平台:Obot Server(包括 MCP 和 LLM 网关、注册中心、身份与审计服务)、Obot CLI,以及用于监控用户设备上 AI 活动的 Obot Sentry。
怎样才能让它运行起来?在本地开发或评估时,可以用 Docker 运行 Obot,并使用生成的引导令牌登录;如果用于生产环境或多租户场景,则应改为将 Obot 部署到 Kubernetes。
试用时需要模型提供商的 API 密钥吗?基本评估不需要。内置的 Local 身份提供商允许你无需外部身份系统即可创建账户;只有在想使用 LLM 网关时,才需要模型提供商的密钥。
Docker 部署方式可以直接用于生产环境吗?不可以。Docker 部署会挂载宿主机的 Docker 套接字来启动同级容器,仅适用于开发、评估或可信的单租户环境;生产和多租户部署则需要使用 Kubernetes。
这个平台面向哪些用户?它面向需要统一管控 AI 工具、模型以及众多用户和设备上智能体访问权限的组织,而不是只想找一个单独助手的个人开发者。
什么是 vMCP?vMCP(虚拟 MCP 服务器)可以将一个或多个目录中的 MCP 服务器整合到一个端点之后,这些底层服务器可以由 Obot 托管,也可以在外部运行;它还可以固定到某个特定的目录快照。
Obot Sentry 有什么作用?Obot Sentry 运行在用户设备上,用于扫描、审计并执行本地 AI 活动的策略,包括盘点已安装的 AI 客户端和工具、记录本地工具调用,并且(处于实验阶段)对 Claude Code、Codex、Cursor 和 Kiro 等客户端实施工具调用白名单。
哪些 AI 客户端和 IDE 可以与 Obot 配合使用?Obot 不要求统一使用某一种客户端。Claude Code、Codex、Cursor、VS Code 以及其他 IDE 和 CLI 工具,都可以使用平台中与自身相关的部分功能。
Obot 界面支持哪些语言?目前 Obot 界面支持英语、日语、韩语和简体中文。
大小
57.8 MB
星标
1.2K
时长
2年
提交 · 90 天