Oi Ai
'Oi build this feature for me'.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only
What it can do
- Oi.Auth.Whoami: Return the current Oi MCP authentication, organization context, billing plan, current limits, and billing link for debugging. Use this when the user asks who Oi is authenticated as, wh
- Oi.Workflows.List: List the Oi workflows available to this organization. Use this when the user asks what workflows exist or says oi workflow/wf without enough task detail to select one.
- Oi.Skills.List: List a paginated preview of Oi Skills available to this organization. Skills are reusable task instruction documents exposed through Oi MCP. ## Plan and Billing Current organization pl
What data it sees
Do you need an account
No: the server works without sign-in
'Oi build this feature for me'. Oi exposes your collaborative team's private agent contexts, guardrails, data connections and workflows, so the same reusable context can be used across ChatGPT, Codex, Claude, Cursor, and other MCP-compatible clients.
Server tool list (38)
Raw names from tools/list. Only developers need these.
| oi.auth.whoami | Return the current Oi MCP authentication, organization context, billing plan, current limits, and billing link for debugging. Use this when the user asks who Oi is authenticated as, which organization this MCP session is using, what plan or limits apply, or why Codex/ChatGPT may be seeing different Oi data. Does not return access tokens, refresh tokens, or secrets. ## Plan and Billing Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities. |
| oi.workflows.list | List the Oi workflows available to this organization. Use this when the user asks what workflows exist or says oi workflow/wf without enough task detail to select one. |
| oi.skills.list | List a paginated preview of Oi Skills available to this organization. Skills are reusable task instruction documents exposed through Oi MCP. ## Plan and Billing Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities. |
| oi.workflows.get | Return the reusable compiled prompt scaffold for a specific Oi workflow by workflowId. Prefer oi.workflows.use when the user has a concrete task. |
| oi.skills.search | Search installed and marketplace Skills by need, title, tag, or category. ## Plan and Billing Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities. |
| oi.workflows.start-session | Load a specific Oi workflow as reusable session context for the current client thread. The selectors wf, workflow, and workflows are reserved Workflow type selectors, not Workflow ids; strip them and use this Workflow session path. Returns compiled workflow context text only, with no user task attached. |
| oi.workflows.create | Create a private Oi Workflow draft in the current organization from required workflow fields and ordered Context steps. Use oi.contexts.search first when an agent is unsure which Context ids or slugs to include. This creates a draft only; it does not release or publish the Workflow. ## Plan and Billing Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities. |
| oi.workflows.update | Update an existing private Oi Workflow draft in the current organization by workflowId. Send the complete draft shape, including ordered Context steps. Use oi.workflows.get first if the agent needs to inspect the current workflow. This updates the draft only; it does not release or publish the Workflow. ## Plan and Billing Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities. |
| oi.workflows.use | Use Oi Workflows for a concrete task. This is the primary tool for requests like oi use launch-readiness audit this release or oi use feature-discovery plan this launch. Pass workflowId only for a specific workflow; otherwise omit it and Oi selects the best installed workflow. The selectors wf, workflow, and workflows are reserved Workflow type selectors, not Workflow ids; strip them and use this Workflow path. Returns an execution-ready prompt with the user request appended under ## User Request. |
| oi.skills.create | Create a private Oi Skill in the current organization. A Skill is a reusable task instruction document. ## Plan and Billing Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities. |
| oi.skills.update | Update an existing private Oi Skill draft. Pass action=release to release the updated draft. ## Plan and Billing Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities. |
| oi.skills.publish | Publish a released Oi Skill to the marketplace for the current organization. |
| oi.skills.get | Return an installed Oi Skill as an execution-ready reusable instruction document without appending a task. Prefer Use Skill when the user has a concrete task. |
| oi.skills.use | Use an installed Oi Skill for a concrete task. Returns an execution-ready prompt containing the Skill document and user request. |
| oi.contexts.list | List a paginated preview of Oi Contexts available to this organization. This is the primary listing tool for requests like oi list, oi list contexts, $Oi list contexts, or show available Contexts in Oi. Treat oi, and $Oi as equivalent invocation forms. This returns at most 10 records and is not exhaustive. If the user names an Context or selector, call oi.contexts.use with that raw contextId instead of using this list to pre-validate existence. ## Plan and Billing Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities. |
| oi.contexts.search | Search Contexts by need, title, tag, category, or organization. This uses the app-global search path: organization/private results are returned first, then public marketplace results fill the remaining slots. Use this when the user is unsure which Context exists or wants to discover a Context before creating a Workflow. ## Plan and Billing Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities. |
| oi.contexts.create | Create a private Oi Context in the current organization. Use this only when the user explicitly asks to create or import a Context and has confirmed the source license permits reuse. Prefer markdown content in `content`; use `privateContent` for organization-private instructions that should not be published. ## Plan and Billing Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities. |
| oi.contexts.get | Return the reusable compiled prompt for a specific Oi Context. Prefer oi.contexts.use when you already have a concrete task. |
| oi.contexts.update | Update an existing private Oi Context draft in the current organization, including plaintext license metadata. Pass action=release to release the updated draft. ## Plan and Billing Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities. |
| oi.guardrails.list | List a paginated preview of private Oi Guardrails in the current organization. |
| oi.guardrails.create | Create a private Oi Guardrail in the current organization. Use this only when the user explicitly asks to create or import a Guardrail and the source license permits reuse. Prefer markdown content in `content`; `publish: true` releases the initial version first. |
| oi.guardrails.get | Return a private Oi Guardrail record for the current organization. |
| oi.guardrails.update | Save changes to a Guardrail draft. If there is an open draft, this updates it; otherwise it creates the next draft version. `publish: true` releases the draft first. |
| oi.guardrails.delete | Archive and disable a private Oi Guardrail in the current organization. This is not a physical database delete. |
| oi.guardrails.release | Release a private Oi Guardrail in the current organization. |
| oi.guardrails.publish | Publish a private Oi Guardrail in the current organization. |
| oi.guardrails.unpublish | Unpublish a private Oi Guardrail in the current organization. |
| oi.contexts.start-session | Load one or more Oi Contexts as reusable session context for the current client thread. The selectors ctx, context, and contexts are reserved Context type selectors, not Context ids; strip them and use this Context session path. Returns compiled context text only, with no user task attached. |
| oi.recommend | Recommend the best Oi Context or Workflow for a prompt. Use this when the user asks oi recommend or wants help choosing the most suitable reusable setup before running it. |
| oi.contexts.use | Use Oi Contexts for a concrete task. This is the primary tool for requests like oi designer review this flow, oi ctx growth-lead inspect pricing, or $Oi context product-manager review this roadmap. Treat oi, and $Oi as equivalent invocation forms. When the user names one or more Contexts, pass the raw selector unchanged as contextId, including + multi-context selectors of up to 3 Contexts and @2 or @v2 version pins, for example head-of-product@3+gtm-strategist+staff-engineer. The selectors ctx, context, and contexts are reserved Context type selectors, not Context ids; strip them and use this Context path. The selectors workflow, workflows, and wf are reserved for Workflows, not Contexts; use the Workflow path instead of longer Context chains. Do not first list contexts or treat a missing list preview item as absent. Without contextId, Oi routes implicitly. Returns an execution-ready prompt with the user request appended under ## User Request. ## Plan and Billing Current organization plan: Business. Current limits: 10,000 seats; 10,000 private Guardrails; 10,000 private Skills; 10,000 private Contexts; 10,000 private Workflows; 10,000 Connections; 10,000 API keys; 1,000,000 Agent messages per day; 1,000,000 Agent messages per month. Billing and upgrades: https://app.oioioi.ai/dashboard/organization/billing. When a user asks for work that exceeds the current plan or an unavailable paid capability, do the portion available on the current plan, clearly say what is blocked by the plan, and include the billing link for upgrading. Do not invent exceptions, temporary limit increases, prices, or hidden capabilities. |
| oi.contexts.save-draft-feedback | Save confirmed durable feedback into the active private Context draft for a single latest Context. Do not use this for multi-context selectors or version-pinned Contexts. When runtime instruction updates are enabled, Oi may save confirmed future guidance under Private using subheadings if needed. Structured-only metadata such as suggested prompts, categories, tags, platform instructions, and capabilities stays preserved unless another structured write path updates it. Only use it after the user confirms, and only for repeated corrections or updated logic that should change future behavior. Never use it for one-off task details, temporary debugging context, secrets, credentials, or other sensitive information. |
| oi.brain.save-feedback | Propose or save a direct durable update into Org Brain or User Brain. Use this for requests like update our org brain, add this to Brain, remember this for the organization, save this as team memory, or update my private Brain. Do not create or update Contexts or Workflows when the user asks to update Brain unless they explicitly ask for those surfaces. For the smoothest UX, call with scope=auto and confirmed=false when you notice a durable memory or need scope confirmation; Oi will return a confirmation prompt and saveArguments. If the user has already explicitly asked to update Org Brain or User Brain with specific content, choose scope=organization or scope=user and set confirmed=true. Use scope=organization for organization-wide facts, vocabulary, policies, approval rules, shared project context, or repeated team workflows that should apply to the current organization. Use scope=user for personal preferences, recurring individual working style, or user-specific context that should follow the authenticated user. Confirmed Brain updates use an AI markdown update pass: compare the latest Brain markdown with the requested change, preserve existing structure, create headings when needed, add only missing guidance, and make the smallest accurate edit. Return a simple saved response when a new version is released, or a simple no-change response when the requested guidance appears to already exist in some capacity. Never save one-off task details, guesses, secrets, credentials, sensitive private data, or unconfirmed assumptions. |
| oi.guardrails.confirm | Confirm a triggered Oi Guardrail for a blocked Context or Workflow request and continue. The requestId carries the original Context or Workflow routing details. |
| oi.usage.report | Attach detailed token accounting and runtime metadata to a previously issued Oi Context or Workflow usage event without storing prompt text. Prefer usageEventId from the prior Oi tool result; optional contextId or workflowId can be included for client-side clarity but usageEventId is authoritative. |
| oi.effectiveness.report | Report what happened after an Oi-assisted task completed. Use this after calling an Oi Context, Workflow, Skill, Connection, or Guardrail tool when you know whether the result was accepted, retried, saved, copied, completed, or rejected. Prefer usageEventId from the prior Oi tool result; traceId may also be used when available. Do not send raw prompt text; send a short redacted taskSummary only when useful. |
| oi.connections.list | List the Connections installed for the current Oi organization. Use this stable discovery tool before selecting a provider or connection instance; adding provider capabilities does not change this tool schema. |
| oi.connections.get | Return the live capabilities and input contracts for one installed Connection. Capabilities are dynamic data, so new provider actions do not require publishing new MCP tools. |
| oi.connections.use | Execute a capability returned by Connections Get. Pass the provider, dynamic action name, and its arguments. Oi resolves credentials, applies organization policy, verifies write targets, requires confirmation for writes, and audits execution without exposing provider secrets. |