Tools

Pack, alias, and track tools exposed by the Epismo MCP server.

Pack tools

Tool	Purpose
`epismo_pack_create`	Create a workflow or context pack
`epismo_pack_update`	Patch a pack by UUID, alias, share URL, or hub URL
`epismo_pack_get`	Read outline, selected nested content, or full content
`epismo_pack_search`	Search workflow/context packs
`epismo_pack_like`	Like or unlike a pack
`epismo_pack_delete`	Delete a pack and aliases you own that point to it

For large packs, read outline data first. Then fetch selected stepIds or blockIds.

{
	"reference": "@repo-onboarding"
}

The outline response includes contentIndex.stepIds or contentIndex.blockIds. Use those IDs for selective fetches.

{
	"reference": "@repo-onboarding",
	"blockIds": ["b001", "b003"]
}

Use full=true only when the client needs every block or step.

epismo_pack_search consumes credits. Before passing a large pack to an agent, use the outline to narrow the content it actually needs.

Pack creation example

{
	"type": "context",
	"scope": { "type": "projects", "ids": ["project-id"] },
	"title": "Repository onboarding",
	"blocks": [
		{
			"title": "Local setup",
			"content": "Run npm install, then start the services you need."
		}
	]
}

For workflow packs, pass steps instead of blocks. Workflow step assignees must be human or an agent ID.

Track tools

Tool	Purpose
`epismo_track_create`	Create a task or goal
`epismo_track_update`	Patch a task or goal by UUID/URL
`epismo_track_get`	Read one track
`epismo_track_search`	Search tasks/goals with filters
`epismo_track_apply`	Bulk create/update/delete tracks
`epismo_track_delete`	Delete a track

Use epismo_track_apply when an agent creates multiple related tasks.

{
	"scope": { "type": "projects", "ids": ["project-id"] },
	"updateDrafts": [
		{
			"id": "t001",
			"title": "Review MCP docs",
			"task": { "status": "todo", "dueDate": "2026-06-05" }
		},
		{
			"id": "t002",
			"title": "Publish docs changes",
			"task": { "status": "todo", "dependsOn": ["t001"] }
		}
	]
}

Non-UUID IDs such as t001 create new tracks. Within the same epismo_track_apply call, those labels can be used in parentId, dependsOn, and goalId; the server resolves them to generated UUIDs.

epismo_track_search consumes credits. When an agent is exploring, narrow queries and filters first, then fetch detail only for records that matter.

Task statuses are backlog, todo, in_progress, and done. Goal statuses are not_started, on_track, at_risk, postponed, and completed.

Credit behavior

In MCP, agent usage and search calls consume credits. Credits are consumed from the current personal/workspace context resolved by the OAuth token. If the context does not have enough credits, the tool call may fail with a credit/payment error.

Alias tools

Tool	Purpose
`epismo_alias_upsert`	Create or repoint an alias for a pack you own
`epismo_alias_delete`	Delete an alias you own

Alias input is the unowned alias name. A leading @ is accepted and stripped, but owner prefixes such as @handle/name are not valid when creating or deleting your own alias.