Tokens

Epismo exposes product-specific token endpoints for CLI and MCP clients.

CLI tokens

POST /v1/cli/tokens
Authorization: Bearer <token>
Content-Type: application/json
 
{ "workspaceId": "workspace-id" }

The response includes accessToken, refreshToken, tokenType, expiresIn, and scope. Use the access token as EPISMO_TOKEN in CI.

If workspaceId is omitted, the token uses the authorized request context. For CI, prefer an explicit workspace ID.

MCP tokens

MCP tokens are used by MCP clients that connect to the Epismo MCP server.

Issuing an MCP token requires resource, and the value must be an absolute http or https URL for the MCP server resource. Refreshing an MCP token requires both refreshToken and the same kind of absolute resource URL.