The tool surface · Live today

Wire any agent into Opti knowledge.

16 live MCP tools cover list, fetch, and pack retrieval, plus a small write surface for logging signals and skill runs. Point any MCP-aware client at /partner/mcp with your partner API key and it can query everything documented on this site.

See connection setup16 tools, live today.

The call, end to end

Your agent→ MCP client config→ ESAI MCP server (/partner/mcp)→ Tool call (e.g. get-context-pack)→ Grounded knowledge back

Any MCP-aware client — Claude, GitHub Copilot, Cursor, or a custom in-house agent — that supports remote MCP servers can add this one via its own MCP settings: the /partner/mcp URL plus your partner API key. Once connected, every tool below is callable.

The flagship recipe: batch, don't trickle

get-module (includeProfileIndex) → get-profiles

Discover what a module has, then fetch the subset you actually need in one call — not one profile-at-a-time approval per fetch.

get-module (includeProfileIndex)→ (pick subset)→ get-profiles

What's a context pack

A context pack is a named, live-resolved, auth-scoped knowledge slice. A pack definition names a slice of one or more modules — it never stores profile text, only references. get-context-pack resolves that selection against the live module registry at request time and filters the result through your key's visibility rules.

list-context-packs→ get-context-pack→ get-knowledge-version (compareTo)→ Your agent's context

Example scenarios

try these