Resources

Context resources exposed to MCP clients.

MCP clients should read resources before choosing IDs for tool calls.

URI	Contents
`epismo://context/current_user`	Current user/account/workspace JSON
`epismo://context/projects`	Projects accessible in the selected workspace
`epismo://context/users`	Workspace users visible to the caller
`epismo://context/agents`	Installed agents available for assignment

Task assignees can use user IDs or agent IDs. Workflow pack step assignees use human or agent IDs only.

Resource payloads

Resources return JSON. The current user resource includes the authenticated user ID, account ID, and workspace when the bearer token is workspace-scoped.

{
	"id": "user-id",
	"accountId": "account-id",
	"workspace": {
		"id": "workspace-id",
		"name": "Workspace name"
	}
}

Projects, users, and agents return arrays with IDs and display names. Use those IDs in tool arguments instead of asking an agent to infer IDs from visible labels.

Access fields

Mutation tools use scope and sharedWith. Create tools and epismo_track_apply require scope; update tools can omit scope and sharedWith to preserve existing access.

{ "scope": { "type": "personal" } }

{ "scope": { "type": "projects", "ids": ["project-id"] } }

Use sharedWith when private access should include specific users outside the selected project scope.

{
	"sharedWith": {
		"userIds": ["user-id"],
		"emails": ["teammate@example.com"]
	}
}

Search tools use scopes to choose where private results are searched.

{
	"scopes": [{ "type": "personal" }, { "type": "projects", "ids": ["project-id"] }]
}