Tools

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

Pack tools

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

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.

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": "Team onboarding",
	"blocks": [
		{
			"title": "Where things live",
			"content": "Docs in Notion, code in GitHub, designs in Figma."
		}
	]
}

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

Track tools

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

Use epismo_track_apply when an agent creates multiple related tasks.

{
	"scope": { "type": "projects", "ids": ["project-id"] },
	"upserts": [
		{
			"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.

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

Tool costs are listed in the tables above. 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	Cost
`epismo_alias_upsert`	Create or repoint an alias for a pack you own	1 credit
`epismo_alias_list`	List your personal and active-workspace aliases	1 credit
`epismo_alias_delete`	Delete an alias	1 credit

Alias input is the alias name; a leading @ is accepted and stripped. The @handle/name form references another account's alias for reading and cannot be used to create or delete one.

epismo_alias_upsert and epismo_alias_delete accept an optional namespace — personal (default) or workspace (the active workspace's shared account, resolvable by every member). Only the pack's owner may create, repoint, or delete an alias to it. epismo_alias_list returns each entry's namespace and a ready-to-use reference.