Setup
Connect a Streamable HTTP client through OAuth and verify context.
Add https://mcp.epismo.ai/ as a Streamable HTTP server in an MCP client. Authentication uses OAuth with the mcp scope. The MCP endpoint publishes protected-resource metadata that points the client to Epismo's authorization server.
GET https://mcp.epismo.ai/.well-known/oauth-protected-resource
GET https://api.epismo.ai/.well-known/oauth-authorization-serverA 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 Playbooks, Case input, 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 connecting, 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.
Tool schemas published by the server are authoritative for exact input fields. Every mutation takes an idempotency UUID, and mutations of an existing Case or Task require its latest expectedLockVersion.