Oi
- 1 repo stars
- Updated June 29, 2026
- carhaix/oi-mcp
io.github.carhaix/oi is a MCP server that connects agents to your Oi teams, contexts, workflows, and tools over remote HTTP.
About
io.github.carhaix/oi is the official Oi Model Context Protocol bridge: a remote HTTP MCP server that lets coding agents read and drive your Oi setup—teams, contexts, workflows, tools, and more—from inside Claude Code, Cursor, or compatible clients. Developers who already orchestrate work on Oi.ioi.ai add this during Build agent-tooling so the agent shares the same organizational graph humans use, instead of duplicating prompts in repo-local files. Configuration is intermediate: you supply a required Bearer token (OAuth access token or exported organization API key) on the Authorization header for the streamable-http remote. It complements local repo skills rather than replacing them—think platform-backed context and workflow execution, not a single-file skill. Repository carhaix/oi-mcp documents integration patterns. Best when your agent stack and Oi tenants are the source of truth for multi-step AI workflows; skip if you only need static API docs without Oi tenancy.
- 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
Oi by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http oi https://api.oioioi.ai/mcp --header "Authorization: Bearer YOUR_TOKEN"Add your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Transport | HTTP |
| Auth | Required |
| Last updated | June 29, 2026 |
| Repository | carhaix/oi-mcp ↗ |
What it does
Expose your Oi organization—teams, contexts, workflows, and tools—to Claude Code via remote MCP over HTTP.
Who is it for?
Best when you're standardizing on Oi for AI teams, contexts, and workflows and want Claude Code or Cursor to use that live setup.
Skip if: Skip if you're without an Oi account or API token, or teams that need only local filesystem skills with no hosted orchestration.
What you get
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
By the numbers
- 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
README.md
Oi - MCPRecommended MCP Servers
0Latency MemoryPersistent memory layer for AI agents.
0nMCP — Universal AI API OrchestratorUniversal AI API Orchestrator — 1,554 tools, 96 services.
0xHumans Protocol MCPMCP for AI agents: financing, skills, lending on Base1k Patient Mcp1k patient MCP server
1trippulse1trip PULSE: 21-tool AI travel planner.
3D AI Agent Avatar3D AI Agent Avatar — render any GLB, give it a Solana wallet, a voice, and pump.fun powers.89How it compares
Remote AI-platform MCP bridge, not a single-purpose local CLI skill or a raw REST collection without MCP tools.
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.