Oli by Thommidhi: API and MCP reference

Reference for Oli by Thommidhi: a remote MCP server at thommidhi.com/mcp and a REST API at thommidhi.com/api/v1 (OpenAPI 3.1), with OAuth 2.1 (PKCE, client ID metadata documents, dynamic registration) or personal access keys, scoped tools, rate limits and request ids. It never returns YouTube data.

Endpoints

MCP (Streamable HTTP, JSON responses): https://thommidhi.com/mcp. REST: https://thommidhi.com/api/v1, OpenAPI at https://thommidhi.com/api/v1/openapi.json. Authorization server metadata: https://thommidhi.com/.well-known/oauth-authorization-server; protected resource metadata: https://thommidhi.com/.well-known/oauth-protected-resource/mcp.

Authentication

OAuth 2.1 authorization code with PKCE (S256 only), client ID metadata documents or dynamic client registration, tokens bound to the MCP resource, 1-hour access tokens and rotating 30-day refresh tokens. Or a personal access key a creator makes in their Lab, scoped and revocable.

Tools

Reads: get_my_creator_profile, get_my_terms, check_offer, list_my_deals, list_paid_briefs. Writes, each after the creator's yes: save_deal, update_deal, save_work_plan, and terms through propose_terms_update (a preview held for 30 minutes) then confirm_terms_update. Every tool carries explicit readOnlyHint, destructiveHint, idempotentHint and openWorldHint annotations. Prompts: set_up_my_terms, handle_an_offer, check_an_offer, brief_to_video, plan_my_shoot. Scopes: profile:read, terms:read, deals:read, briefs:read, deals:write, terms:write; the server enforces each on every call.

Data use and limits

Tools return only what the creator typed in Thommidhi and paid briefs offered to them; never YouTube data. 60 tool calls a minute and 3,000 a day per connection or key; 429 with Retry-After beyond that. Every response carries x-request-id.

Contact: hello@thommidhi.com