Setup

Connect a Streamable HTTP client through OAuth and verify context.

https://mcp.epismo.ai/ — Streamable HTTP; OAuth scope: mcp.

Public catalog browsing, public case, record, popularity, and handoff-graph reads, and UUID-based public playbook reads work without OAuth and cost 0 credits. Writes, private work, non-empty search queries, aliases, and identity resources require Authorization: Bearer <oauth_access_token>. Protected calls return a 401 OAuth challenge; connecting or listing tools alone does not require login.

GET https://mcp.epismo.ai/.well-known/oauth-protected-resource
GET https://api.epismo.ai/.well-known/oauth-authorization-server

A conforming client should discover these documents, register when necessary, use Authorization Code with PKCE, and request only the scopes it needs. Do not paste access tokens into case input, playbooks, records, URLs, or chat prompts.

The hosted server is stateless. It creates a fresh transport for each HTTP request and does not issue Mcp-Session-Id; clients must not depend on session affinity. Tool results and Epismo IDs—not transport session state—are the durable continuation mechanism.

After authenticating for protected work, read epismo://context/current_user and, when using a workspace, epismo://context/teams. This confirms which user and workspace the OAuth token represents before the agent creates ACLs or assigns work. Clients without MCP resource access can use epismo_team_list to resolve team IDs.

Tool schemas published by the server are authoritative for exact input fields. Provide an idempotency UUID when the tool schema requires one; mutations of an existing case or task require its latest expectedLockVersion.