Skip to main content
The server speaks standard MCP over Streamable HTTP. Any HTTP client can drive it; you just need to handle the JSON-RPC envelope, session id, and SSE framing.

Initialize

Save the Mcp-Session-Id response header — you’ll pass it on every subsequent call.

List tools

Call a tool

List / read resources

Uploaded files show up as resources/list entries with URIs of the form file://uploads/{chat_id}/{encoded-rel-path}. See MCP methods → resources.

Dynamic system prompt

Non-MCP clients can fetch the per-session system prompt over plain HTTP:
Stream it into the model’s system message. The response carries an X-Public-Base-URL header with the server’s public URL — use that when rewriting file links.

Python example (mcp SDK)

Managed Yambr

For managed Yambr, the same MCP endpoint is public at https://api.yambr.com/mcp/computer_use with Authorization: Bearer sk-yambr-.... Use the exact same initialize / tools/list / tools/call / resources/* calls shown above — just change the URL and the Bearer token. Your LLM traffic stays on your own provider (OpenAI, Anthropic, whatever); Yambr only provides the Computer Use tools. See LiteLLM gateway and Access model.

See also