Tools Reference
Every MCP tool the Zuse Bifrost server exposes today, grouped by what it works on, with the ability each one enforces.
161 tools across 13 groups: 72 read and 89 write (79 of them marked destructive, so a client confirms before running those). Every write runs the same action the application's own screens run, so permission checks, tenant scoping, webhooks and the activity log apply identically. Every count and list on this page is generated from the server's own export.
Machine-readable catalog
The authoritative, auto-generated list is published by the API host:
GET https://api.example.test/mcp-tools.jsonSibling documents at the same host, regenerated on every deploy:
https://api.example.test/abilities.json, the full ability catalogue.https://api.example.test/error-codes.json, every error code with its HTTP status and remediation.https://api.example.test/webhook-events.json, every outbound webhook event.
Tools by group
Each group below is one page of the reference. A page opens with what the group's tools are for, lists them, and then documents every tool in full: its arguments as the server validates them, what it returns, how it fails, the REST endpoint that runs the same action, the webhook events it fires, example prompts and the tools/call request an MCP client sends. A row here opens the tool on its page.
Account Tools
The account behind the token: who is acting, which team the token is scoped to, where alerts go and what sits unread in the Notifications Center. Open the group.
get_meGet MeREADlist_notificationsList NotificationsDESTRUCTIVEmark_all_notifications_readMark All Notifications ReadDESTRUCTIVEmark_notification_readMark Notification ReadBuild Tools
The tracker of a project: its stories, tasks, sub-tasks, bugs, spikes and improvements, each numbered from the same sequence as the epics (CRM-142) with its kind, status from the backlog to done, resolution, priority, the people on it, its estimates and dates, the fields its kind adds and, for a story, the acceptance criteria that say when it is done. Open the group.
assign_work_itemAssign Work ItemDESTRUCTIVEcreate_labelCreate LabelDESTRUCTIVEcreate_work_itemCreate Work ItemDESTRUCTIVEdelete_labelDelete LabelDESTRUCTIVEdelete_work_itemDelete Work ItemREADget_board_snapshotGet Board SnapshotREADget_sprintGet SprintREADget_work_itemGet Work ItemREADlist_labelsList LabelsREADlist_my_workList My WorkREADlist_sprintsList SprintsREADlist_work_itemsList Work ItemsDESTRUCTIVEmove_work_itemMove Work ItemDESTRUCTIVEupdate_labelUpdate LabelDESTRUCTIVEupdate_work_itemUpdate Work ItemCode Tools
Where a project's code lives: the Git repositories the team registered, each with its provider, the owner and name as the provider spells them, the branch releases are cut from, the address, whether it is private and the component it builds. Open the group.
create_repositoryCreate RepositoryDESTRUCTIVEdelete_repositoryDelete RepositoryREADget_repositoryGet RepositoryREADlist_repositoriesList RepositoriesDESTRUCTIVEupdate_repositoryUpdate RepositoryDictionary Tools
The dictionary of a project: the glossary (the words the project agrees on, each with one definition, the other names it goes by, the terms it leans on, its source and its review status) and the data entities (the things the project keeps records of, each with its fields, their types, flags, validation and examples, its component, its owner, whether it holds personal data and how long it is kept). Open the group.
create_data_entityCreate Data EntityDESTRUCTIVEcreate_glossary_termCreate Glossary TermDESTRUCTIVEdelete_data_entityDelete Data EntityDESTRUCTIVEdelete_glossary_termDelete Glossary TermREADget_data_entityGet Data EntityREADget_glossary_termGet Glossary TermREADlist_data_entitiesList Data EntitiesREADlist_glossary_termsList Glossary TermsDESTRUCTIVEupdate_data_entityUpdate Data EntityDESTRUCTIVEupdate_glossary_termUpdate Glossary TermDocuments Tools
The documents a project writes from its own record: the business requirements document the client signs and the software requirements specification the team builds against, each asked for with a kind, a title, a file format (PDF or HTML) and a scope (the record as it stands, with or without drafts, or a frozen baseline), rendered in the background as the person who asked and under their permissions, numbered within its kind (BRD #2), with an opening page Heimdall drafts when nobody wrote it, moved to final by the project manager's approval, which supersedes the kind's earlier final copy, and shared with the client's guests from that moment. Open the group.
generate_documentGenerate DocumentREADget_documentGet DocumentREADlist_documentsList DocumentsObservability Tools
Where to look when something did not happen: outbound webhook endpoints and their deliveries, and the activity log of every change made to a subject and who made it, from the application, the REST API, an MCP tool, an accepted Heimdall draft or a scheduled job. Open the group.
create_webhook_endpointCreate Webhook EndpointDESTRUCTIVEdelete_webhook_endpointDelete Webhook EndpointREADget_activity_logActivity LogREADget_webhook_deliveryGet Webhook DeliveryREADget_webhook_endpointGet Webhook EndpointREADlist_webhook_deliveriesList Webhook DeliveriesREADlist_webhook_endpointsList Webhook EndpointsDESTRUCTIVEpause_webhook_endpointPause Webhook EndpointDESTRUCTIVEresume_webhook_endpointResume Webhook EndpointDESTRUCTIVEretry_dead_webhook_deliveriesRetry Dead Webhook DeliveriesDESTRUCTIVEretry_webhook_deliveryRetry Webhook DeliveryDESTRUCTIVErotate_webhook_endpoint_secretRotate Webhook Endpoint SecretDESTRUCTIVEtest_webhook_endpointTest Webhook EndpointPeople Tools
The people of a project: the stakeholders it answers to (the client's sponsor, product owner and approvers, Zuse's own leads, third parties, each with a side, a role, a weight and the approvals that name them) and the personas it is built for (named, sketched users with goals, frustrations and habits, the "as a …" of every story). Open the group.
create_personaCreate PersonaDESTRUCTIVEcreate_stakeholderCreate StakeholderDESTRUCTIVEdelete_personaDelete PersonaDESTRUCTIVEdelete_stakeholderDelete StakeholderREADget_personaGet PersonaREADget_stakeholderGet StakeholderREADlist_personasList PersonasREADlist_stakeholdersList StakeholdersDESTRUCTIVEupdate_personaUpdate PersonaDESTRUCTIVEupdate_stakeholderUpdate StakeholderPlanning Tools
The planning record of a project: its epics (the bodies of work the client recognises, each numbered from the project's tracker sequence, CRM-12, with its goal, value, measures, owner, MoSCoW priority, status from draft to done and dates) and its requirements (what the system shall do, functional, CRM-FR-12, and the qualities it shall keep, non-functional, CRM-NFR-3, each with a category and a measure, with the statement, the source, the priority, the verification method and the status from draft to baselined). Open the group.
analyse_change_impactAnalyse Change ImpactWRITEcomment_on_itemComment On ItemWRITEconvene_councilConvene CouncilDESTRUCTIVEcreate_baselineCreate BaselineDESTRUCTIVEcreate_epicCreate EpicDESTRUCTIVEcreate_raid_itemCreate RAID ItemWRITEcreate_requirement_draftCreate Requirement DraftWRITEcreate_story_draftCreate Story DraftDESTRUCTIVEcreate_use_caseCreate Use CaseDESTRUCTIVEdecide_council_findingDecide Council FindingDESTRUCTIVEdecide_suggestionDecide SuggestionDESTRUCTIVEdelete_baselineDelete BaselineDESTRUCTIVEdelete_business_ruleDelete Business RuleDESTRUCTIVEdelete_change_requestDelete Change RequestDESTRUCTIVEdelete_decisionDelete DecisionDESTRUCTIVEdelete_epicDelete EpicDESTRUCTIVEdelete_raid_itemDelete RAID ItemDESTRUCTIVEdelete_requirementDelete RequirementDESTRUCTIVEdelete_use_caseDelete Use CaseREADget_approval_requestGet Approval RequestREADget_baselineGet BaselineREADget_business_ruleGet Business RuleREADget_change_requestGet Change RequestREADget_council_sessionGet Council SessionREADget_decisionGet DecisionREADget_epicGet EpicREADget_import_batchGet Import BatchREADget_raid_itemGet RAID ItemREADget_requirementGet RequirementREADget_revisionGet RevisionREADget_use_caseGet Use CaseWRITElink_artefactsLink ArtefactsREADlist_attachmentsList AttachmentsREADlist_baselinesList BaselinesREADlist_business_rulesList Business RulesREADlist_change_requestsList Change RequestsREADlist_commentsList CommentsREADlist_council_sessionsList Council SessionsREADlist_decisionsList DecisionsREADlist_epicsList EpicsREADlist_import_batchesList Import BatchesREADlist_linksList LinksREADlist_pending_approvalsList Pending ApprovalsREADlist_quality_reviewsList Quality ReviewsREADlist_raid_itemsList RAID ItemsREADlist_requirementsList RequirementsREADlist_research_notesList Research NotesREADlist_revisionsList RevisionsREADlist_use_casesList Use CasesWRITEpropose_business_rulePropose Business RuleDESTRUCTIVEraise_change_requestRaise Change RequestWRITEraise_riskRaise RiskWRITErecord_decision_draftRecord Decision DraftDESTRUCTIVEremove_linkRemove LinkDESTRUCTIVErestore_revisionRestore RevisionWRITEreview_qualityReview QualityDESTRUCTIVEstart_brief_importStart Brief ImportDESTRUCTIVEstart_project_researchStart Project ResearchDESTRUCTIVEsubmit_for_reviewSubmit For ReviewWRITEsweep_improvementsSweep ImprovementsDESTRUCTIVEupdate_approval_policyUpdate Approval PolicyDESTRUCTIVEupdate_baselineUpdate BaselineDESTRUCTIVEupdate_business_ruleUpdate Business RuleDESTRUCTIVEupdate_change_requestUpdate Change RequestDESTRUCTIVEupdate_decisionUpdate DecisionDESTRUCTIVEupdate_epicUpdate EpicDESTRUCTIVEupdate_raid_itemUpdate RAID ItemDESTRUCTIVEupdate_requirementUpdate RequirementDESTRUCTIVEupdate_use_caseUpdate Use CaseProject Tools
A project is one client engagement's record: its key, which prefixes every reference inside it, its status from discovery to maintenance, its methodology, visibility, health and leads. Open the group.
create_clientCreate ClientDESTRUCTIVEcreate_componentCreate ComponentDESTRUCTIVEcreate_design_referenceCreate Design ReferenceDESTRUCTIVEcreate_environmentCreate EnvironmentDESTRUCTIVEcreate_projectCreate ProjectDESTRUCTIVEdelete_componentDelete ComponentDESTRUCTIVEdelete_design_referenceDelete Design ReferenceDESTRUCTIVEdelete_environmentDelete EnvironmentREADget_clientGet ClientREADget_componentGet ComponentREADget_design_referenceGet Design ReferenceREADget_environmentGet EnvironmentREADget_projectGet ProjectREADget_project_settingsGet Project SettingsREADlist_clientsList ClientsREADlist_componentsList ComponentsREADlist_design_referencesList Design ReferencesREADlist_environmentsList EnvironmentsREADlist_projectsList ProjectsDESTRUCTIVEupdate_clientUpdate ClientDESTRUCTIVEupdate_componentUpdate ComponentDESTRUCTIVEupdate_design_referenceUpdate Design ReferenceDESTRUCTIVEupdate_environmentUpdate EnvironmentDESTRUCTIVEupdate_projectUpdate ProjectDESTRUCTIVEupdate_project_settingsUpdate Project SettingsRole & Group Tools
A role is the permission set one member holds, seeded per team and editable by its owner; a group is a bundle of members with permissions they share. Open the group.
Team Member Tools
Team members are the staff and guests who collaborate inside a team, each with a role that decides what they may do. Open the group.
Team Tools
A team groups the people, roles and projects of one organisation, and every token is scoped to exactly one. Open the group.
Token Tools
Personal access tokens authorise every REST and MCP call, and the plaintext value exists exactly once. Open the group.
What is coming
The planning, build, test, release and maintenance families (context packs, stories and acceptance criteria, comments, status moves, test results, defects, deployments, incidents) join this page as each module lands, under the same rules: one ability per tool, the same ability as the REST equivalent, and a confirmation before anything destructive. An agent should read the live catalogue with tools/list rather than assume this page's groups are the whole surface.
Resource catalogs
Alongside tools, the server exposes 3 read-only resources:
zusegenius://enums/ability— API Ability Catalogue: Every ability a personal access token can carry: theentity:actiongates that mirror the team permission catalogue (projects, planning artefacts, tests, releases, incidents, teams, roles, tokens, webhooks and more) plus the extras (account:read,account:write,mcp:use,ci:deploy,ci:test-results). MCP and REST answer to the same catalogue: a tool requires the same ability its REST equivalent does, so mint for the operations you intend to call rather than for the channel. Read once at session start to know what the current token can do and to ask for the minimum-privilege list when a new token is minted. Returns{ abilities: [{value, group, label}], core_count, extras_count, total }.zusegenius://enums/error-code— API Error Code Catalogue: Every error code the REST API and the MCP tools can emit. Each entry carries the HTTP status, the default message, a remediation hint and adocs_urlanchor. Read it whenever a tool response carries anerrorenvelope, so the right remediation is picked before a retry: a baseline lock needs a change request, a refused transition names the statuses allowed, an exhausted AI budget waits for an admin. Returns{ error_codes: [{code, http_status, message, remediation, docs_url}] }.zusegenius://enums/webhook-event— Outbound Webhook Event Catalogue: Every outbound webhook event Zuse Bifrost can emit, grouped by family (project,team,role,tokenandaitoday, with the planning, build, test, release and maintenance families joining as each module lands). Each row carries the minimum ability a subscribing token must hold to receive the event and the keys itsdataobject can carry. Read it before registering a webhook endpoint so the event list lines up with what the source actions produce. Returns{ webhook_events: [{name, family, required_ability, payload_keys}], families: [string] }.
Clients that support resource browsing pick any of these as context before driving the tools. See the resources reference for payload shapes.
How is this guide?
Last updated on