oi.connections.listLABSCO SUMMARY
Authoring and running sit on the same surface.
Most platform servers let an agent invoke what a human already built. Here the lifecycle operations are exposed too, so a Workflow or Guardrail can be created and revised from inside the session that will use it — which is the difference between an agent that runs your automation and one that extends it. The reporting tools point the same way: usage and effectiveness are queryable, so what gets built next can be informed by what is actually being used.
What it is
The hosted MCP server for Oi, reached by URL rather than installed. It exposes Oi's building blocks — Contexts, Workflows, Skills, Guardrails, Connections and durable memory — to an MCP client, covering both using them and authoring them.
What you get
- Identity and routing for the calling client
- Contexts, Workflows and available Skills discovered and executed
- Authoring and lifecycle operations over Contexts, Workflows, Skills and Guardrails, so they can be created and changed from the same session that runs them
- Stable Connection discovery and execution —
oi.connections.list,oi.connections.get,oi.connections.use - Durable memory updates at two scopes: Org Brain and User Brain
- Usage reporting for Contexts and Workflows, plus cross-surface effectiveness reporting
Requirements
An Oi account and a bearer token. Point your client at https://api.oioioi.ai/mcp over streamable HTTP with an Authorization header — either an OAuth access token obtained through the Oi app, or an exported organization API key. Nothing to install locally. The repository itself holds the registry metadata, published as oi-mcp (2.0.0).
Setup effort
Follow the published steps
USE CASES
01
Running an existing workflow from your assistant
Discover the Contexts and Workflows available on your org and execute the right one without switching to the Oi app.
02
Reaching a system Oi is already connected to
List the stable connections, read one, and use it — rather than wiring up a second integration for the same system.
03
Building the automation while you are describing it
Author a Context, Workflow, Skill or Guardrail in the same conversation where you worked out that you needed it.
04
Seeing what is actually being used
Pull usage and cross-surface effectiveness reporting to decide what to keep, fix or retire.
3 tools
Listed in project docs. Your client may show a different list.
oi.connections.getoi.connections.useBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
INSTALLATION
Connect your client
Server setup
This is a hosted (remote) MCP server — nothing is installed locally. Point your MCP client at the server URL:
ENDPOINT URL
https://api.oioioi.ai/mcpAuthenticate either with OAuth via the Oi app (https://app.oioioi.ai), or by sending an Authorization: Bearer <YOUR_API_TOKEN> header
