Oi
Expose your Oi organization—teams, contexts, workflows, and tools—to Claude Code via remote MCP over HTTP.
Overview
io.github.carhaix/oi is a MCP server for the Build phase that connects agents to your Oi teams, contexts, workflows, and tools over remote HTTP.
What is this MCP server?
- Remote streamable-http endpoint at https://api.oioioi.ai/mcp (v0.2.0)
- Bearer Authorization for OAuth access tokens or exported Oi organization API keys
- Unified access to Oi teams, contexts, workflows, tools, and related setup
- Hosted MCP—no local stdio package required in registry metadata
- Official guide at oioioi.ai for Oi MCP onboarding
- Registry version 0.2.0
- Remote URL https://api.oioioi.ai/mcp with required secret Authorization header
- GitHub repository https://github.com/carhaix/oi-mcp
Community signal: 1 GitHub stars.
What problem does it solve?
Your agent works blind to Oi-hosted teams and workflows, forcing you to copy context by hand into every coding session.
Who is it for?
Solo builders standardizing on Oi for AI teams, contexts, and workflows who want Claude Code or Cursor to use that live setup.
Skip if: Builders without an Oi account or API token, or teams that need only local filesystem skills with no hosted orchestration.
What do I get? / Deliverables
After you add the remote MCP URL with a valid Bearer token, the agent can call Oi-backed tools and context from the same MCP session.
- Live MCP connection to Oi teams, contexts, workflows, and tools
- Agent sessions that reuse Oi setup instead of duplicated local prompt packs
- Documented integration path via oioioi.ai Oi MCP guide
Recommended MCP Servers
Journey fit
Build is canonical because you connect an external AI ops platform into your agent stack while assembling product and automation tooling. Agent-tooling fits remote streamable-http MCP that surfaces Oi teams, contexts, workflows, and registered tools to the coding agent.
How it compares
Remote AI-platform MCP bridge, not a single-purpose local CLI skill or a raw REST collection without MCP tools.
Common Questions / FAQ
Who is io.github.carhaix/oi for?
Developers using Oi (oioioi.ai) who want MCP-enabled agents to access organization teams, contexts, workflows, and tools.
When should I use io.github.carhaix/oi?
Use it in Build while wiring agent-tooling so implementation sessions can read Oi configuration and invoke platform workflows without manual exports.
How do I add io.github.carhaix/oi to my agent?
Register remote MCP https://api.oioioi.ai/mcp (streamable-http) and set Authorization Bearer to your OAuth token or exported Oi organization API key.