Obot은 조직이 AI 생태계를 관리, 보안 및 거버넌스할 수 있는 오픈소스 플랫폼입니다. AI 클라이언트를 모델 및 도구와 연결하고, 승인된 MCP 서버와 기술을 배포하며, 에이전트 접근 및 자격 증명을 관리하고, 호스팅된 AI 워크로드를 실행하며, 호스팅 서비스와 사용자 기기 간 활동을 기록하는 공유 인프라를 제공합니다.

Obot은 조직이 단일 AI 클라이언트, 모델 제공자, 도구 생태계에 표준화할 필요를 요구하지 않습니다. Claude Code, Codex, Cursor, VS Code 및 기타 IDE 및 CLI와 같은 데스크톱 에이전트와 도구들은 해당 플랫폼의 일부 부분을 사용할 수 있습니다.

건축

Obot 플랫폼은 사용자 기기에서의 AI 활동과 Obot Server가 관리하거나 프록시하는 서비스와 연결합니다.

사용자 기기에서는 데스크톱 에이전트와 도구가 Obot 게이트웨이에 연결되며, Obot Sentry는 기기에서 발생하는 AI 활동에 대한 정책을 검사, 감사 및 집행합니다. Obot CLI는 사용자와 AI 클라이언트가 승인된 MCP 서버와 기술을 발견, 설치 및 관리할 수 있게 합니다.

오봇 서버는 다음과 같은 서비스를 제공합니다:

• MCP 서버 및 모델 제공자에 대한 통제된 접근을 위한 MCP 및 LLM 게이트웨이.

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

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:

• MCP and LLM gateways for controlled access to MCP servers and model providers.
• Isolated execution for hosted MCP servers and Claude Environments sessions.
• Platform services for identity and access control, including permissions and secrets.
• Correlated audit logs of AI activity across the platform.
• MCP and Skills registries built on curated Git-backed catalogs.

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.

• Expose MCP servers through virtual MCP servers (vMCPs), which combine one or more catalog servers behind a single endpoint, whether those servers are hosted by Obot or run outside it.
• Reach remote MCP servers on private networks through MCP tunnels, which connect outbound to Obot so no inbound port has to be opened.
• Pin each vMCP component to a snapshot of its catalog entry, so catalog changes take effect only through an explicit upgrade.
• Control server and tool access by user or identity-provider group through vMCP profiles.
• Enable tool search on large vMCPs so clients search for and call tools without loading every tool definition into the model’s context.
• Chat with and call tools on any vMCP you can access using the built-in MCP tester.
• Manage MCP OAuth, user and shared credentials, and Kubernetes secret bindings.
• Inspect, reject, or modify MCP requests and responses with MCP, webhook, or built-in credential filters.

LLM Gateway

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

• Connect external AI clients to OpenAI, Anthropic, Amazon Bedrock, Azure, and Generic Responses Compatible providers.