Oi

MCP server: Oi

{
  "type": "streamable_http",
  "url": "https://api.oioioi.ai/mcp"
}

Starts a sticky Oi Context session for the current Cursor thread.

Use this command when the user wants a named Context to stay active for the thread.

Examples:
- `/session software-engineer`
- `/session product-manager`

Call `oi_contexts_start_session` with:
- `contextId`: the named Context exactly as provided by the user

After starting the session, confirm that the Context session is active for the current thread.

Use a named Oi Context for a concrete task.

Use this command when the user provides a Context name and a task.

Examples:
- `/context designer review this onboarding flow`
- `/context software-engineer explain this auth change`
- `/context growth-lead find monetization opportunities in this pricing page`

Call `oi_contexts_use` with:
- `contextId`: the named Context exactly as provided by the user
- `prompt`: the remaining task text

If the user only gives a Context name and no task, ask for the task or use `oi_contexts_start_session` if the intent is to load reusable context only.

Lists the Contexts available from the connected Oi organization.

Use this command when the user wants to see which Contexts are available before choosing one.

Call `oi_contexts_list`.

Return the available Contexts clearly and briefly for the user.

Loads Oi Contexts and routes context-aware requests through the connected MCP server.

---
name: oi
description: Use Oi to load Contexts from the connected MCP server. Use when the user asks for Oi directly, names a Context, wants sticky Oi context in the current thread, or starts with `oi`.
---

# Oi

## When to use

- When the user says `oi ...` or `use Oi ...`
- When the user names one or more Oi Contexts
- When the user wants Oi context loaded into the current thread
- When the user wants to list available Contexts before choosing one

## Instructions

1. Treat `Oi` and `oi` as the same plugin surface when plain-text routing is available.
2. If the user wants to browse available Contexts, call `oi_contexts_list`.
3. If the user names a Context and provides a task, call `oi_contexts_use`.
4. Pass the Context selector through unchanged as `contextId`.
5. Preserve `+` for multiple Contexts and `@2` or `@v2` for versions.
6. If the user wants sticky context for the current thread, call `oi_contexts_start_session`.
7. Only use `oi_contexts_recommend` when the user does not know which Context to use or the provided selector cannot be resolved.
8. Prefer Oi MCP operations over treating the request as plain English when the user clearly intends to use Oi.