
Oi
io.github.carhaixPublished by GitHub account carhaixv2.0.0Updated Oct 24, 2026
Access Oi Contexts, Workflows, Skills, Guardrails, Connections, and reporting tools.
Overview
Hosted Oi MCP server that lets an assistant discover, run and author Oi Contexts, Workflows, Skills, Guardrails and Connections, plus memory and reporting.
- What you can do
- Discover and execute Oi Contexts, Workflows and available Skills
- Author and manage the lifecycle of Contexts, Workflows, Skills and Guardrails
- Find and run stable Connections through list, get and use operations
- Update durable Org Brain and User Brain memory
- Pull Context and Workflow usage reporting and cross-surface effectiveness reports
- Resolve identity and routing for the connected Oi organization
- When to use it
- Use it when your team already works in Oi and wants an assistant to run or build its Contexts, Workflows, Skills and Guardrails, reuse saved Connections, and read usage reporting from the same chat.
- Requirements
- A remote MCP endpoint at the Oi API; no local package. Authentication is required via OAuth through the Oi app or an Authorization bearer token holding an OAuth access token or an exported Oi organization API key. Network access to the Oi service.
Installation
In SourceWeft
- Open Oi in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.carhaix%2Foi/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"oi": {
"type": "http",
"url": "https://api.oioioi.ai/mcp"
}
}
}README
[Oi Logo] Oi - MCP
Registry metadata for the hosted Oi MCP server, including Contexts, Workflows, Skills, Guardrails, Brain, Connections, and reporting.
Connect
Server URL: https://api.oioioi.ai/mcp
Authentication:
- OAuth via the Oi app
Authorization: Bearer <api-token>
Tool surface
- Identity and routing
- Context, Workflow, and available Skill discovery and execution
- Context, Workflow, Skill, and Guardrail authoring/lifecycle operations
- Stable Connection discovery and execution through
oi.connections.list,oi.connections.get, andoi.connections.use - Org Brain and User Brain durable-memory updates
- Context/Workflow usage reporting and cross-surface effectiveness reporting
Source: README.md at commit 724ee41
Tools
0Version history
1- v2.0.0LatestSep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.