# Operator Documentation

Searchable operator docs for MCP tools, REST routes, and GPT app actions.

- Generated at: 2026-04-20T08:41:52.604Z
- Catalog API: /api/docs/catalog
- Focused host: https://docs.contractspec.studio
- Integrated path: https://www.contractspec.studio/docs

## Markdown routes

- Canonical (English): /docs.md
- Localized: /en/docs.md

## Summary

| Metric | Value |
| --- | --- |
| Operations | 310 |
| Documented ops | 279 |
| Matched REST routes | 0 |
| Advanced inventory | 0 |
| Live MCP tools | 279 |
| GPT actions | 0 |
| Warnings | 4 |

## Warnings

- Generated MCP manifest file not found for drift comparison.
- API docblock folder not found for public docs enrichment.
- REST route source folder not found for web-application API.
- GPT app blocks source folder not found for gpt-apps.
- Generated docs catalog file is missing at /var/task/packages/apps/web-marketing/generated/docs/surface-catalog.json. Falling back to runtime catalog generation.

## Operations

### Agency Kit Diff Sources

Diff two captures of the same source (v1)

- Operation key: `agency-kit.diff-sources`
- Domain: agency-kit
- Metadata: Registry
- Goal: Track how product sources change over time to detect meaningful shifts
- Context: v1 feature. Compares capture snapshots and highlights additions, removals, and changes.
- Stability: experimental
- Auth: user
- MCP tool: agency-kit_diff-sources
- Tags: agency-kit, diff, monitoring

### Agency Kit Export Drift Items

Export drift items as tickets to Linear/Jira

- Operation key: `agency-kit.export-drift-items`
- Domain: agency-kit
- Metadata: Registry
- Goal: Convert detected drift into actionable work items in project management tools
- Context: v1 feature. Maps drift severity to priority, risk type to labels.
- Stability: experimental
- Auth: user
- MCP tool: agency-kit_export-drift-items
- Tags: agency-kit, export, tickets

### Agency Kit Get Deliverable

Get a generated deliverable by ID

- Operation key: `agency-kit.get-deliverable`
- Domain: agency-kit
- Metadata: Registry
- Goal: Retrieve full deliverable content for viewing or export
- Context: Deliverable detail view and export flow
- Stability: experimental
- Auth: user
- MCP tool: agency-kit_get-deliverable
- Tags: agency-kit, deliverable

### Agency Kit Get Drift Register

Get drift items with feedback links

- Operation key: `agency-kit.get-drift-register`
- Domain: agency-kit
- Metadata: Registry
- Goal: Surface contradictions between sources with feedback for trust and action
- Context: Drift register table with severity and risk type filtering
- Stability: experimental
- Auth: user
- MCP tool: agency-kit_get-drift-register
- Tags: agency-kit, drift

### Agency Kit List Companies

List all companies for a workspace

- Operation key: `agency-kit.list-companies`
- Domain: agency-kit
- Metadata: Registry
- Goal: Display all scanned companies in the agency kit dashboard
- Context: Dashboard view with pagination
- Stability: experimental
- Auth: user
- MCP tool: agency-kit_list-companies
- Tags: agency-kit, company

### Agency Kit Share Deliverable

Create a public share link for a deliverable

- Operation key: `agency-kit.share-deliverable`
- Domain: agency-kit
- Metadata: Registry
- Goal: Enable viral distribution of generated deliverables via public share links
- Context: Part of GTM integration. Creates time-limited or permanent share tokens.
- Stability: experimental
- Auth: user
- MCP tool: agency-kit_share-deliverable
- Tags: agency-kit, share

### Agent Orchestration Packet Assign

Assign a planned packet to a lane worker with wave metadata

- Operation key: `agent-orchestration.packet.assign`
- Domain: agent-orchestration
- Metadata: Registry
- Goal: Guarantee deterministic packet assignment before execution starts
- Context: Agent swarm execution OS packet lifecycle
- Stability: experimental
- Auth: user
- MCP tool: agent-orchestration_packet_assign
- Tags: agent-orchestration, packet, assign, competition-killer

### Agent Orchestration Packet Plan

Plan a lane-scoped AI work packet

- Operation key: `agent-orchestration.packet.plan`
- Domain: agent-orchestration
- Metadata: Registry
- Goal: Enable deterministic parallel work scheduling for AI agents
- Context: Phase 0 baseline for agent swarm orchestration
- Stability: experimental
- Auth: user
- MCP tool: agent-orchestration_packet_plan
- Tags: agent-orchestration, packet, competition-killer

### Agent Orchestration Packet Verify

Verify packet outputs against acceptance and policy checks

- Operation key: `agent-orchestration.packet.verify`
- Domain: agent-orchestration
- Metadata: Registry
- Goal: Enforce deterministic quality gates before packet completion
- Context: Agent swarm execution OS verification lane
- Stability: experimental
- Auth: user
- MCP tool: agent-orchestration_packet_verify
- Tags: agent-orchestration, packet, verify, competition-killer

### Agent Orchestration Squad Run Control

Control a governed squad run lifecycle or approval checkpoint

- Operation key: `agent-orchestration.squad-run.control`
- Domain: agent-orchestration
- Metadata: Registry
- Goal: Pause, resume, cancel, approve, defer, and complete squad runs
- Context: Control plane for user-visible squads surfaced in mission control and chat delegation
- Stability: experimental
- Auth: user
- MCP tool: agent-orchestration_squad-run_control
- Tags: agent-orchestration, squad, control, openclaw

### Agent Orchestration Squad Run Start

Start a user-visible squad run for a governed agent team

- Operation key: `agent-orchestration.squad-run.start`
- Domain: agent-orchestration
- Metadata: Registry
- Goal: Let operators launch reviewed Ops and Engineering squads
- Context: Mission control first, chat delegation second, reusing packet orchestration infrastructure
- Stability: experimental
- Auth: user
- MCP tool: agent-orchestration_squad-run_start
- Tags: agent-orchestration, squad, mission-control, openclaw

### Ai Workspace Agent Define

Not available

- Operation key: `ai.workspace.agent.define`
- Domain: ai
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Ai Workspace Agent List

Not available

- Operation key: `ai.workspace.agent.list`
- Domain: ai
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Analytics Metric Definition Get

Not available

- Operation key: `analytics.metric-definition.get`
- Domain: analytics
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Analytics Metric Definition List

Not available

- Operation key: `analytics.metric-definition.list`
- Domain: analytics
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Analytics Metric Definition Upsert

Not available

- Operation key: `analytics.metric-definition.upsert`
- Domain: analytics
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Analytics Metric Snapshot Get

Not available

- Operation key: `analytics.metric-snapshot.get`
- Domain: analytics
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Analytics Metric Snapshot List

Not available

- Operation key: `analytics.metric-snapshot.list`
- Domain: analytics
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Analytics Metric Snapshot Refresh

Not available

- Operation key: `analytics.metric-snapshot.refresh`
- Domain: analytics
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Autopilot Disable

Disable Autopilot for a workspace

- Operation key: `autopilot.disable`
- Domain: autopilot
- Metadata: Registry
- Goal: Allow workspaces to opt-out of background product loops
- Context: Part of the Autopilot domain. Stops all scheduled runs; existing artifacts remain.
- Stability: experimental
- Auth: user
- MCP tool: autopilot_disable
- Tags: autopilot, workspace, config

### Autopilot Dismiss Run

Dismiss an Autopilot run without acting on it

- Operation key: `autopilot.dismiss-run`
- Domain: autopilot
- Metadata: Registry
- Goal: Allow users to acknowledge and dismiss runs they do not want to act on
- Context: Part of the Autopilot domain. Deliverables remain for auditability but run is marked dismissed.
- Stability: experimental
- Auth: user
- MCP tool: autopilot_dismiss-run
- Tags: autopilot, run

### Autopilot Enable

Enable Autopilot for a workspace with schedule, preset, and sources

- Operation key: `autopilot.enable`
- Domain: autopilot
- Metadata: Registry
- Goal: Allow workspaces to opt-in to background product loops that generate planning deliverables
- Context: Part of the Autopilot domain. Autopilot runs feedback → patterns → focus → brief → patch → impact → export → checks in background.
- Stability: experimental
- Auth: user
- MCP tool: autopilot_enable
- Tags: autopilot, workspace, config

### Autopilot Get Config

Retrieve Autopilot configuration for a workspace

- Operation key: `autopilot.get-config`
- Domain: autopilot
- Metadata: Registry
- Goal: Fetch current Autopilot status, schedule, and policy settings
- Context: Part of the Autopilot domain. Used by the settings page and orchestrator.
- Stability: experimental
- Auth: user
- MCP tool: autopilot_get-config
- Tags: autopilot, config

### Autopilot Get Run

Retrieve a single Autopilot run with full deliverables

- Operation key: `autopilot.get-run`
- Domain: autopilot
- Metadata: Registry
- Goal: Fetch run details for inspection, review, or trace display
- Context: Part of the Autopilot domain. Used by the run detail view and Action Item run trace.
- Stability: experimental
- Auth: user
- MCP tool: autopilot_get-run
- Tags: autopilot, run

### Autopilot List Runs

List Autopilot runs for a workspace with filters

- Operation key: `autopilot.list-runs`
- Domain: autopilot
- Metadata: Registry
- Goal: Populate the runs feed with filterable run history
- Context: Part of the Autopilot domain. Supports filtering by status, focus template, and pagination.
- Stability: experimental
- Auth: user
- MCP tool: autopilot_list-runs
- Tags: autopilot, run, feed

### Autopilot Review Certify

Manually certify a Needs Review run after human inspection

- Operation key: `autopilot.review-certify`
- Domain: autopilot
- Metadata: Registry
- Goal: Allow stakeholders to unblock runs that were stopped at a policy gate
- Context: Part of the Autopilot domain. After review, triggers export + check + notify for the run.
- Stability: experimental
- Auth: user
- MCP tool: autopilot_review-certify
- Tags: autopilot, run, review

### Autopilot Trigger Run

Trigger an immediate Autopilot run for a workspace

- Operation key: `autopilot.trigger-run`
- Domain: autopilot
- Metadata: Registry
- Goal: Allow users to manually kick off the background product loop on demand
- Context: Part of the Autopilot domain. Creates a new run with status "planned", then starts execution.
- Stability: experimental
- Auth: user
- MCP tool: autopilot_trigger-run
- Tags: autopilot, run

### Autopilot Update Policy

Update Autopilot policy configuration for a workspace

- Operation key: `autopilot.update-policy`
- Domain: autopilot
- Metadata: Registry
- Goal: Allow workspace admins to tune guardrails (presets or custom overrides)
- Context: Part of the Autopilot domain. Policies control scope, feedback, risk, idempotency, and output gates.
- Stability: experimental
- Auth: user
- MCP tool: autopilot_update-policy
- Tags: autopilot, policy, config

### Autopilot Update Schedule

Update Autopilot run schedule for a workspace

- Operation key: `autopilot.update-schedule`
- Domain: autopilot
- Metadata: Registry
- Goal: Allow workspace admins to choose daily, weekly, or on-ingestion runs
- Context: Part of the Autopilot domain. Schedule controls how often background runs are triggered.
- Stability: experimental
- Auth: user
- MCP tool: autopilot_update-schedule
- Tags: autopilot, schedule, config

### Brief Delete

Soft-deletes an opportunity brief (reversible via restore)

- Operation key: `brief.delete`
- Domain: brief
- Metadata: Registry
- Goal: Allow users to remove briefs that are no longer needed
- Context: Part of the Decision Layer. Authored/generated hybrid; soft-delete + restore.
- Stability: experimental
- Auth: user
- MCP tool: brief_delete
- Tags: decision, brief, delete, loop-crud

### Brief Generate

Generates a structured opportunity brief with mandatory citations from feedback

- Operation key: `brief.generate`
- Domain: brief
- Metadata: Registry
- Goal: Transform patterns and focus into a validated, citeable rationale for change
- Context: Part of the Decision Layer (M3). Briefs are strict JSON outputs validated against a schema with citation requirements.
- Stability: experimental
- Auth: user
- MCP tool: brief_generate
- Tags: decision, brief, m3

### Brief Get

Get a specific opportunity brief by ID

- Operation key: `brief.get`
- Domain: brief
- Metadata: Registry
- Goal: Allow users to inspect full brief details including recommendations and citations
- Context: Part of the Decision Layer. Returns the complete brief record for the brief detail view.
- Stability: experimental
- Auth: user
- MCP tool: brief_get
- Tags: decision, brief, detail, citations

### Brief List

List opportunity briefs with pagination

- Operation key: `brief.list`
- Domain: brief
- Metadata: Registry
- Goal: Allow users to browse and paginate through generated opportunity briefs
- Context: Part of the Decision Layer. Provides paginated access to briefs for the decision feed.
- Stability: experimental
- Auth: user
- MCP tool: brief_list
- Tags: decision, brief, list, pagination

### Brief Update

Updates a persisted opportunity brief after human review

- Operation key: `brief.update`
- Domain: brief
- Metadata: Registry
- Goal: Allow humans to refine a generated brief without forcing a full regeneration
- Context: Part of the Decision Layer. Supports inline edits to the stored opportunity brief artifact.
- Stability: experimental
- Auth: user
- MCP tool: brief_update
- Tags: decision, brief, update, human-in-loop

### Change Check Get

Get a single outcome verification check by ID

- Operation key: `change.check.get`
- Domain: change
- Metadata: Registry
- Goal: Allow users and agents to inspect the full check lifecycle state
- Context: Part of the Change Layer. Returns the complete check record for detail views and inline AI actions.
- Stability: experimental
- Auth: user
- MCP tool: change_check_get
- Tags: change, check, detail

### Change Check List

List outcome verification checks with status and timeline

- Operation key: `change.check.list`
- Domain: change
- Metadata: Registry
- Goal: Allow users and agents to see pending checks awaiting evaluation
- Context: Part of the Change Layer. Provides access to checks for the checks list view and recap workflows.
- Stability: experimental
- Auth: user
- MCP tool: change_check_list
- Tags: change, check, list

### Change Handoff Pack Generate

Generates a reviewed engineering handoff pack from repository context and traceability state

- Operation key: `change.handoff-pack.generate`
- Domain: change
- Metadata: Registry
- Goal: Prepare agent-ready engineering handoff without hidden code writes
- Context: Change layer. Composes engineering context, traceability, and task generation for destination-specific coding-agent handoff.
- Stability: experimental
- Auth: user
- MCP tool: change_handoff-pack_generate
- Tags: change, handoff, engineering

### Change Handoff Pack Share Slack

Shares a reviewed engineering handoff summary into Slack

- Operation key: `change.handoff-pack.share-slack`
- Domain: change
- Metadata: Registry
- Goal: Route reviewed engineering handoff status to Slack without making Slack the system of record
- Context: Change layer. Uses the reviewed handoff pack and engineering context bundle to publish a ready/blocked summary into a selected Slack channel.
- Stability: experimental
- Auth: user
- MCP tool: change_handoff-pack_share-slack
- Tags: change, handoff, slack, engineering

### Change Handoff Pack Verify

Verifies whether a generated engineering handoff pack is ready for human review

- Operation key: `change.handoff-pack.verify`
- Domain: change
- Metadata: Registry
- Goal: Block weak handoffs before they are sent to coding agents
- Context: Change layer. Verification step for engineering handoff using the current context bundle and traceability state.
- Stability: experimental
- Auth: user
- MCP tool: change_handoff-pack_verify
- Tags: change, handoff, verification

### Change List

List compiled action items with impact summaries and PM board linkage

- Operation key: `change.list`
- Domain: change
- Metadata: Registry
- Goal: Allow users to browse and filter their compiled action items
- Context: Part of the Change Layer. Provides summary data for the changes feed, focus tabs, and impact views.
- Stability: experimental
- Auth: user
- MCP tool: change_list
- Tags: change, list, impact, pm-board

### Change Remediation Pack Deliver

Delivers a persisted remediation session into governed managed PR creation

- Operation key: `change.remediation-pack.deliver`
- Domain: change
- Metadata: Registry
- Goal: Execute reviewed remediation delivery from server-owned state instead of browser-held drafts
- Context: Change layer. Re-validates approval, expiry, and governance before opening or reusing a managed delivery PR.
- Stability: experimental
- Auth: user
- MCP tool: change_remediation-pack_deliver
- Tags: change, remediation, delivery

### Change Remediation Pack Generate

Generates an incident remediation pack with RCA, governed delivery draft, and reviewed PR payload

- Operation key: `change.remediation-pack.generate`
- Domain: change
- Metadata: Registry
- Goal: Translate production incident context into an approval-gated remediation package before mutation
- Context: Change layer. Composes incident bundle evidence into RCA, candidate file changes, verification steps, and managed delivery metadata.
- Stability: experimental
- Auth: user
- MCP tool: change_remediation-pack_generate
- Tags: change, remediation, engineering

### Change Remediation Pack Verify

Verifies whether a remediation pack is safe to move into managed PR delivery

- Operation key: `change.remediation-pack.verify`
- Domain: change
- Metadata: Registry
- Goal: Block weak or ungrounded remediations before Git mutation
- Context: Change layer. Final verification step for incident remediation using incident evidence, traceability, and managed delivery readiness.
- Stability: experimental
- Auth: user
- MCP tool: change_remediation-pack_verify
- Tags: change, remediation, verification

### Change Remediation Session Get

Reads a persisted remediation session by id

- Operation key: `change.remediation-session.get`
- Domain: change
- Metadata: Registry
- Goal: Recover remediation state without trusting client-held payloads
- Context: Change layer. Returns the server-owned remediation session, approval state, and delivery state.
- Stability: experimental
- Auth: user
- MCP tool: change_remediation-session_get
- Tags: change, remediation, session

### Check Delete

Soft-deletes an outcome check — reversible via restore

- Operation key: `check.delete`
- Domain: check
- Metadata: Registry
- Goal: Allow users to remove checks that are no longer needed
- Context: Part of the Change Layer. Operational artifact; soft-delete + restore.
- Stability: experimental
- Auth: user
- MCP tool: check_delete
- Tags: change, check, delete, loop-crud

### Check Update

Updates a check status, records observed values, or adds notes

- Operation key: `check.update`
- Domain: check
- Metadata: Registry
- Goal: Enable outcome tracking by recording metric observations and transitioning check lifecycle
- Context: Part of the Change Layer (M5). Valid transitions: planned -> running -> observed -> confirmed/rejected.
- Stability: experimental
- Auth: user
- MCP tool: check_update
- Tags: change, check, m5

### Connector Attio Activity Search

Search Attio CRM activity such as notes, tasks, meetings, and call recordings

- Operation key: `connector.attio.activity.search`
- Domain: connector
- Metadata: Registry
- Goal: Bring Attio activity history into operator and agent context without forcing generic integration-data browsing first
- Context: Attio activity surface over the connected CRM workspace.
- Stability: experimental
- Auth: user
- MCP tool: connector_attio_activity_search
- Tags: connector, attio, crm, activity

### Connector Attio Attributes List

List Attio object attribute definitions

- Operation key: `connector.attio.attributes.list`
- Domain: connector
- Metadata: Registry
- Goal: Expose Attio schema context so agents and operators can reason about custom objects and safe write targets
- Context: Attio object configuration discovery for CRM-aware workflows.
- Stability: experimental
- Auth: user
- MCP tool: connector_attio_attributes_list
- Tags: connector, attio, crm, schema

### Connector Attio Record Get

Get one Attio record with raw values and metadata

- Operation key: `connector.attio.record.get`
- Domain: connector
- Metadata: Registry
- Goal: Hydrate a specific Attio account, contact, deal, or custom object into AI context
- Context: Attio record detail surface with connector-scoped access control.
- Stability: experimental
- Auth: user
- MCP tool: connector_attio_record_get
- Tags: connector, attio, crm, detail

### Connector Attio Search

Search records across the connected Attio workspace

- Operation key: `connector.attio.search`
- Domain: connector
- Metadata: Registry
- Goal: Let agents and operators find accounts, contacts, deals, and custom objects in Attio before falling back to normalized feeds
- Context: Attio CRM workspace search with connector-scoped auth and governance.
- Stability: experimental
- Auth: user
- MCP tool: connector_attio_search
- Tags: connector, attio, crm, search

### Connector Attio Write

Plan or execute approved Attio CRM writes

- Operation key: `connector.attio.write`
- Domain: connector
- Metadata: Registry
- Goal: Let governed AI flows and operators create CRM records, notes, and tasks through one auditable Attio write path
- Context: Attio mutation planner and executor with confirmation-gated writes.
- Stability: experimental
- Auth: user
- MCP tool: connector_attio_write
- Tags: connector, attio, crm, write

### Connector Notion Context Query

Rank Notion workspace memory for AI context assembly

- Operation key: `connector.notion.context.query`
- Domain: connector
- Metadata: Registry
- Goal: Let chat, MCP, and operators retrieve the most relevant Notion context before generic browsing
- Context: Notion workspace graph surface. Ranks mirrors, cold workspace hits, and comment context for AI-native retrieval.
- Stability: experimental
- Auth: user
- MCP tool: connector_notion_context_query
- Tags: connector, notion, context, retrieval

### Connector Notion Hydrate

Hydrate a Notion page or data source into the workspace graph surface

- Operation key: `connector.notion.hydrate`
- Domain: connector
- Metadata: Registry
- Goal: Allow on-demand Notion reads to become first-class artifacts for AI and UI
- Context: Notion workspace graph surface. Used after search hits or before autonomous writes.
- Stability: experimental
- Auth: user
- MCP tool: connector_notion_hydrate
- Tags: connector, notion, hydrate

### Connector Notion Item Get

Get one Notion artifact with rich markdown, graph, and write detail

- Operation key: `connector.notion.item.get`
- Domain: connector
- Metadata: Registry
- Goal: Let UI, chat, and MCP inspect a synced or hydrated Notion artifact deeply
- Context: Notion workspace graph surface. Returns one typed artifact detail for AI and operator workflows.
- Stability: experimental
- Auth: user
- MCP tool: connector_notion_item_get
- Tags: connector, notion, knowledge, detail

### Connector Notion Item Override

Override the applied classification for a mirrored Notion item

- Operation key: `connector.notion.item.override`
- Domain: connector
- Metadata: Registry
- Goal: Let users correct Notion auto-analysis without editing mirrored source content
- Context: Notion knowledge ingestion v1. Overrides persist across future syncs.
- Stability: experimental
- Auth: user
- MCP tool: connector_notion_item_override
- Tags: connector, notion, knowledge, override

### Connector Notion Items List

List mirrored Notion knowledge items for a connector

- Operation key: `connector.notion.items.list`
- Domain: connector
- Metadata: Registry
- Goal: Allow users to inspect synced Notion pages and row mirrors
- Context: Notion knowledge ingestion v1. Used by settings data management screens.
- Stability: experimental
- Auth: user
- MCP tool: connector_notion_items_list
- Tags: connector, notion, knowledge, items

### Connector Notion Search

Search the connected Notion workspace for pages and data sources

- Operation key: `connector.notion.search`
- Domain: connector
- Metadata: Registry
- Goal: Allow AI and operators to discover Notion content outside the current hydrated set
- Context: Notion workspace graph surface. Uses whole-workspace discovery with connector-scoped access.
- Stability: experimental
- Auth: user
- MCP tool: connector_notion_search
- Tags: connector, notion, search

### Connector Notion Sources Configure

Configure which Notion knowledge sources should sync

- Operation key: `connector.notion.sources.configure`
- Domain: connector
- Metadata: Registry
- Goal: Persist selected Notion pages and data sources with default classification settings
- Context: Notion knowledge ingestion v1. Selected sources are stored in KnowledgeSource records.
- Stability: experimental
- Auth: user
- MCP tool: connector_notion_sources_configure
- Tags: connector, notion, knowledge, sources

### Connector Notion Sources List

List selected and discoverable Notion knowledge sources

- Operation key: `connector.notion.sources.list`
- Domain: connector
- Metadata: Registry
- Goal: Allow users to configure which Notion pages and data sources sync into knowledge
- Context: Notion knowledge ingestion v1. Used by settings integrations UI.
- Stability: experimental
- Auth: user
- MCP tool: connector_notion_sources_list
- Tags: connector, notion, knowledge, sources

### Connector Notion Write

Apply an autonomous Notion write with guardrails and audit detail

- Operation key: `connector.notion.write`
- Domain: connector
- Metadata: Registry
- Goal: Let agents update Notion content, properties, and comments safely
- Context: Notion workspace graph surface. Supports guarded content writes, property updates, block appends, and comments.
- Stability: experimental
- Auth: user
- MCP tool: connector_notion_write
- Tags: connector, notion, write

### Connector Notion Write Plan

Create an approval-gated Notion write plan

- Operation key: `connector.notion.write.plan`
- Domain: connector
- Metadata: Registry
- Goal: Let agents and operators preview a Notion mutation, capture a conflict token, and enqueue it for human approval before apply
- Context: Notion workspace graph surface. Plans comments, content updates, property updates, and block appends without applying them immediately.
- Stability: experimental
- Auth: user
- MCP tool: connector_notion_write_plan
- Tags: connector, notion, write, approval

### Content Ops Asset Lineage Get

Get canonical asset lineage

- Operation key: `content-ops.asset-lineage-get`
- Domain: content-ops
- Metadata: Registry
- Goal: Trace packet slices and published URLs from canonical asset ID
- Context: Part of the Content Ops domain.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_asset-lineage-get
- Tags: content-ops, lineage, audit

### Content Ops Brief Create

Create packet content brief

- Operation key: `content-ops.brief-create`
- Domain: content-ops
- Metadata: Registry
- Goal: Standardize canonical copy inputs before draft generation
- Context: Part of the Content Ops domain. Briefs capture objective, audience, and CTA boundaries.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_brief-create
- Tags: content-ops, brief, copywriting

### Content Ops Calendar Get

Get packet execution calendar

- Operation key: `content-ops.calendar-get`
- Domain: content-ops
- Metadata: Registry
- Goal: Provide timeline view for packet schedule and lane allocation
- Context: Part of the Content Ops domain.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_calendar-get
- Tags: content-ops, calendar, planning

### Content Ops Canonical Generate

Generate canonical asset draft

- Operation key: `content-ops.canonical-generate`
- Domain: content-ops
- Metadata: Registry
- Goal: Produce canonical blog-ready draft content from validated brief inputs
- Context: Part of the Content Ops domain. Canonical draft is the source for all channel slices.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_canonical-generate
- Tags: content-ops, canonical, generation

### Content Ops Learning Capture

Capture packet learning

- Operation key: `content-ops.learning-capture`
- Domain: content-ops
- Metadata: Registry
- Goal: Persist explicit lessons so future packets can improve deterministically
- Context: Part of the Content Ops domain. Learning capture closes the weekly publication loop.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_learning-capture
- Tags: content-ops, learning, iteration

### Content Ops Packet Advance

Advance a packet status

- Operation key: `content-ops.packet-advance`
- Domain: content-ops
- Metadata: Registry
- Goal: Move publication packets through deterministic lifecycle states
- Context: Part of the Content Ops domain. Transition gates enforce rewrite, QA, and risk approvals.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_packet-advance
- Tags: content-ops, packet, lifecycle

### Content Ops Packet Create

Create a publication packet

- Operation key: `content-ops.packet-create`
- Domain: content-ops
- Metadata: Registry
- Goal: Initialize a packet with owner, risk class, and target channels
- Context: Part of the Content Ops domain. Packet creation starts the content lifecycle state machine.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_packet-create
- Tags: content-ops, packet, publishing

### Content Ops Packet Get

Fetch a publication packet by packet ID

- Operation key: `content-ops.packet-get`
- Domain: content-ops
- Metadata: Registry
- Goal: Provide packet lifecycle state and metadata for operations
- Context: Part of the Content Ops domain.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_packet-get
- Tags: content-ops, packet, query

### Content Ops Packet List

List packets with lifecycle filters

- Operation key: `content-ops.packet-list`
- Domain: content-ops
- Metadata: Registry
- Goal: Provide paginated packet listings for execution planning
- Context: Part of the Content Ops domain.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_packet-list
- Tags: content-ops, packet, planning

### Content Ops Publish Mark

Mark packet as published

- Operation key: `content-ops.publish-mark`
- Domain: content-ops
- Metadata: Registry
- Goal: Capture publication URLs and move packet to published status
- Context: Part of the Content Ops domain. Publication marks immutable archive references.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_publish-mark
- Tags: content-ops, publishing, archive

### Content Ops Qa Verify

Run packet QA verification

- Operation key: `content-ops.qa-verify`
- Domain: content-ops
- Metadata: Registry
- Goal: Ensure rewrite, links, UTMs, and policy checks pass before schedule
- Context: Part of the Content Ops domain. QA gate protects publication quality and trust.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_qa-verify
- Tags: content-ops, qa, governance

### Content Ops Rewrite Run

Run copy rewrite checks

- Operation key: `content-ops.rewrite-run`
- Domain: content-ops
- Metadata: Registry
- Goal: Enforce Julian-style rewrite passes before packet scheduling
- Context: Part of the Content Ops domain. Rewrite gate validates copy quality and ad-detector checks.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_rewrite-run
- Tags: content-ops, rewrite, quality

### Content Ops Schedule Set

Set publication schedule for packet

- Operation key: `content-ops.schedule-set`
- Domain: content-ops
- Metadata: Registry
- Goal: Assign packet publication date/time with timezone-aware metadata
- Context: Part of the Content Ops domain. Schedule setting requires completed QA and approvals.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_schedule-set
- Tags: content-ops, schedule, publishing

### Content Ops Scoreboard Compute

Compute weekly content ops scoreboard

- Operation key: `content-ops.scoreboard-compute`
- Domain: content-ops
- Metadata: Registry
- Goal: Generate weekly packet output and conversion deltas for learning loop
- Context: Part of the Content Ops domain. Scoreboard metrics drive next sprint priorities.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_scoreboard-compute
- Tags: content-ops, analytics, scoreboard

### Content Ops Scoreboard Weekly Get

Get weekly content ops scoreboard

- Operation key: `content-ops.scoreboard-weekly-get`
- Domain: content-ops
- Metadata: Registry
- Goal: Expose packet output and conversion deltas for review loops
- Context: Part of the Content Ops domain.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_scoreboard-weekly-get
- Tags: content-ops, scoreboard, analytics

### Content Ops Slice Generate

Generate channel slices from canonical asset

- Operation key: `content-ops.slice-generate`
- Domain: content-ops
- Metadata: Registry
- Goal: Compile deterministic channel variants while preserving thesis and evidence
- Context: Part of the Content Ops domain. Slice generation powers LinkedIn/X/newsletter/reddit outputs.
- Stability: experimental
- Auth: user
- MCP tool: content-ops_slice-generate
- Tags: content-ops, distribution, channels

### Contractspec Codebase Analyze

Analyzes the codebase for ContractSpec coverage — covered/uncovered endpoints, orphaned contracts, and drift

- Operation key: `contractspec.codebase.analyze`
- Domain: contractspec
- Metadata: Registry
- Goal: Detect spec-to-code gaps so teams can close coverage holes before shipping
- Context: ContractSpec domain. Uses the source-analysis extractor to detect framework routes and cross-reference them with contract files on disk.
- Stability: experimental
- Auth: user
- MCP tool: contractspec_codebase_analyze
- Tags: contractspec, analysis, coverage

### Contractspec Contract Read

Reads a single ContractSpec contract definition by name

- Operation key: `contractspec.contract.read`
- Domain: contractspec
- Metadata: Registry
- Goal: Provide detailed contract inspection for auditing and AI-assisted editing
- Context: ContractSpec domain. Finds the contract by name and returns its full metadata including version, tags, and owners.
- Stability: experimental
- Auth: user
- MCP tool: contractspec_contract_read
- Tags: contractspec, contracts, read

### Contractspec Contracts List

Lists all ContractSpec contracts with metadata (name, version, type, domain, tags, owners)

- Operation key: `contractspec.contracts.list`
- Domain: contractspec
- Metadata: Registry
- Goal: Provide a catalog view of all defined contracts for auditing and discovery
- Context: ContractSpec domain. Scans the contracts lib source directories and extracts metadata from each contract file.
- Stability: experimental
- Auth: user
- MCP tool: contractspec_contracts_list
- Tags: contractspec, contracts, catalog

### Contractspec Spec Evolve

Runs the spec evolution pipeline to generate contract change suggestions from telemetry

- Operation key: `contractspec.spec.evolve`
- Domain: contractspec
- Metadata: Registry
- Goal: Proactively suggest contract changes based on real-world usage patterns and anomalies
- Context: ContractSpec domain. Analyzes telemetry samples, detects latency spikes and error bursts, and generates typed suggestions with confidence scores.
- Stability: experimental
- Auth: user
- MCP tool: contractspec_spec_evolve
- Tags: contractspec, evolution, ai

### Correlation Run

Runs the correlation pipeline: signature extraction, linking, clustering, and scoring

- Operation key: `correlation.run`
- Domain: correlation
- Metadata: Registry
- Goal: Transform isolated feedback chunks into connected, ranked patterns for decision-making
- Context: Part of the Correlation Layer (M2). Operates on feedback chunks from M1. Idempotent — safe to re-run without duplicating edges or patterns.
- Stability: experimental
- Auth: user
- MCP tool: correlation_run
- Tags: correlation, patterning, m2

### Engineering Context Bundle Get

Returns repository, traceability, freshness, and MCP readiness in one engineering context bundle

- Operation key: `engineering.context-bundle.get`
- Domain: engineering
- Metadata: Registry
- Goal: Provide reviewed engineering context before handoff or automation
- Context: Engineering context domain. Bridges repository context, contract traceability, and MCP availability for agent-assisted delivery.
- Stability: experimental
- Auth: user
- MCP tool: engineering_context-bundle_get
- Tags: engineering, context, traceability

### Engineering Incident Bundle Get

Returns a normalized incident bundle with repo context, traceability, delivery evidence, and blockers

- Operation key: `engineering.incident-bundle.get`
- Domain: engineering
- Metadata: Registry
- Goal: Prepare deterministic RCA and remediation planning before any code mutation
- Context: Engineering context domain. Composes observability signals with repository context, releases, PR state, and traceability.
- Stability: experimental
- Auth: user
- MCP tool: engineering_incident-bundle_get
- Tags: engineering, incidents, rca

### Engineering Incident Feed List

Lists normalized production incidents for a repository using provider-agnostic observability intake

- Operation key: `engineering.incident-feed.list`
- Domain: engineering
- Metadata: Registry
- Goal: Expose ranked incident signals before RCA, remediation planning, and reviewed PR delivery
- Context: Engineering context domain. Extends repository context with normalized incident intake from production signals.
- Stability: experimental
- Auth: user
- MCP tool: engineering_incident-feed_list
- Tags: engineering, incidents, observability

### Engineering Traceability Get

Returns contract coverage and spec/docblock traceability gaps for an engineering repository

- Operation key: `engineering.traceability.get`
- Domain: engineering
- Metadata: Registry
- Goal: Expose deterministic drift and missing context before handoff
- Context: Engineering context domain. Designed for reviewed handoff, audit, and repository explanation workflows.
- Stability: experimental
- Auth: user
- MCP tool: engineering_traceability_get
- Tags: engineering, traceability, contracts

### Feedback Delete Item

Deletes a feedback item and its metadata

- Operation key: `feedback.delete-item`
- Domain: feedback
- Metadata: Registry
- Goal: Allow users to remove feedback items that are no longer needed
- Context: Part of the Feedback Layer.
- Stability: experimental
- Auth: user
- MCP tool: feedback_delete-item
- Tags: feedback, delete, item

### Feedback Delete Items

Deletes all feedback items matching a filter snapshot

- Operation key: `feedback.delete-items`
- Domain: feedback
- Metadata: Registry
- Goal: Allow operators to remove large filtered result sets in one action
- Context: Part of the Feedback Layer. Scoped bulk delete for the signals table.
- Stability: experimental
- Auth: user
- MCP tool: feedback_delete-items
- Tags: feedback, delete, bulk

### Feedback Get Item

Get a single feedback item by ID

- Operation key: `feedback.get-item`
- Domain: feedback
- Metadata: Registry
- Goal: Allow users to inspect full feedback item details including chunks
- Context: Part of the Feedback Layer. Returns the complete item with all chunks for citation and review.
- Stability: experimental
- Auth: user
- MCP tool: feedback_get-item
- Tags: feedback, detail, chunks

### Feedback Ingest

Ingests feedback artifacts (text, links, and files) into the system

- Operation key: `feedback.ingest`
- Domain: feedback
- Metadata: Registry
- Goal: Allow users to upload and process feedback artifacts for citation and analysis
- Context: Part of the Feedback Layer (M1). Handles artifact intake, chunking, PII redaction, and indexing for feedback evidence.
- Stability: experimental
- Auth: user
- MCP tool: feedback_ingest
- Tags: feedback, ingestion, m1

### Feedback List Items

List feedback items with server pagination and sorting

- Operation key: `feedback.list-items`
- Domain: feedback
- Metadata: Registry
- Goal: Allow users to browse and sort ingested feedback items in a table
- Context: Part of the Feedback Layer. Provides the canonical server-driven browse contract for feedback signals.
- Stability: experimental
- Auth: user
- MCP tool: feedback_list-items
- Tags: feedback, list, pagination, table, sorting

### Feedback Search

Searches feedback chunks by keyword, segment, date, and vector similarity

- Operation key: `feedback.search`
- Domain: feedback
- Metadata: Registry
- Goal: Allow users to find and cite relevant feedback chunks for patterns and decisions
- Context: Part of the Feedback Layer (M1). Combines keyword filtering with vector similarity for hybrid retrieval.
- Stability: experimental
- Auth: user
- MCP tool: feedback_search
- Tags: feedback, search, m1

### Feedback Update Item

Updates feedback metadata such as segment, persona, tags, or curation status

- Operation key: `feedback.update-item`
- Domain: feedback
- Metadata: Registry
- Goal: Allow human curation of feedback items without changing the original evidence text
- Context: Part of the Feedback Layer. Only metadata fields are mutable; raw text and chunks remain immutable.
- Stability: experimental
- Auth: user
- MCP tool: feedback_update-item
- Tags: feedback, update, curation, item

### Focus Create

Creates a timeboxed focus zone with a target metric, segment, timeframe, and constraints

- Operation key: `focus.create`
- Domain: focus
- Metadata: Registry
- Goal: Allow users to declare a deliberate decision zone that frames downstream analysis and briefs
- Context: Part of the Decision Layer (M3). A focus is a commitment to a specific metric and audience within a timeframe.
- Stability: experimental
- Auth: user
- MCP tool: focus_create
- Tags: decision, focus, m3

### Focus Delete

Soft-deletes a focus (reversible via restore)

- Operation key: `focus.delete`
- Domain: focus
- Metadata: Registry
- Goal: Allow users to remove focuses that are no longer needed
- Context: Part of the Decision Layer. Authored entity; soft-delete + restore.
- Stability: experimental
- Auth: user
- MCP tool: focus_delete
- Tags: decision, focus, delete, loop-crud

### Focus Get

Get a specific focus zone by ID

- Operation key: `focus.get`
- Domain: focus
- Metadata: Registry
- Goal: Allow users to inspect full focus zone details including metric direction
- Context: Part of the Decision Layer. Returns the complete focus record for the focus detail view.
- Stability: experimental
- Auth: user
- MCP tool: focus_get
- Tags: decision, focus, detail

### Focus List

List focus zones with pagination

- Operation key: `focus.list`
- Domain: focus
- Metadata: Registry
- Goal: Allow users to browse and paginate through declared focus zones
- Context: Part of the Decision Layer. Provides paginated access to focus zones for the decision feed.
- Stability: experimental
- Auth: user
- MCP tool: focus_list
- Tags: decision, focus, list, pagination

### Focus Update

Updates a focus status or fields (metric, segment, timeframe, constraints when draft)

- Operation key: `focus.update`
- Domain: focus
- Metadata: Registry
- Goal: Allow users to transition focus lifecycle or edit draft focus details
- Context: Part of the Decision Layer (M3). Status transitions: draft->active, draft->archived, active->archived. Field updates only when status is draft.
- Stability: experimental
- Auth: user
- MCP tool: focus_update
- Tags: decision, focus, m3, update

### Governance Approval Request

Create an approval request for high-risk operations

- Operation key: `governance.approval.request`
- Domain: governance
- Metadata: Registry
- Goal: Guarantee explicit human approvals for high-risk execution paths
- Context: Trust and governance controls for enterprise readiness
- Stability: experimental
- Auth: user
- MCP tool: governance_approval_request
- Tags: governance, approval, risk

### Governance Approval Respond

Resolve a pending governance approval request

- Operation key: `governance.approval.respond`
- Domain: governance
- Metadata: Registry
- Goal: Capture reviewer decisions for high-risk operations
- Context: Approval workflow for enterprise-grade governance controls
- Stability: experimental
- Auth: user
- MCP tool: governance_approval_respond
- Tags: governance, approval, review

### Governance Audit Pack Get

Retrieves governance audit pack for compliance review

- Operation key: `governance.audit-pack.get`
- Domain: governance
- Metadata: Registry
- Goal: Provide audit metrics for enterprise trust and compliance
- Context: Governance MCP and GPT surfaces
- Stability: experimental
- Auth: user
- MCP tool: governance_audit-pack_get
- Tags: governance, audit, compliance

### Governance Enterprise Export Get

Not available

- Operation key: `governance.enterprise-export.get`
- Domain: governance
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Governance Evidence Graph Get

Retrieves claim-evidence verification graph

- Operation key: `governance.evidence-graph.get`
- Domain: governance
- Metadata: Registry
- Goal: Provide evidence graph for GTM and pricing proof surfaces
- Context: Governance MCP and GPT surfaces
- Stability: experimental
- Auth: user
- MCP tool: governance_evidence-graph_get
- Tags: governance, evidence, graph

### Governance Evidence Publication Get

Retrieves published evidence for competitor parity claims

- Operation key: `governance.evidence-publication.get`
- Domain: governance
- Metadata: Registry
- Goal: Provide verifiable evidence for governance and parity claims
- Context: Used by the CompetitorParityEvidenceCard component
- Stability: experimental
- Auth: user
- MCP tool: governance_evidence-publication_get
- Tags: governance, evidence, parity

### Governance Evidence Scorecard Monthly Get

Not available

- Operation key: `governance.evidence-scorecard.monthly.get`
- Domain: governance
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Governance Evidence Scorecard Quarterly Get

Not available

- Operation key: `governance.evidence-scorecard.quarterly.get`
- Domain: governance
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Governance Growth Diagnostics Get

Not available

- Operation key: `governance.growth-diagnostics.get`
- Domain: governance
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Governance Policy Get

Get operation-level governance policy rules

- Operation key: `governance.policy.get`
- Domain: governance
- Metadata: Registry
- Goal: Expose current governance policy for UI, API, and MCP checks
- Context: Risk and trust controls for parallel execution
- Stability: experimental
- Auth: user
- MCP tool: governance_policy_get
- Tags: governance, policy, risk

### Governance Policy Set

Set operation-level governance policy rules

- Operation key: `governance.policy.set`
- Domain: governance
- Metadata: Registry
- Goal: Enforce explicit risk-class policy behavior for critical operations
- Context: Risk and trust controls for parallel execution
- Stability: experimental
- Auth: user
- MCP tool: governance_policy_set
- Tags: governance, policy, risk

### Governance Policy Simulate

Simulate governance and automation policy outcomes for scenarios

- Operation key: `governance.policy.simulate`
- Domain: governance
- Metadata: Registry
- Goal: Make autonomy policy impacts explainable before enablement
- Context: Trust and governance policy simulation workspace
- Stability: experimental
- Auth: user
- MCP tool: governance_policy_simulate
- Tags: governance, policy, simulation, trust

### Governance Production Hardening Gates Get

Not available

- Operation key: `governance.production-hardening-gates.get`
- Domain: governance
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Governance Release Gate Alarms Get

Not available

- Operation key: `governance.release-gate-alarms.get`
- Domain: governance
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Governance Risk Assessment Evaluate

Evaluate operation risk class and approval requirement

- Operation key: `governance.risk-assessment.evaluate`
- Domain: governance
- Metadata: Registry
- Goal: Standardize risk scoring before write-path execution
- Context: Trust and governance controls for aggressive parallel execution
- Stability: experimental
- Auth: user
- MCP tool: governance_risk-assessment_evaluate
- Tags: governance, risk-assessment, policy

### Governance Rollback Trigger

Not available

- Operation key: `governance.rollback.trigger`
- Domain: governance
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Governance Runtime Eval Suite Get

Not available

- Operation key: `governance.runtime-eval-suite.get`
- Domain: governance
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Governance Runtime Optimizer Get

Not available

- Operation key: `governance.runtime-optimizer.get`
- Domain: governance
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Governance Runtime Stress Simulation Get

Not available

- Operation key: `governance.runtime-stress-simulation.get`
- Domain: governance
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Governance Schedule Policy Apply Set

Set scheduling apply-policy constraints

- Operation key: `governance.schedule-policy.apply.set`
- Domain: governance
- Metadata: Registry
- Goal: Control auto-apply and explicit approval requirements by risk class
- Context: Calendar and booking governance trust controls
- Stability: experimental
- Auth: user
- MCP tool: governance_schedule-policy_apply_set
- Tags: governance, schedule, apply-policy

### Governance Schedule Policy Draft Get

Get scheduling draft-policy constraints

- Operation key: `governance.schedule-policy.draft.get`
- Domain: governance
- Metadata: Registry
- Goal: Expose draft-first scheduling policy bounds by risk class
- Context: Calendar and booking governance trust controls
- Stability: experimental
- Auth: user
- MCP tool: governance_schedule-policy_draft_get
- Tags: governance, schedule, draft-policy

### Governance Sla Get

Returns SLA metrics for governance review operations

- Operation key: `governance.sla.get`
- Domain: governance
- Metadata: Registry
- Goal: Track review turnaround and compliance with SLA targets
- Context: Used by the Review Operations Center screen
- Stability: experimental
- Auth: user
- MCP tool: governance_sla_get
- Tags: governance, sla, metrics

### Governance Trust Level Get

Not available

- Operation key: `governance.trust-level.get`
- Domain: governance
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Graph Daily Note Get

Get or auto-create a day/week/month/year node for the workspace

- Operation key: `graph.daily-note.get`
- Domain: graph
- Metadata: Registry
- Goal: Provide automatic time-based knowledge organization
- Context: Knowledge graph domain. Auto-creates the daily note node if it does not exist for the given date and scope.
- Stability: experimental
- Auth: user
- MCP tool: graph_daily-note_get
- Tags: graph, daily-note, get

### Graph Node Archive

Soft-delete a node while preserving references for lineage

- Operation key: `graph.node.archive`
- Domain: graph
- Metadata: Registry
- Goal: Allow non-destructive removal with reference integrity
- Context: Knowledge graph domain. Archived nodes retain bi-directional references for traceability.
- Stability: experimental
- Auth: user
- MCP tool: graph_node_archive
- Tags: graph, node, archive

### Graph Node Create

Create a graph node with BlockNoteJS content, optional parent, and supertags

- Operation key: `graph.node.create`
- Domain: graph
- Metadata: Registry
- Goal: Allow users to add structured knowledge to the workspace graph
- Context: Knowledge graph domain. Nodes form the primary content unit with bi-directional references.
- Stability: experimental
- Auth: user
- MCP tool: graph_node_create
- Tags: graph, node, create

### Graph Node Get

Retrieve a node with resolved supertag fields and references

- Operation key: `graph.node.get`
- Domain: graph
- Metadata: Registry
- Goal: Allow reading individual graph nodes with full context
- Context: Knowledge graph domain. Returns resolved field values from applied supertags.
- Stability: experimental
- Auth: user
- MCP tool: graph_node_get
- Tags: graph, node, get

### Graph Node List

List child nodes of a parent with cursor-based pagination

- Operation key: `graph.node.list`
- Domain: graph
- Metadata: Registry
- Goal: Support browsing hierarchical node structures
- Context: Knowledge graph domain. Returns direct children of the specified parent node.
- Stability: experimental
- Auth: user
- MCP tool: graph_node_list
- Tags: graph, node, list

### Graph Node Move

Reparent a node to a different position in the graph

- Operation key: `graph.node.move`
- Domain: graph
- Metadata: Registry
- Goal: Support drag-and-drop reordering and cross-node moves
- Context: Knowledge graph domain. Validates no circular parentage is introduced.
- Stability: experimental
- Auth: user
- MCP tool: graph_node_move
- Tags: graph, node, move

### Graph Node Reference Create

Create a bi-directional reference between two nodes (mention, mirror, or backlink)

- Operation key: `graph.node.reference.create`
- Domain: graph
- Metadata: Registry
- Goal: Build the connective tissue between knowledge nodes
- Context: Knowledge graph domain. References enable `@`-mention, mirroring, and backlink discovery.
- Stability: experimental
- Auth: user
- MCP tool: graph_node_reference_create
- Tags: graph, node, reference, create

### Graph Node Update

Update node content, description, or field values

- Operation key: `graph.node.update`
- Domain: graph
- Metadata: Registry
- Goal: Allow users to modify existing graph nodes
- Context: Knowledge graph domain. Supports partial updates to content and metadata.
- Stability: experimental
- Auth: user
- MCP tool: graph_node_update
- Tags: graph, node, update

### Graph Search Execute

Execute a search query and return matching nodes with pagination

- Operation key: `graph.search.execute`
- Domain: graph
- Metadata: Registry
- Goal: Power live search results across the knowledge graph
- Context: Knowledge graph domain. Supports supertag, field, date, text, and hierarchy filters.
- Stability: experimental
- Auth: user
- MCP tool: graph_search_execute
- Tags: graph, search, execute

### Graph Search List

List saved searches in a workspace

- Operation key: `graph.search.list`
- Domain: graph
- Metadata: Registry
- Goal: Support browsing and managing saved searches
- Context: Knowledge graph domain. Returns paginated saved search definitions.
- Stability: experimental
- Auth: user
- MCP tool: graph_search_list
- Tags: graph, search, list

### Graph Supertag Apply

Apply a supertag to a node, auto-populating fields from defaults

- Operation key: `graph.supertag.apply`
- Domain: graph
- Metadata: Registry
- Goal: Allow users to tag nodes for structured data capture
- Context: Knowledge graph domain. Multiple supertags can coexist on a single node with merged fields.
- Stability: experimental
- Auth: user
- MCP tool: graph_supertag_apply
- Tags: graph, supertag, apply

### Graph Supertag Define

Create a supertag definition with field schema and optional inheritance

- Operation key: `graph.supertag.define`
- Domain: graph
- Metadata: Registry
- Goal: Allow structured typing of graph nodes through supertag definitions
- Context: Knowledge graph domain. Supertags define field schemas, can inherit from parents, and optionally bridge to ContractSpec contracts.
- Stability: experimental
- Auth: user
- MCP tool: graph_supertag_define
- Tags: graph, supertag, define

### Graph Supertag Get

Retrieve a supertag definition with resolved inheritance chain

- Operation key: `graph.supertag.get`
- Domain: graph
- Metadata: Registry
- Goal: Allow reading supertag schemas with merged inherited fields
- Context: Knowledge graph domain. Walks the inheritsFrom chain and merges fields from ancestors.
- Stability: experimental
- Auth: user
- MCP tool: graph_supertag_get
- Tags: graph, supertag, get

### Graph Supertag List

List all supertag definitions in a workspace

- Operation key: `graph.supertag.list`
- Domain: graph
- Metadata: Registry
- Goal: Support supertag browsing, search, and management UIs
- Context: Knowledge graph domain. Returns paginated supertag definitions with field counts.
- Stability: experimental
- Auth: user
- MCP tool: graph_supertag_list
- Tags: graph, supertag, list

### Growth Operator Apply

Not available

- Operation key: `growth-operator.apply`
- Domain: growth-operator
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Growth Operator Config Get

Not available

- Operation key: `growth-operator.config.get`
- Domain: growth-operator
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Growth Operator Drift Summary

Get triad drift summary (signup, active, churn) for a workspace

- Operation key: `growth-operator.drift-summary`
- Domain: growth-operator
- Metadata: Registry
- Goal: Surface metric breaches for operate dashboards
- Context: Growth operator domain. Aggregates D0/D1/D3/D7/D30 checkpoint breaches.
- Stability: experimental
- Auth: user
- MCP tool: growth-operator_drift-summary
- Tags: growth-operator, drift, triad

### Growth Operator Intervention Get

Not available

- Operation key: `growth-operator.intervention.get`
- Domain: growth-operator
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Growth Operator Interventions List

List growth interventions with filtering and pagination

- Operation key: `growth-operator.interventions-list`
- Domain: growth-operator
- Metadata: Registry
- Goal: Allow operate surfaces to inspect and control autonomous behavior
- Context: Growth operator domain. Returns interventions with state, lane, and decision.
- Stability: experimental
- Auth: user
- MCP tool: growth-operator_interventions-list
- Tags: growth-operator, interventions, audit

### Growth Operator Outcome History

Get checkpoint verification outcome history

- Operation key: `growth-operator.outcome-history`
- Domain: growth-operator
- Metadata: Registry
- Goal: Surface before/after evidence for applied interventions
- Context: Growth operator domain. Returns D0/D1/D3/D7/D30 verification records.
- Stability: experimental
- Auth: user
- MCP tool: growth-operator_outcome-history
- Tags: growth-operator, outcomes, verification

### Growth Operator Pause

Pause autonomous growth operator for a workspace

- Operation key: `growth-operator.pause`
- Domain: growth-operator
- Metadata: Registry
- Goal: Allow one-click kill-switch when autonomous behavior needs to stop
- Context: Growth operator domain. Stops new interventions from being applied.
- Stability: experimental
- Auth: user
- MCP tool: growth-operator_pause
- Tags: growth-operator, pause, autonomy

### Integration Data Analytics Events List

List analytics events (PostHog) with filters

- Operation key: `integration-data.analytics-events.list`
- Domain: integration-data
- Metadata: Registry
- Goal: Allow AI agents to browse synced analytics events from PostHog
- Context: Integration data domain. MCP tool cursorpm_integrationData_listAnalyticsEvents.
- Stability: experimental
- Auth: user
- MCP tool: integration-data_analytics-events_list
- Tags: integration-data, analytics-events, list

### Integration Data Calendar Events List

List calendar events (Google, Microsoft) with filters

- Operation key: `integration-data.calendar-events.list`
- Domain: integration-data
- Metadata: Registry
- Goal: Allow AI agents to browse synced calendar events from connectors
- Context: Integration data domain. MCP tool cursorpm_integrationData_listCalendarEvents.
- Stability: experimental
- Auth: user
- MCP tool: integration-data_calendar-events_list
- Tags: integration-data, calendar-events, list

### Integration Data Feed List

List normalized integration records across all entity types

- Operation key: `integration-data.feed.list`
- Domain: integration-data
- Metadata: Registry
- Goal: Allow AI agents and UI surfaces to browse integration data through one canonical feed
- Context: Integration intelligence domain. Aggregates messages, social posts, calendar events, email threads, analytics events, session replays, feature flag snapshots, and analytics logs.
- Stability: experimental
- Auth: user
- MCP tool: integration-data_feed_list
- Tags: integration-data, feed, normalized

### Integration Data Health Get

Get integration data health metrics, attribution counts, and sync freshness

- Operation key: `integration-data.health.get`
- Domain: integration-data
- Metadata: Registry
- Goal: Allow operators and AI agents to verify whether synced integration data is attributable and feeding the loop
- Context: Integration intelligence domain. Reports total counts, unattributed rows, derivation lag, and recent sync state.
- Stability: experimental
- Auth: user
- MCP tool: integration-data_health_get
- Tags: integration-data, health

### Integration Data Messages List

List integration messages (Slack, Intercom) with filters

- Operation key: `integration-data.messages.list`
- Domain: integration-data
- Metadata: Registry
- Goal: Allow AI agents to browse synced messages from connectors
- Context: Integration data domain. MCP tool cursorpm_integrationData_listMessages.
- Stability: experimental
- Auth: user
- MCP tool: integration-data_messages_list
- Tags: integration-data, messages, list

### Integration Data Record Get

Get one normalized integration record with lineage metadata

- Operation key: `integration-data.record.get`
- Domain: integration-data
- Metadata: Registry
- Goal: Allow API, MCP, and UI callers to inspect a single integration record
- Context: Integration intelligence domain. Returns one canonical record with related feedback linkage and derivation state.
- Stability: experimental
- Auth: user
- MCP tool: integration-data_record_get
- Tags: integration-data, record, detail

### Integration Data Slack Threads List

List normalized Slack thread records with Slack-specific filters

- Operation key: `integration-data.slack-threads.list`
- Domain: integration-data
- Metadata: Registry
- Goal: Allow AI and UI callers to browse Slack-native work queues and thread context
- Context: Integration intelligence domain. Returns Slack thread summaries with assistant and promotion state.
- Stability: experimental
- Auth: user
- MCP tool: integration-data_slack-threads_list
- Tags: integration-data, slack, threads, list

### Integration Data Social Posts List

List social posts (LinkedIn) with filters

- Operation key: `integration-data.social-posts.list`
- Domain: integration-data
- Metadata: Registry
- Goal: Allow AI agents to browse synced social posts from connectors
- Context: Integration data domain. MCP tool cursorpm_integrationData_listSocialPosts.
- Stability: experimental
- Auth: user
- MCP tool: integration-data_social-posts_list
- Tags: integration-data, social-posts, list

### Integration Data Summary Get

Get aggregated counts by entity type and provider

- Operation key: `integration-data.summary.get`
- Domain: integration-data
- Metadata: Registry
- Goal: Allow AI agents to see integration data overview
- Context: Integration data domain. MCP tool cursorpm_integrationData_getSummary.
- Stability: experimental
- Auth: user
- MCP tool: integration-data_summary_get
- Tags: integration-data, summary

### Integration Data Vcs Commits List

List synced VCS commits from normalized integration data

- Operation key: `integration-data.vcs-commits.list`
- Domain: integration-data
- Metadata: Registry
- Goal: Allow UI and AI agents to browse GitHub commits from connector sync
- Context: Integration data domain. Reads normalized vcs_commit rows instead of live provider data.
- Stability: experimental
- Auth: user
- MCP tool: integration-data_vcs-commits_list
- Tags: integration-data, vcs, commits

### Integration Data Vcs Issues List

List synced VCS issues from normalized integration data

- Operation key: `integration-data.vcs-issues.list`
- Domain: integration-data
- Metadata: Registry
- Goal: Allow UI and AI agents to browse synced GitHub issues
- Context: Integration data domain. Reads normalized vcs_issue rows instead of live provider data.
- Stability: experimental
- Auth: user
- MCP tool: integration-data_vcs-issues_list
- Tags: integration-data, vcs, issues

### Integration Data Vcs Pull Requests List

List synced VCS pull requests from normalized integration data

- Operation key: `integration-data.vcs-pull-requests.list`
- Domain: integration-data
- Metadata: Registry
- Goal: Allow UI and AI agents to browse synced PRs without live GitHub calls
- Context: Integration data domain. Reads normalized vcs_pull_request rows instead of live provider data.
- Stability: experimental
- Auth: user
- MCP tool: integration-data_vcs-pull-requests_list
- Tags: integration-data, vcs, pull-requests

### Loop Evidence Get

Fetch loop evidence records for claims and audits

- Operation key: `loop.evidence.get`
- Domain: loop
- Metadata: Registry
- Goal: Make growth and trust claims evidence-backed and queryable
- Context: Growth-loop evidence query surface.
- Stability: experimental
- Auth: user
- MCP tool: loop_evidence_get
- Tags: loop, evidence, query

### Loop Metrics Get

Fetch loop-level execution metrics

- Operation key: `loop.metrics.get`
- Domain: loop
- Metadata: Registry
- Goal: Provide measurable quality and throughput views for governance and growth
- Context: Growth-loop analytics query surface.
- Stability: experimental
- Auth: user
- MCP tool: loop_metrics_get
- Tags: loop, metrics, query

### Loop Run Cancel

Cancel an in-flight workflow-backed loop run

- Operation key: `loop.run.cancel`
- Domain: loop
- Metadata: Registry
- Goal: Stop a durable loop run without mutating hidden in-memory state
- Context: Workflow-backed loop runtime cancellation surface.
- Stability: experimental
- Auth: user
- MCP tool: loop_run_cancel
- Tags: loop, run, cancel

### Loop Run Checkpoints Get

List replayable checkpoints for a run

- Operation key: `loop.run.checkpoints.get`
- Domain: loop
- Metadata: Registry
- Goal: Support governed replay-from-step workflows
- Context: Growth-loop orchestration replay query surface.
- Stability: experimental
- Auth: user
- MCP tool: loop_run_checkpoints_get
- Tags: loop, run, checkpoint, query

### Loop Run Get

Fetch one loop run with lineage-aware state

- Operation key: `loop.run.get`
- Domain: loop
- Metadata: Registry
- Goal: Provide run visibility for replay, takeover, and audit workflows
- Context: Growth-loop orchestration query surface.
- Stability: experimental
- Auth: user
- MCP tool: loop_run_get
- Tags: loop, run, query

### Loop Run Replay From Checkpoint

Replay a completed run from a governed checkpoint

- Operation key: `loop.run.replay_from_checkpoint`
- Domain: loop
- Metadata: Registry
- Goal: Allow humans to edit step state and safely re-run remaining execution
- Context: Growth-loop orchestration domain with checkpoint replay and idempotency guarantees.
- Stability: experimental
- Auth: user
- MCP tool: loop_run_replay_from_checkpoint
- Tags: loop, replay, checkpoint

### Loop Run Replay Preview Get

Preview counterfactual replay impact for a checkpoint

- Operation key: `loop.run.replay_preview.get`
- Domain: loop
- Metadata: Registry
- Goal: Expose simulation-first replay guidance before stateful reruns
- Context: Growth-loop replay planning surface for deterministic simulation and downgrade recommendations.
- Stability: experimental
- Auth: user
- MCP tool: loop_run_replay_preview_get
- Tags: loop, replay, preview, query

### Loop Run Start

Start a new AI-native growth loop run

- Operation key: `loop.run.start`
- Domain: loop
- Metadata: Registry
- Goal: Create a durable run entry point for cross-domain orchestration
- Context: Growth-loop orchestration domain with policy-gated automation.
- Stability: experimental
- Auth: user
- MCP tool: loop_run_start
- Tags: loop, run, start

### Loop Run Wait Resume

Resume an explicit workflow wait for a loop run

- Operation key: `loop.run.wait.resume`
- Domain: loop
- Metadata: Registry
- Goal: Apply reviewer decisions to durable approval waits
- Context: Workflow-backed loop runtime wait-resolution surface.
- Stability: experimental
- Auth: user
- MCP tool: loop_run_wait_resume
- Tags: loop, run, wait, resume

### Loop Step Patch

Patch one loop step payload before replay or resume

- Operation key: `loop.step.patch`
- Domain: loop
- Metadata: Registry
- Goal: Enable governed human edits to deterministic run checkpoints
- Context: Growth-loop orchestration domain with auditable step overrides.
- Stability: experimental
- Auth: user
- MCP tool: loop_step_patch
- Tags: loop, step, patch

### Meeting Decision Extract

Extract decisions, risks, and action items from transcript evidence

- Operation key: `meeting.decision.extract`
- Domain: meeting
- Metadata: Registry
- Goal: Turn unstructured meeting dialogue into execution-ready outcomes
- Context: Meeting intelligence rebuild extraction phase
- Stability: experimental
- Auth: user
- MCP tool: meeting_decision_extract
- Tags: meeting, decision, extraction

### Meeting Execution Followthrough Draft Preview

Preview the governed follow-through draft for a review item.

- Operation key: `meeting-execution.followthrough-draft.preview`
- Domain: meeting-execution
- Metadata: Registry
- Goal: Show operators the draft before approval or sync.
- Context: Meeting execution review workflow.
- Stability: experimental
- Auth: user
- MCP tool: meeting-execution_followthrough-draft_preview
- Tags: meeting-execution, draft, preview

### Meeting Execution Launch

Not available

- Operation key: `meeting.execution.launch`
- Domain: meeting
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Meeting Execution Outcome Update

Verify, fail, or roll back a synced outcome.

- Operation key: `meeting-execution.outcome-update`
- Domain: meeting-execution
- Metadata: Registry
- Goal: Keep downstream verification and rollback first-class.
- Context: Meeting execution outcome workflow.
- Stability: experimental
- Auth: user
- MCP tool: meeting-execution_outcome-update
- Tags: meeting-execution, outcome, verification

### Meeting Execution Pilot Scorecard Get

Get launch-gate metrics for the meeting execution pilot.

- Operation key: `meeting-execution.pilot-scorecard.get`
- Domain: meeting-execution
- Metadata: Registry
- Goal: Surface trust and usage gates for pilot rollout decisions.
- Context: Meeting execution pilot admin workflow.
- Stability: experimental
- Auth: user
- MCP tool: meeting-execution_pilot-scorecard_get
- Tags: meeting-execution, pilot, scorecard

### Meeting Execution Review Approve

Approve a review item for downstream sync.

- Operation key: `meeting-execution.review-approve`
- Domain: meeting-execution
- Metadata: Registry
- Goal: Keep review and sync separate while recording explicit approval.
- Context: Meeting execution approval workflow.
- Stability: experimental
- Auth: user
- MCP tool: meeting-execution_review-approve
- Tags: meeting-execution, review, approve

### Meeting Execution Review Edit

Edit a review item while preserving lineage and trust state.

- Operation key: `meeting-execution.review-edit`
- Domain: meeting-execution
- Metadata: Registry
- Goal: Allow operators to refine follow-through before approval.
- Context: Meeting execution review workflow.
- Stability: experimental
- Auth: user
- MCP tool: meeting-execution_review-edit
- Tags: meeting-execution, review, edit

### Meeting Execution Review Item Get

Get a review item with lineage, sync history, and outcomes.

- Operation key: `meeting-execution.review-item.get`
- Domain: meeting-execution
- Metadata: Registry
- Goal: Support review detail and desktop quick review parity.
- Context: Meeting execution review detail.
- Stability: experimental
- Auth: user
- MCP tool: meeting-execution_review-item_get
- Tags: meeting-execution, review-item, lineage

### Meeting Execution Review Queue List

List reviewable meeting execution items.

- Operation key: `meeting-execution.review-queue.list`
- Domain: meeting-execution
- Metadata: Registry
- Goal: Provide the canonical queue for review and sync work.
- Context: Meeting execution review queue.
- Stability: experimental
- Auth: user
- MCP tool: meeting-execution_review-queue_list
- Tags: meeting-execution, review-queue

### Meeting Execution Review Reject

Reject a review item with a structured reason code.

- Operation key: `meeting-execution.review-reject`
- Domain: meeting-execution
- Metadata: Registry
- Goal: Capture human rejection without losing lineage.
- Context: Meeting execution review workflow.
- Stability: experimental
- Auth: user
- MCP tool: meeting-execution_review-reject
- Tags: meeting-execution, review, reject

### Meeting Execution Sync Apply

Apply a reviewed meeting follow-through to the target system.

- Operation key: `meeting-execution.sync-apply`
- Domain: meeting-execution
- Metadata: Registry
- Goal: Turn approved review items into governed external mutations.
- Context: Meeting execution sync workflow.
- Stability: experimental
- Auth: user
- MCP tool: meeting-execution_sync-apply
- Tags: meeting-execution, sync, apply

### Meeting Execution Sync Preview

Preview a target-system sync for an approved review item.

- Operation key: `meeting-execution.sync-preview`
- Domain: meeting-execution
- Metadata: Registry
- Goal: Show destination impact before external mutation.
- Context: Meeting execution sync workflow.
- Stability: experimental
- Auth: user
- MCP tool: meeting-execution_sync-preview
- Tags: meeting-execution, sync, preview

### Meeting History List

List recently active meetings for rapid re-entry

- Operation key: `meeting.history.list`
- Domain: meeting
- Metadata: Registry
- Goal: Expose recent meeting history without re-running provider sync
- Context: Meeting intelligence history panel
- Stability: experimental
- Auth: user
- MCP tool: meeting_history_list
- Tags: meeting, history, recent

### Meeting Intelligence Meeting List

List provider-backed meetings with review metadata

- Operation key: `meeting-intelligence.meeting.list`
- Domain: meeting-intelligence
- Metadata: Registry
- Goal: Power inbox, search, and meeting history surfaces from one contract
- Context: Meeting intelligence operate catalog
- Stability: experimental
- Auth: user
- MCP tool: meeting-intelligence_meeting_list
- Tags: meeting, list, catalog, operate

### Meeting Provider Ingest

Sync one or more provider-backed meetings into meeting intelligence

- Operation key: `meeting.provider.ingest`
- Domain: meeting
- Metadata: Registry
- Goal: Replace synthetic meeting ingestion with normalized competitor-backed provider fan-out
- Context: Meeting intelligence provider ingestion
- Stability: experimental
- Auth: user
- MCP tool: meeting_provider_ingest
- Tags: meeting, provider, ingestion, parity

### Meeting Recording Ingest

Ingest and normalize meeting recording metadata

- Operation key: `meeting.recording.ingest`
- Domain: meeting
- Metadata: Registry
- Goal: Create a deterministic recording artifact before transcript generation
- Context: Meeting intelligence rebuild phase 0
- Stability: experimental
- Auth: user
- MCP tool: meeting_recording_ingest
- Tags: meeting, recording, ingestion

### Meeting Search

Search meetings across titles, participants, highlights, and transcript text

- Operation key: `meeting.search`
- Domain: meeting
- Metadata: Registry
- Goal: Deliver Fireflies and tl;dv class searchable meeting history
- Context: Meeting intelligence search experience
- Stability: experimental
- Auth: user
- MCP tool: meeting_search
- Tags: meeting, search, history

### Meeting Signal Quality Score

Score extraction quality, contradiction, and ambiguity signals

- Operation key: `meeting.signal.quality.score`
- Domain: meeting
- Metadata: Registry
- Goal: Provide confidence-aware trust context before downstream promotion
- Context: Meeting intelligence confidence and contradiction scoring
- Stability: experimental
- Auth: user
- MCP tool: meeting_signal_quality_score
- Tags: meeting, quality, confidence, trust

### Meeting Summary Normalize

Normalize a meeting transcript into actionable intelligence

- Operation key: `meeting.summary.normalize`
- Domain: meeting
- Metadata: Registry
- Goal: Convert transcript noise into decision and action primitives
- Context: Phase 0 foundation for meeting intelligence domain
- Stability: experimental
- Auth: user
- MCP tool: meeting_summary_normalize
- Tags: meeting, intelligence, competition-killer

### Meeting Transcript Generate

Generate a speaker-aware transcript from an ingested recording

- Operation key: `meeting.transcript.generate`
- Domain: meeting
- Metadata: Registry
- Goal: Produce normalized transcript segments for downstream extraction
- Context: Meeting intelligence rebuild phase 1 transcript pipeline
- Stability: experimental
- Auth: user
- MCP tool: meeting_transcript_generate
- Tags: meeting, transcript, speaker-attribution

### Patch Delete

Soft-deletes an action item (patch) — reversible via restore

- Operation key: `patch.delete`
- Domain: patch
- Metadata: Registry
- Goal: Allow users to remove action items that are no longer needed
- Context: Part of the Change Layer. Execution artifact; soft-delete + restore.
- Stability: experimental
- Auth: user
- MCP tool: patch_delete
- Tags: change, patch, delete, action-item, loop-crud

### Patch Get

Get a single compiled patch by ID

- Operation key: `patch.get`
- Domain: patch
- Metadata: Registry
- Goal: Allow users to inspect full patch details including intent and impacts
- Context: Part of the Change Layer. Returns the complete patch record for the change detail view.
- Stability: experimental
- Auth: user
- MCP tool: patch_get
- Tags: change, patch, detail

### Patch Update

Updates an action item (patch) status

- Operation key: `patch.update`
- Domain: patch
- Metadata: Registry
- Goal: Allow users to transition action item lifecycle (e.g. mark as applied, reject)
- Context: Part of the Change Layer. Valid statuses: draft, compiled, committed, applied, rejected.
- Stability: experimental
- Auth: user
- MCP tool: patch_update
- Tags: change, patch, update, action-item

### Pattern Delete

Suppresses a pattern (derived entity) — optional restore

- Operation key: `pattern.delete`
- Domain: pattern
- Metadata: Registry
- Goal: Allow users to dismiss patterns that are no longer relevant
- Context: Part of the Correlation Layer. Derived signal; suppress/dismiss by default.
- Stability: experimental
- Auth: user
- MCP tool: pattern_delete
- Tags: correlation, pattern, delete, suppress, loop-crud

### Pattern Get

Get a specific detected pattern by ID

- Operation key: `pattern.get`
- Domain: pattern
- Metadata: Registry
- Goal: Allow users to inspect full pattern details including citations and confidence
- Context: Part of the Correlation Layer. Returns the complete pattern record for the pattern detail view.
- Stability: experimental
- Auth: user
- MCP tool: pattern_get
- Tags: correlation, pattern, detail, citations

### Pattern List

Lists detected patterns with filters and ranking by score

- Operation key: `pattern.list`
- Domain: pattern
- Metadata: Registry
- Goal: Allow users to browse, filter, and drill into correlation patterns
- Context: Part of the Correlation Layer (M2). Patterns are ranked by source diversity, recency, severity, and user diversity.
- Stability: experimental
- Auth: user
- MCP tool: pattern_list
- Tags: correlation, patterns, m2

### Pitch Ops Packet Advance

Not available

- Operation key: `pitch-ops.packet-advance`
- Domain: pitch-ops
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Pitch Ops Packet Create

Not available

- Operation key: `pitch-ops.packet-create`
- Domain: pitch-ops
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Pitch Ops Packet Get

Not available

- Operation key: `pitch-ops.packet-get`
- Domain: pitch-ops
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Pitch Ops Packet List

Not available

- Operation key: `pitch-ops.packet-list`
- Domain: pitch-ops
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### PM Actionitem List

List compiled action items (actionItems) with pagination

- Operation key: `pm.actionitem.list`
- Domain: pm
- Metadata: Registry
- Goal: Allow PM agents to browse compiled action items
- Context: PM MCP cross-domain tool for change layer
- Stability: experimental
- Auth: user
- MCP tool: pm_actionitem_list
- Tags: pm, change, action-items, list, pagination

### PM Attachment Create

Create an attachment for a PM issue

- Operation key: `pm.attachment.create`
- Domain: pm
- Metadata: Registry
- Goal: Support file evidence and artifact sharing on issues
- Context: Core PM issue collaboration parity
- Stability: experimental
- Auth: user
- MCP tool: pm_attachment_create
- Tags: pm, attachment, issue-depth

### PM Attachment Delete

Delete a PM issue attachment

- Operation key: `pm.attachment.delete`
- Domain: pm
- Metadata: Registry
- Goal: Allow operators to remove outdated or unsafe files
- Context: Core PM issue collaboration parity
- Stability: experimental
- Auth: user
- MCP tool: pm_attachment_delete
- Tags: pm, attachment, delete

### PM Attachment List

List attachments for a PM issue

- Operation key: `pm.attachment.list`
- Domain: pm
- Metadata: Registry
- Goal: Render durable issue evidence and previews
- Context: Core PM issue collaboration parity
- Stability: experimental
- Auth: user
- MCP tool: pm_attachment_list
- Tags: pm, attachment, query

### PM Board Config Get

Read the persisted PM board lane order

- Operation key: `pm.board-config.get`
- Domain: pm
- Metadata: Registry
- Goal: Load workspace defaults and project overrides for PM board layout
- Context: PM workspace customization
- Stability: experimental
- Auth: user
- MCP tool: pm_board-config_get
- Tags: pm, board, configuration

### PM Board Config Set

Persist the PM board lane order

- Operation key: `pm.board-config.set`
- Domain: pm
- Metadata: Registry
- Goal: Save workspace defaults and project overrides for PM board layout
- Context: PM workspace customization
- Stability: experimental
- Auth: user
- MCP tool: pm_board-config_set
- Tags: pm, board, configuration

### PM Cycle Commit

Commit a planned cycle, locking its scope and starting execution

- Operation key: `pm.cycle.commit`
- Domain: pm
- Metadata: Registry
- Goal: Lock cycle scope and transition to execution
- Context: Phase 0 PM stack contract surface
- Stability: experimental
- Auth: user
- MCP tool: pm_cycle_commit
- Tags: pm, cycle, commit, competition-killer

### PM Cycle List

List PM cycles in a workspace

- Operation key: `pm.cycle.list`
- Domain: pm
- Metadata: Registry
- Goal: Retrieve cycles with dates, status, and issue counts
- Context: PM cycles screen at /operate/project/cycles
- Stability: experimental
- Auth: user
- MCP tool: pm_cycle_list
- Tags: pm, cycle, list

### PM Cycle Plan

Create a PM cycle plan from issue backlog

- Operation key: `pm.cycle.plan`
- Domain: pm
- Metadata: Registry
- Goal: Allow deterministic cycle planning bounded by capacity
- Context: Phase 0 PM stack contract surface
- Stability: experimental
- Auth: user
- MCP tool: pm_cycle_plan
- Tags: pm, cycle, planning, competition-killer

### PM Cycle Review

Review a completed cycle, capturing velocity and retrospective data

- Operation key: `pm.cycle.review`
- Domain: pm
- Metadata: Registry
- Goal: Capture cycle completion metrics and retrospective
- Context: Phase 0 PM stack contract surface
- Stability: experimental
- Auth: user
- MCP tool: pm_cycle_review
- Tags: pm, cycle, review, competition-killer

### PM Dependency Detect

Detect blocking dependencies among issues

- Operation key: `pm.dependency.detect`
- Domain: pm
- Metadata: Registry
- Goal: Expose dependency graph risks before execution begins
- Context: Phase 0 PM stack contract surface
- Stability: experimental
- Auth: user
- MCP tool: pm_dependency_detect
- Tags: pm, dependency, risk, competition-killer

### PM Dependency Resolve

Resolve or dismiss a detected dependency between issues

- Operation key: `pm.dependency.resolve`
- Domain: pm
- Metadata: Registry
- Goal: Record dependency resolution decision
- Context: Phase 0 PM stack contract surface
- Stability: experimental
- Auth: user
- MCP tool: pm_dependency_resolve
- Tags: pm, dependency, resolve, competition-killer

### PM Feedback List

List feedback items with server pagination and sorting

- Operation key: `pm.feedback.list`
- Domain: pm
- Metadata: Registry
- Goal: Allow PM agents to browse ingested feedback items in table form
- Context: PM MCP cross-domain tool for feedback layer
- Stability: experimental
- Auth: user
- MCP tool: pm_feedback_list
- Tags: pm, feedback, list, pagination, table, sorting

### PM Focus List

List focus zones with pagination

- Operation key: `pm.focus.list`
- Domain: pm
- Metadata: Registry
- Goal: Allow PM agents to browse declared focus zones
- Context: PM MCP cross-domain tool for decision layer
- Stability: experimental
- Auth: user
- MCP tool: pm_focus_list
- Tags: pm, decision, focus, list, pagination

### PM Issue Auto Enrich

AI-powered enrichment suggestions for a PM issue (labels, priority, links, assignee, custom fields)

- Operation key: `pm.issue.auto-enrich`
- Domain: pm
- Metadata: Registry
- Goal: Enable agentic auto-population of issue metadata
- Context: PM issue depth expansion -- AI-native patterns
- Stability: experimental
- Auth: user
- MCP tool: pm_issue_auto-enrich
- Tags: pm, ai-native, auto-enrich, agentic

### PM Issue Close

Close a PM issue

- Operation key: `pm.issue.close`
- Domain: pm
- Metadata: Registry
- Goal: Finalize issue lifecycle with explicit closure metadata
- Context: Phase 0 PM stack contract surface
- Stability: experimental
- Auth: user
- MCP tool: pm_issue_close
- Tags: pm, issue, close, competition-killer

### PM Issue Create

Create a PM issue in the autonomous operations graph

- Operation key: `pm.issue.create`
- Domain: pm
- Metadata: Registry
- Goal: Establish a canonical issue primitive for the PM rebuild
- Context: Phase 0 foundation for competition killer pack PM domain
- Stability: experimental
- Auth: user
- MCP tool: pm_issue_create
- Tags: pm, issue, competition-killer

### PM Issue Link Create

Create a cross-domain link from a PM issue to any entity

- Operation key: `pm.issue.link.create`
- Domain: pm
- Metadata: Registry
- Goal: Enable deep cross-module issue relations
- Context: PM issue depth expansion -- cross-domain relations
- Stability: experimental
- Auth: user
- MCP tool: pm_issue_link_create
- Tags: pm, link, cross-domain, issue-depth

### PM Issue Link List

List all cross-domain links for a PM issue

- Operation key: `pm.issue.link.list`
- Domain: pm
- Metadata: Registry
- Goal: Retrieve issue relations across all domains
- Context: PM issue depth expansion -- cross-domain relations
- Stability: experimental
- Auth: user
- MCP tool: pm_issue_link_list
- Tags: pm, link, cross-domain, issue-depth

### PM Issue Link Remove

Remove a cross-domain link from a PM issue

- Operation key: `pm.issue.link.remove`
- Domain: pm
- Metadata: Registry
- Goal: Allow link cleanup on issues
- Context: PM issue depth expansion -- cross-domain relations
- Stability: experimental
- Auth: user
- MCP tool: pm_issue_link_remove
- Tags: pm, link, cross-domain, issue-depth

### PM Issue List

List all PM issues in a workspace

- Operation key: `pm.issue.list`
- Domain: pm
- Metadata: Registry
- Goal: Retrieve issues with title, status, priority, assignee, and more
- Context: PM MCP agentic context
- Stability: experimental
- Auth: user
- MCP tool: pm_issue_list
- Tags: pm, issue, list

### PM Issue Update

Update a PM issue fields and status

- Operation key: `pm.issue.update`
- Domain: pm
- Metadata: Registry
- Goal: Allow deterministic issue updates across PM workflows
- Context: Phase 0 PM stack contract surface
- Stability: experimental
- Auth: user
- MCP tool: pm_issue_update
- Tags: pm, issue, update, competition-killer

### PM Notification List

List PM autonomous notifications

- Operation key: `pm.notification.list`
- Domain: pm
- Metadata: Registry
- Goal: Support durable unread and history views for autonomous PM activity
- Context: PM autonomous review and notification surface
- Stability: experimental
- Auth: user
- MCP tool: pm_notification_list
- Tags: pm, notification, autonomous

### PM Notification Read

Mark PM autonomous notifications as read

- Operation key: `pm.notification.read`
- Domain: pm
- Metadata: Registry
- Goal: Support durable unread counts and inbox hygiene
- Context: PM autonomous review and notification surface
- Stability: experimental
- Auth: user
- MCP tool: pm_notification_read
- Tags: pm, notification, autonomous

### PM Pattern List

List detected patterns with filters and ranking by score

- Operation key: `pm.pattern.list`
- Domain: pm
- Metadata: Registry
- Goal: Allow PM agents to browse correlation patterns
- Context: PM MCP cross-domain tool for correlation layer
- Stability: experimental
- Auth: user
- MCP tool: pm_pattern_list
- Tags: pm, correlation, patterns, list

### PM Project Create

Create a PM project

- Operation key: `pm.project.create`
- Domain: pm
- Metadata: Registry
- Goal: Provide project-level planning root for PM stack rebuild
- Context: Phase 0 PM stack contract surface
- Stability: experimental
- Auth: user
- MCP tool: pm_project_create
- Tags: pm, project, competition-killer

### PM Project List

List PM projects in a workspace

- Operation key: `pm.project.list`
- Domain: pm
- Metadata: Registry
- Goal: Retrieve projects with name, status, and issue counts
- Context: PM project list for board and cycles
- Stability: experimental
- Auth: user
- MCP tool: pm_project_list
- Tags: pm, project, list

### PM Project Plan

Generate a cycle plan for a PM project

- Operation key: `pm.project.plan`
- Domain: pm
- Metadata: Registry
- Goal: Produce deterministic cycle plans from project issue backlog
- Context: Phase 0 PM stack contract surface
- Stability: experimental
- Auth: user
- MCP tool: pm_project_plan
- Tags: pm, project, planning, competition-killer

### PM Project Rebaseline

Rebaseline a PM project plan

- Operation key: `pm.project.rebaseline`
- Domain: pm
- Metadata: Registry
- Goal: Allow explicit project plan reset after scope or risk changes
- Context: Phase 0 PM stack contract surface
- Stability: experimental
- Auth: user
- MCP tool: pm_project_rebaseline
- Tags: pm, project, rebaseline, competition-killer

### PM Release Create

Create a PM release record for a project

- Operation key: `pm.release.create`
- Domain: pm
- Metadata: Registry
- Goal: Track versions, readiness, and release scope in native PM
- Context: Core PM parity for Linear initiatives/releases and Jira versions
- Stability: experimental
- Auth: user
- MCP tool: pm_release_create
- Tags: pm, release, versioning

### PM Release List

List PM releases for a workspace or project

- Operation key: `pm.release.list`
- Domain: pm
- Metadata: Registry
- Goal: Support release centers, roadmap filters, and readiness reviews
- Context: Core PM parity for release/version listing
- Stability: experimental
- Auth: user
- MCP tool: pm_release_list
- Tags: pm, release, query

### PM Release Update

Update PM release metadata and readiness

- Operation key: `pm.release.update`
- Domain: pm
- Metadata: Registry
- Goal: Keep release readiness and timing aligned with execution state
- Context: Core PM parity for release management
- Stability: experimental
- Auth: user
- MCP tool: pm_release_update
- Tags: pm, release, update

### PM View List

List saved issue views in a workspace

- Operation key: `pm.view.list`
- Domain: pm
- Metadata: Registry
- Goal: Retrieve available saved views for issue filtering
- Context: PM deep customization
- Stability: experimental
- Auth: user
- MCP tool: pm_view_list
- Tags: pm, view, deep-customization

### PM Workload Recommend

Recommend workload assignments for issue backlog

- Operation key: `pm.workload.recommend`
- Domain: pm
- Metadata: Registry
- Goal: Balance assignee workloads while respecting capacity
- Context: Phase 0 PM stack contract surface
- Stability: experimental
- Auth: user
- MCP tool: pm_workload_recommend
- Tags: pm, workload, recommendation, competition-killer

### Publish Node List

Not available

- Operation key: `publish.node.list`
- Domain: publish
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Publish Node Publish

Not available

- Operation key: `publish.node.publish`
- Domain: publish
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Rag Query Knowledge

Queries the product knowledge base with semantic search

- Operation key: `rag.query-knowledge`
- Domain: rag
- Metadata: Registry
- Goal: Provide the copilot engine with relevant product context during live calls
- Context: Desktop Live Copilot Phase 1. Searches the local vector store for relevant document chunks.
- Stability: experimental
- Auth: user
- MCP tool: rag_query-knowledge
- Tags: rag, knowledge, search, desktop

### Runtime Target Capability Check

Validate runtime operation support for a target surface and mode

- Operation key: `runtime.target.capability-check`
- Domain: runtime
- Metadata: Registry
- Goal: Enforce policy-consistent capability checks across all runtime channels
- Context: Phase 0 runtime target registry and capability parity guardrail
- Stability: experimental
- Auth: user
- MCP tool: runtime_target_capability-check
- Tags: runtime, target, capability, competition-killer

### Runtime Target Render

Render compiled view-model blocks for a specific target

- Operation key: `runtime.target.render`
- Domain: runtime
- Metadata: Registry
- Goal: Provide deterministic multi-target rendering from a shared view model
- Context: Phase 0 baseline for runtime target rendering
- Stability: experimental
- Auth: user
- MCP tool: runtime_target_render
- Tags: runtime, target, render, competition-killer

### Runtime Ui Block Generate

Generate policy-aware UI blocks from a compiled runtime view model

- Operation key: `runtime.ui-block.generate`
- Domain: runtime
- Metadata: Registry
- Goal: Deliver deterministic, auditable UI blocks for multi-target rendering
- Context: Phase 0 + Phase 1 runtime generation pipeline
- Stability: experimental
- Auth: user
- MCP tool: runtime_ui-block_generate
- Tags: runtime, ui-block, generator, competition-killer

### Runtime View Model Compile

Compile a surface payload into a target-specific view model

- Operation key: `runtime.view-model.compile`
- Domain: runtime
- Metadata: Registry
- Goal: Enable multi-target rendering from a shared runtime contract
- Context: Phase 0 baseline for runtime domain
- Stability: experimental
- Auth: user
- MCP tool: runtime_view-model_compile
- Tags: runtime, view-model, competition-killer

### Schedule Availability Compute

Compute availability windows and utilization for planning

- Operation key: `schedule.availability.compute`
- Domain: schedule
- Metadata: Registry
- Goal: Expose capacity-aware availability inputs for schedule preview
- Context: Calendar and booking stack rebuild phase 0
- Stability: experimental
- Auth: user
- MCP tool: schedule_availability_compute
- Tags: schedule, availability, capacity

### Schedule Booking Cancel

Cancel an existing booking

- Operation key: `schedule.booking.cancel`
- Domain: schedule
- Metadata: Registry
- Goal: Apply cancellation policy windows and persist booking state transitions
- Context: Public booking runtime cancellation operation
- Stability: experimental
- Auth: anonymous
- MCP tool: schedule_booking_cancel
- Tags: schedule, booking, cancel

### Schedule Booking Create

Create and confirm a booking from hold or direct slot selection

- Operation key: `schedule.booking.create`
- Domain: schedule
- Metadata: Registry
- Goal: Persist booking outcomes with policy-safe schedule writes and idempotency
- Context: Public booking runtime create operation
- Stability: experimental
- Auth: anonymous
- MCP tool: schedule_booking_create
- Tags: schedule, booking, create

### Schedule Booking Hold Create

Create a temporary hold on a candidate booking slot

- Operation key: `schedule.booking.hold.create`
- Domain: schedule
- Metadata: Registry
- Goal: Prevent double booking between slot selection and booking confirmation
- Context: Public booking runtime hold lifecycle
- Stability: experimental
- Auth: anonymous
- MCP tool: schedule_booking_hold_create
- Tags: schedule, booking, hold

### Schedule Booking Hold Release

Release a previously created slot hold

- Operation key: `schedule.booking.hold.release`
- Domain: schedule
- Metadata: Registry
- Goal: Free held inventory when booking is cancelled or abandoned
- Context: Public booking runtime hold lifecycle
- Stability: experimental
- Auth: anonymous
- MCP tool: schedule_booking_hold_release
- Tags: schedule, booking, hold

### Schedule Booking Link Create

Create a booking link with routing and policy defaults

- Operation key: `schedule.booking-link.create`
- Domain: schedule
- Metadata: Registry
- Goal: Enable controlled inbound booking for teams and owners
- Context: Calendar and booking stack rebuild phase 0
- Stability: experimental
- Auth: user
- MCP tool: schedule_booking-link_create
- Tags: schedule, booking-link, create

### Schedule Booking Link Disable

Disable a booking link while retaining auditability

- Operation key: `schedule.booking-link.disable`
- Domain: schedule
- Metadata: Registry
- Goal: Allow policy-safe booking shutdowns without deleting history
- Context: Calendar and booking stack rebuild phase 0
- Stability: experimental
- Auth: user
- MCP tool: schedule_booking-link_disable
- Tags: schedule, booking-link, disable

### Schedule Booking Link Route

Resolve and persist owner routing decision for a booking link

- Operation key: `schedule.booking-link.route`
- Domain: schedule
- Metadata: Registry
- Goal: Apply deterministic round-robin or priority routing at booking time
- Context: Booking runtime routing operation for scheduling stack
- Stability: experimental
- Auth: user
- MCP tool: schedule_booking-link_route
- Tags: schedule, booking, routing

### Schedule Booking Link Update

Update booking link metadata, owners, and routing strategy

- Operation key: `schedule.booking-link.update`
- Domain: schedule
- Metadata: Registry
- Goal: Keep booking links aligned with team capacity and ownership changes
- Context: Calendar and booking stack rebuild phase 0
- Stability: experimental
- Auth: user
- MCP tool: schedule_booking-link_update
- Tags: schedule, booking-link, update

### Schedule Booking List

List schedule bookings by workspace or link

- Operation key: `schedule.booking.list`
- Domain: schedule
- Metadata: Registry
- Goal: Expose operator-grade booking list for management screens
- Context: Booking management and operator workflows
- Stability: experimental
- Auth: user
- MCP tool: schedule_booking_list
- Tags: schedule, booking, list

### Schedule Booking Mark No Show

Mark a booking as no-show

- Operation key: `schedule.booking.mark-no-show`
- Domain: schedule
- Metadata: Registry
- Goal: Record that a participant did not attend a confirmed booking
- Context: Operator action after meeting time has passed
- Stability: experimental
- Auth: user
- MCP tool: schedule_booking_mark-no-show
- Tags: schedule, booking, no-show

### Schedule Booking Poll Cancel

Cancel an open booking poll

- Operation key: `schedule.booking-poll.cancel`
- Domain: schedule
- Metadata: Registry
- Goal: Stop a consensus scheduling process that should no longer continue
- Context: Operator-controlled poll lifecycle
- Stability: experimental
- Auth: user
- MCP tool: schedule_booking-poll_cancel
- Tags: schedule, booking-poll, cancel

### Schedule Booking Poll Create

Create a booking poll from candidate slots and invitees

- Operation key: `schedule.booking-poll.create`
- Domain: schedule
- Metadata: Registry
- Goal: Enable consensus scheduling for a booking link
- Context: Calendly-class meeting poll workflow
- Stability: experimental
- Auth: user
- MCP tool: schedule_booking-poll_create
- Tags: schedule, booking-poll, create

### Schedule Booking Poll Finalize

Finalize a booking poll onto a selected candidate slot

- Operation key: `schedule.booking-poll.finalize`
- Domain: schedule
- Metadata: Registry
- Goal: Turn consensus signals into an actual booking outcome
- Context: Operator review or auto-finalize poll closeout
- Stability: experimental
- Auth: user
- MCP tool: schedule_booking-poll_finalize
- Tags: schedule, booking-poll, finalize

### Schedule Booking Poll List

List booking polls for a workspace or booking link

- Operation key: `schedule.booking-poll.list`
- Domain: schedule
- Metadata: Registry
- Goal: Give operators visibility into poll status and consensus progress
- Context: Operate booking conversion and poll management
- Stability: experimental
- Auth: user
- MCP tool: schedule_booking-poll_list
- Tags: schedule, booking-poll, list

### Schedule Booking Poll Public Get

Retrieve a public booking poll and its vote state

- Operation key: `schedule.booking-poll.public.get`
- Domain: schedule
- Metadata: Registry
- Goal: Allow invitees to vote on a scheduling poll
- Context: Public poll view for consensus scheduling
- Stability: experimental
- Auth: anonymous
- MCP tool: schedule_booking-poll_public_get
- Tags: schedule, booking-poll, public

### Schedule Booking Poll Vote

Submit or replace invitee votes on a booking poll

- Operation key: `schedule.booking-poll.vote`
- Domain: schedule
- Metadata: Registry
- Goal: Capture consensus preferences for poll candidates
- Context: Public booking poll voting
- Stability: experimental
- Auth: anonymous
- MCP tool: schedule_booking-poll_vote
- Tags: schedule, booking-poll, vote

### Schedule Booking Reschedule

Reschedule an existing booking to a new slot

- Operation key: `schedule.booking.reschedule`
- Domain: schedule
- Metadata: Registry
- Goal: Apply reschedule policy windows while preserving booking lineage
- Context: Public booking runtime reschedule operation
- Stability: experimental
- Auth: anonymous
- MCP tool: schedule_booking_reschedule
- Tags: schedule, booking, reschedule

### Schedule Booking Slots Query

Query bookable slots for a public booking link

- Operation key: `schedule.booking.slots.query`
- Domain: schedule
- Metadata: Registry
- Goal: Provide conflict-safe, policy-aware slots for booking confirmation
- Context: Public booking runtime slot discovery operation
- Stability: experimental
- Auth: anonymous
- MCP tool: schedule_booking_slots_query
- Tags: schedule, booking, slots

### Schedule Calendar Connection Upsert

Create or update a calendar provider connection

- Operation key: `schedule.calendar.connection.upsert`
- Domain: schedule
- Metadata: Registry
- Goal: Persist provider connectivity for conflict-safe booking sync
- Context: Booking runtime provider connection management
- Stability: experimental
- Auth: user
- MCP tool: schedule_calendar_connection_upsert
- Tags: schedule, booking, calendar-provider

### Schedule Calendar Sync Pull

Pull external provider events into scheduling context

- Operation key: `schedule.calendar.sync.pull`
- Domain: schedule
- Metadata: Registry
- Goal: Refresh local booking conflict view from connected calendars
- Context: Calendar provider synchronization operation (inbound)
- Stability: experimental
- Auth: user
- MCP tool: schedule_calendar_sync_pull
- Tags: schedule, calendar-provider, sync, pull

### Schedule Calendar Sync Push

Push local booking updates to external calendar provider

- Operation key: `schedule.calendar.sync.push`
- Domain: schedule
- Metadata: Registry
- Goal: Keep provider calendar events consistent with booking lifecycle
- Context: Calendar provider synchronization operation (outbound)
- Stability: experimental
- Auth: user
- MCP tool: schedule_calendar_sync_push
- Tags: schedule, calendar-provider, sync, push

### Schedule Conflict Resolve

Resolve schedule conflicts using policy-aligned strategies

- Operation key: `schedule.conflict.resolve`
- Domain: schedule
- Metadata: Registry
- Goal: Keep capacity and booking plans conflict-aware under change
- Context: Calendar and booking stack rebuild phase 0
- Stability: experimental
- Auth: user
- MCP tool: schedule_conflict_resolve
- Tags: schedule, conflict, resolution

### Schedule Plan Apply

Apply a schedule plan after policy checks and approvals

- Operation key: `schedule.plan.apply`
- Domain: schedule
- Metadata: Registry
- Goal: Enforce draft-first scheduling writes with explicit trust controls
- Context: Calendar and booking stack rebuild phase 0
- Stability: experimental
- Auth: user
- MCP tool: schedule_plan_apply
- Tags: schedule, apply, policy-gate

### Schedule Plan Preview

Generate a policy-aware scheduling preview for action items

- Operation key: `schedule.plan.preview`
- Domain: schedule
- Metadata: Registry
- Goal: Provide draft-first schedule suggestions before any write action
- Context: Phase 0 foundation for schedule domain
- Stability: experimental
- Auth: user
- MCP tool: schedule_plan_preview
- Tags: schedule, planning, competition-killer

### Template Install

Not available

- Operation key: `template.install`
- Domain: template
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Template List

Not available

- Operation key: `template.list`
- Domain: template
- Metadata: Derived
- Goal: Not available
- Context: Not available
- Stability: Not available
- Auth: Not available
- MCP tool: Not available
- Tags: Not available

### Triad Churn Decomposition Get

Get churn decomposition (paid vs inactivity) for root-cause analysis

- Operation key: `triad.churn-decomposition.get`
- Domain: triad
- Metadata: Registry
- Goal: Split headline churn into paid and inactivity components
- Context: Triad metrics domain. Per canonical metric contract, headline churn must always be split.
- Stability: experimental
- Auth: user
- MCP tool: triad_churn-decomposition_get
- Tags: triad, churn, metrics

### Triad Feature Activation Rate

Query activation rate by module, checkpoint, and segment

- Operation key: `triad.feature-activation-rate`
- Domain: triad
- Metadata: Registry
- Goal: Measure first-value activation per module with canonical denominators
- Context: Triad metrics domain. Weighted-mean rollup across enabled modules.
- Stability: experimental
- Auth: user
- MCP tool: triad_feature-activation-rate
- Tags: triad, activation, metrics

### Triad Metrics Get

Get current triad state (signup, active_user, feature_activation_rate, churn) at a checkpoint

- Operation key: `triad.metrics.get`
- Domain: triad
- Metadata: Registry
- Goal: Power the triad bar and AI agent metric consumption
- Context: Triad metrics domain. Returns 4 metrics with trend arrows and freshness metadata.
- Stability: experimental
- Auth: user
- MCP tool: triad_metrics_get
- Tags: triad, metrics, bar

### Triad Next Action

Get ranked next actions across all domains for a metric at a checkpoint

- Operation key: `triad.next-action`
- Domain: triad
- Metadata: Registry
- Goal: Power autonomous loop and AI cockpit suggestions
- Context: Unified product experience. Aggregates PM, schedule, meeting-intelligence, knowledge next-action services.
- Stability: experimental
- Auth: user
- MCP tool: triad_next-action
- Tags: triad, next-action, autonomous

### Triad Suggestions Get

Get triad-drift-driven action suggestions for a workspace

- Operation key: `triad.suggestions.get`
- Domain: triad
- Metadata: Registry
- Goal: Surface evidence-backed next actions based on metric drift
- Context: AI Cockpit and sidebar suggestions. Requires current triad snapshot.
- Stability: experimental
- Auth: user
- MCP tool: triad_suggestions_get
- Tags: triad, suggestions, cockpit

### Vcs Branches Create

Creates a branch from an existing ref using connector-scoped repository access

- Operation key: `vcs.branches.create`
- Domain: vcs
- Metadata: Registry
- Goal: Provide a first-class governed branch creation command for agent and operator Git workflows
- Context: VCS domain. Creates a branch before commits, PRs, or managed delivery handoffs.
- Stability: experimental
- Auth: user
- MCP tool: vcs_branches_create
- Tags: vcs, branches, git

### Vcs Branches List

Lists branches in a repository with protection and default status

- Operation key: `vcs.branches.list`
- Domain: vcs
- Metadata: Registry
- Goal: Provide branch context for comparing refs and creating PR branches
- Context: VCS domain. Returns lightweight branch metadata.
- Stability: experimental
- Auth: user
- MCP tool: vcs_branches_list
- Tags: vcs, branches

### Vcs Deployments List

Lists synced deployments for a repository

- Operation key: `vcs.deployments.list`
- Domain: vcs
- Metadata: Registry
- Goal: Expose normalized deployment state and environment health without live provider fetches
- Context: VCS domain. Reads persisted vcs_deployment records from the Git substrate.
- Stability: experimental
- Auth: user
- MCP tool: vcs_deployments_list
- Tags: vcs, deployment, delivery

### Vcs File Create Or Update

Creates a new file or updates an existing file in a repo

- Operation key: `vcs.file.create-or-update`
- Domain: vcs
- Metadata: Registry
- Goal: Submit code edits via the GitHub API for automated changes
- Context: VCS domain. Used for creating branches with edits, updating files in PRs.
- Stability: experimental
- Auth: user
- MCP tool: vcs_file_create-or-update
- Tags: vcs, file, edit

### Vcs Issue Create

Creates a GitHub issue with title, body, labels, and assignees

- Operation key: `vcs.issue.create`
- Domain: vcs
- Metadata: Registry
- Goal: Export findings, impact items, or tasks as trackable GitHub issues
- Context: VCS domain. Issues can originate from impact analysis, task packs, or manual creation. Part of the export pipeline.
- Stability: experimental
- Auth: user
- MCP tool: vcs_issue_create
- Tags: vcs, issue, export

### Vcs Issue List

Lists issues from a repository with filters for state, labels, and assignees

- Operation key: `vcs.issue.list`
- Domain: vcs
- Metadata: Registry
- Goal: Ingest issue data as feedback and provide visibility into open work
- Context: VCS domain. Supports filtering and pagination. Issues become feedback items for pattern detection.
- Stability: experimental
- Auth: user
- MCP tool: vcs_issue_list
- Tags: vcs, issue, feedback

### Vcs Managed Delivery Execute

Creates or resumes a managed branch, applies file changes, commits them, opens or updates a PR, and optionally requests auto-merge

- Operation key: `vcs.managed-delivery.execute`
- Domain: vcs
- Metadata: Registry
- Goal: Give agents one governed Git delivery operation instead of separate branch, file, PR, and merge calls
- Context: VCS domain. GitHub-first orchestration over managed agent branches with workspace policy gates.
- Stability: experimental
- Auth: user
- MCP tool: vcs_managed-delivery_execute
- Tags: vcs, managed-delivery, autopilot, git

### Vcs Pr Create

Creates a pull request from a task pack with impact report summary and task checklist

- Operation key: `vcs.pr.create`
- Domain: vcs
- Metadata: Registry
- Goal: Export structured change proposals as reviewable GitHub PRs for engineering handoff
- Context: VCS domain. Creates a branch and PR body from the task pack impact analysis. Part of the export pipeline.
- Stability: experimental
- Auth: user
- MCP tool: vcs_pr_create
- Tags: vcs, pr, export

### Vcs Pr Diff

Retrieves file-level diffs for a pull request to feed impact analysis

- Operation key: `vcs.pr.diff`
- Domain: vcs
- Metadata: Registry
- Goal: Provide real code diffs for the git-diff-analyzer to improve what-breaks accuracy
- Context: VCS domain. Returns per-file additions, deletions, and optional patch content.
- Stability: experimental
- Auth: user
- MCP tool: vcs_pr_diff
- Tags: vcs, pr, diff, impact

### Vcs Pr Get

Retrieves detailed pull request information including diff stats and review status

- Operation key: `vcs.pr.get`
- Domain: vcs
- Metadata: Registry
- Goal: Enable deep inspection of individual PRs for feedback or export verification
- Context: VCS domain. Returns full PR metadata including body, diff stats, and labels.
- Stability: experimental
- Auth: user
- MCP tool: vcs_pr_get
- Tags: vcs, pr

### Vcs Pr List

Lists pull requests from a repository with filters for state, author, and branch

- Operation key: `vcs.pr.list`
- Domain: vcs
- Metadata: Registry
- Goal: Ingest PR data as feedback and provide visibility into active work
- Context: VCS domain. Supports filtering and pagination. PRs become feedback items for pattern detection.
- Stability: experimental
- Auth: user
- MCP tool: vcs_pr_list
- Tags: vcs, pr, feedback

### Vcs Pr Merge

Merges an open pull request using the specified merge strategy

- Operation key: `vcs.pr.merge`
- Domain: vcs
- Metadata: Registry
- Goal: Enable automated merge of reviewed PRs after checks pass
- Context: VCS domain. Supports merge, squash, and rebase strategies. Part of the change lifecycle pipeline.
- Stability: experimental
- Auth: user
- MCP tool: vcs_pr_merge
- Tags: vcs, pr, merge

### Vcs Pr Review Comment Create

Creates an inline review comment on a specific line of a PR

- Operation key: `vcs.pr.review-comment.create`
- Domain: vcs
- Metadata: Registry
- Goal: Post line-specific feedback during code review
- Context: VCS domain. Inline comments appear on the PR diff at the specified line.
- Stability: experimental
- Auth: user
- MCP tool: vcs_pr_review-comment_create
- Tags: vcs, pr, review, comment

### Vcs Pr Review Create

Creates a PR review (approve, request changes, or comment only)

- Operation key: `vcs.pr.review.create`
- Domain: vcs
- Metadata: Registry
- Goal: Submit review feedback on pull requests for code review workflows
- Context: VCS domain. Used for approving PRs, requesting changes, or adding general comments.
- Stability: experimental
- Auth: user
- MCP tool: vcs_pr_review_create
- Tags: vcs, pr, review

### Vcs Pr Update

Updates an existing pull request (title, body, state, labels, assignees)

- Operation key: `vcs.pr.update`
- Domain: vcs
- Metadata: Registry
- Goal: Allow lifecycle management of exported PRs as impact analysis evolves
- Context: VCS domain. Supports partial updates. Used to update PR descriptions with new impact data or close stale PRs.
- Stability: experimental
- Auth: user
- MCP tool: vcs_pr_update
- Tags: vcs, pr

### Vcs Releases List

Lists synced releases for a repository

- Operation key: `vcs.releases.list`
- Domain: vcs
- Metadata: Registry
- Goal: Expose normalized release history so AI and UI surfaces can reason on delivery state from synced data
- Context: VCS domain. Reads persisted vcs_release records rather than live provider release endpoints.
- Stability: experimental
- Auth: user
- MCP tool: vcs_releases_list
- Tags: vcs, release, delivery

### Vcs Repo Context Get

Returns synced repository context including freshness, recent commits, active PRs, linked issues, delivery state, and indexed refs

- Operation key: `vcs.repo-context.get`
- Domain: vcs
- Metadata: Registry
- Goal: Provide one normalized git context surface for chat, UI, MCP, and autonomous workflows
- Context: Uses normalized integration-data storage and git knowledge index metadata rather than live provider reads.
- Stability: experimental
- Auth: user
- MCP tool: vcs_repo-context_get
- Tags: vcs, repo, context, integration-data

### Vcs Workflow Runs List

Lists synced workflow runs for a repository

- Operation key: `vcs.workflow-runs.list`
- Domain: vcs
- Metadata: Registry
- Goal: Expose normalized CI delivery state for chat, MCP, UI, and autonomous workflows
- Context: VCS domain. Reads persisted vcs_workflow_run records instead of live provider state.
- Stability: experimental
- Auth: user
- MCP tool: vcs_workflow-runs_list
- Tags: vcs, workflow, ci, delivery

### Workspace Dataview Archive

Archive a workspace dataview (soft delete)

- Operation key: `workspace.dataview.archive`
- Domain: workspace
- Metadata: Registry
- Goal: Enable reversible dataview cleanup
- Context: Workspace personalization write operation for authored dataviews.
- Stability: experimental
- Auth: user
- MCP tool: workspace_dataview_archive
- Tags: workspace, dataview, archive

### Workspace Dataview Create

Create a workspace dataview

- Operation key: `workspace.dataview.create`
- Domain: workspace
- Metadata: Registry
- Goal: Enable reusable custom filtered views for workspace entities
- Context: Workspace personalization write operation for dataview creation.
- Stability: experimental
- Auth: user
- MCP tool: workspace_dataview_create
- Tags: workspace, dataview, create

### Workspace Dataview Get

Get a single workspace dataview by id

- Operation key: `workspace.dataview.get`
- Domain: workspace
- Metadata: Registry
- Goal: Support dataview resolution for page composition
- Context: Workspace personalization. Returns dataview definition with query spec and view config.
- Stability: experimental
- Auth: user
- MCP tool: workspace_dataview_get
- Tags: workspace, dataview, get

### Workspace Dataview List

List workspace dataviews for a workspace

- Operation key: `workspace.dataview.list`
- Domain: workspace
- Metadata: Registry
- Goal: Support dataview discovery and page composition
- Context: Workspace personalization. Returns dataviews available for the current user.
- Stability: experimental
- Auth: user
- MCP tool: workspace_dataview_list
- Tags: workspace, dataview, list

### Workspace Dataview Preview

Execute preview query for a dataview with safe limits

- Operation key: `workspace.dataview.preview`
- Domain: workspace
- Metadata: Registry
- Goal: Support dataview preview in builder and page composition
- Context: Workspace personalization. Returns limited rows for preview; full execution is page-bound.
- Stability: experimental
- Auth: user
- MCP tool: workspace_dataview_preview
- Tags: workspace, dataview, preview

### Workspace Dataview Restore

Restore an archived workspace dataview

- Operation key: `workspace.dataview.restore`
- Domain: workspace
- Metadata: Registry
- Goal: Enable undo of accidental dataview archival
- Context: Workspace personalization write operation for soft-deleted dataviews.
- Stability: experimental
- Auth: user
- MCP tool: workspace_dataview_restore
- Tags: workspace, dataview, restore

### Workspace Dataview Update

Update a workspace dataview

- Operation key: `workspace.dataview.update`
- Domain: workspace
- Metadata: Registry
- Goal: Support iterative editing of query and rendering configuration
- Context: Workspace personalization write operation with optimistic concurrency support.
- Stability: experimental
- Auth: user
- MCP tool: workspace_dataview_update
- Tags: workspace, dataview, update

### Workspace Page Archive

Archive a workspace page (soft delete)

- Operation key: `workspace.page.archive`
- Domain: workspace
- Metadata: Registry
- Goal: Enable reversible page deletion for safe workspace cleanup
- Context: Workspace personalization write operation; archives authored pages.
- Stability: experimental
- Auth: user
- MCP tool: workspace_page_archive
- Tags: workspace, page, archive

### Workspace Page Create

Create a workspace page

- Operation key: `workspace.page.create`
- Domain: workspace
- Metadata: Registry
- Goal: Enable teams to define custom pages and dashboards
- Context: Workspace personalization write operation for authored workspace pages.
- Stability: experimental
- Auth: user
- MCP tool: workspace_page_create
- Tags: workspace, page, create

### Workspace Page Get

Get a single workspace page by id or slug

- Operation key: `workspace.page.get`
- Domain: workspace
- Metadata: Registry
- Goal: Support page resolution for dynamic routes
- Context: Workspace personalization. Returns page definition with layout and widget bindings.
- Stability: experimental
- Auth: user
- MCP tool: workspace_page_get
- Tags: workspace, page, get

### Workspace Page List

List workspace pages for a workspace

- Operation key: `workspace.page.list`
- Domain: workspace
- Metadata: Registry
- Goal: Support nav composition and page discovery
- Context: Workspace personalization. Returns pages available for the current user.
- Stability: experimental
- Auth: user
- MCP tool: workspace_page_list
- Tags: workspace, page, list

### Workspace Page Restore

Restore an archived workspace page

- Operation key: `workspace.page.restore`
- Domain: workspace
- Metadata: Registry
- Goal: Enable undo of accidental page archival
- Context: Workspace personalization write operation for soft-deleted pages.
- Stability: experimental
- Auth: user
- MCP tool: workspace_page_restore
- Tags: workspace, page, restore

### Workspace Page Update

Update a workspace page

- Operation key: `workspace.page.update`
- Domain: workspace
- Metadata: Registry
- Goal: Allow iterative editing of workspace page metadata and layout
- Context: Workspace personalization write operation with optimistic concurrency support.
- Stability: experimental
- Auth: user
- MCP tool: workspace_page_update
- Tags: workspace, page, update

### Workspace Personalization Get

Get effective workspace personalization state for a scope

- Operation key: `workspace.personalization.get`
- Domain: workspace
- Metadata: Registry
- Goal: Read workspace or per-user personalization overlays
- Context: Workspace personalization. Used by resolver/UI to load ordering, pinning, and defaults.
- Stability: experimental
- Auth: user
- MCP tool: workspace_personalization_get
- Tags: workspace, personalization, get

### Workspace Personalization Reset

Reset workspace personalization state for a scope

- Operation key: `workspace.personalization.reset`
- Domain: workspace
- Metadata: Registry
- Goal: Allow quick recovery to default workspace or user overlay state
- Context: Workspace personalization. Used to clear user/workspace overrides safely.
- Stability: experimental
- Auth: user
- MCP tool: workspace_personalization_reset
- Tags: workspace, personalization, reset

### Workspace Personalization Set

Create or update workspace personalization state for a scope

- Operation key: `workspace.personalization.set`
- Domain: workspace
- Metadata: Registry
- Goal: Persist workspace or user overlays for personalized navigation and pages
- Context: Workspace personalization. Supports W2 overlays (workspace + user).
- Stability: experimental
- Auth: user
- MCP tool: workspace_personalization_set
- Tags: workspace, personalization, set

### Workspace Template Archive

Archive a workspace template

- Operation key: `workspace.template.archive`
- Domain: workspace
- Metadata: Registry
- Goal: Remove outdated templates from active distribution
- Context: Workspace builder and template lifecycle
- Stability: experimental
- Auth: user
- MCP tool: workspace_template_archive
- Tags: workspace, template, archive

### Workspace Template Create

Create a workspace template draft

- Operation key: `workspace.template.create`
- Domain: workspace
- Metadata: Registry
- Goal: Start a reusable workspace distribution artifact
- Context: Workspace builder and template lifecycle
- Stability: experimental
- Auth: user
- MCP tool: workspace_template_create
- Tags: workspace, template, create

### Workspace Template Get

Get workspace template metadata and latest release

- Operation key: `workspace.template.get`
- Domain: workspace
- Metadata: Registry
- Goal: Support template discovery and install flow
- Context: Workspace personalization. Returns template metadata; install uses release ID.
- Stability: experimental
- Auth: user
- MCP tool: workspace_template_get
- Tags: workspace, template, get

### Workspace Template Install

Install a workspace template release into a workspace

- Operation key: `workspace.template.install`
- Domain: workspace
- Metadata: Registry
- Goal: Apply reusable PM dashboards and workspace layouts
- Context: Workspace builder and template lifecycle
- Stability: experimental
- Auth: user
- MCP tool: workspace_template_install
- Tags: workspace, template, install

### Workspace Template List

List workspace templates by scope and category

- Operation key: `workspace.template.list`
- Domain: workspace
- Metadata: Registry
- Goal: Support template gallery and install flow
- Context: Workspace personalization. Returns templates available for installation.
- Stability: experimental
- Auth: user
- MCP tool: workspace_template_list
- Tags: workspace, template, list

### Workspace Template Release

Publish a new release for a workspace template

- Operation key: `workspace.template.release`
- Domain: workspace
- Metadata: Registry
- Goal: Snapshot workspace artifacts for installable distribution
- Context: Workspace builder and template lifecycle
- Stability: experimental
- Auth: user
- MCP tool: workspace_template_release
- Tags: workspace, template, release

### Workspace Template Rollback

Rollback a workspace template install

- Operation key: `workspace.template.rollback`
- Domain: workspace
- Metadata: Registry
- Goal: Revert installed workspace artifacts deterministically
- Context: Workspace builder and template lifecycle
- Stability: experimental
- Auth: user
- MCP tool: workspace_template_rollback
- Tags: workspace, template, rollback

### Workspace Template Share

Share a workspace template by updating its scope

- Operation key: `workspace.template.share`
- Domain: workspace
- Metadata: Registry
- Goal: Distribute templates beyond a single workspace when approved
- Context: Workspace builder and template lifecycle
- Stability: experimental
- Auth: user
- MCP tool: workspace_template_share
- Tags: workspace, template, share

### Workspace Template Update

Update workspace template metadata

- Operation key: `workspace.template.update`
- Domain: workspace
- Metadata: Registry
- Goal: Keep template drafts and published templates accurate
- Context: Workspace builder and template lifecycle
- Stability: experimental
- Auth: user
- MCP tool: workspace_template_update
- Tags: workspace, template, update

## Technical appendix

### Source files

| Operation key | Metadata | Source files |
| --- | --- | --- |
| agency-kit.diff-sources | Registry | packages/apps/mcp-server/src/index.ts |
| agency-kit.export-drift-items | Registry | packages/apps/mcp-server/src/index.ts |
| agency-kit.get-deliverable | Registry | packages/apps/mcp-server/src/index.ts |
| agency-kit.get-drift-register | Registry | packages/apps/mcp-server/src/index.ts |
| agency-kit.list-companies | Registry | packages/apps/mcp-server/src/index.ts |
| agency-kit.share-deliverable | Registry | packages/apps/mcp-server/src/index.ts |
| agent-orchestration.packet.assign | Registry | packages/apps/mcp-server/src/index.ts |
| agent-orchestration.packet.plan | Registry | packages/apps/mcp-server/src/index.ts |
| agent-orchestration.packet.verify | Registry | packages/apps/mcp-server/src/index.ts |
| agent-orchestration.squad-run.control | Registry | packages/apps/mcp-server/src/index.ts |
| agent-orchestration.squad-run.start | Registry | packages/apps/mcp-server/src/index.ts |
| autopilot.disable | Registry | packages/apps/mcp-server/src/index.ts |
| autopilot.dismiss-run | Registry | packages/apps/mcp-server/src/index.ts |
| autopilot.enable | Registry | packages/apps/mcp-server/src/index.ts |
| autopilot.get-config | Registry | packages/apps/mcp-server/src/index.ts |
| autopilot.get-run | Registry | packages/apps/mcp-server/src/index.ts |
| autopilot.list-runs | Registry | packages/apps/mcp-server/src/index.ts |
| autopilot.review-certify | Registry | packages/apps/mcp-server/src/index.ts |
| autopilot.trigger-run | Registry | packages/apps/mcp-server/src/index.ts |
| autopilot.update-policy | Registry | packages/apps/mcp-server/src/index.ts |
| autopilot.update-schedule | Registry | packages/apps/mcp-server/src/index.ts |
| brief.delete | Registry | packages/apps/mcp-server/src/index.ts |
| brief.generate | Registry | packages/apps/mcp-server/src/index.ts |
| brief.get | Registry | packages/apps/mcp-server/src/index.ts |
| brief.list | Registry | packages/apps/mcp-server/src/index.ts |
| brief.update | Registry | packages/apps/mcp-server/src/index.ts |
| change.check.get | Registry | packages/apps/mcp-server/src/index.ts |
| change.check.list | Registry | packages/apps/mcp-server/src/index.ts |
| change.handoff-pack.generate | Registry | packages/apps/mcp-server/src/index.ts |
| change.handoff-pack.share-slack | Registry | packages/apps/mcp-server/src/index.ts |
| change.handoff-pack.verify | Registry | packages/apps/mcp-server/src/index.ts |
| change.list | Registry | packages/apps/mcp-server/src/index.ts |
| change.remediation-pack.deliver | Registry | packages/apps/mcp-server/src/index.ts |
| change.remediation-pack.generate | Registry | packages/apps/mcp-server/src/index.ts |
| change.remediation-pack.verify | Registry | packages/apps/mcp-server/src/index.ts |
| change.remediation-session.get | Registry | packages/apps/mcp-server/src/index.ts |
| check.delete | Registry | packages/apps/mcp-server/src/index.ts |
| check.update | Registry | packages/apps/mcp-server/src/index.ts |
| connector.attio.activity.search | Registry | packages/apps/mcp-server/src/index.ts |
| connector.attio.attributes.list | Registry | packages/apps/mcp-server/src/index.ts |
| connector.attio.record.get | Registry | packages/apps/mcp-server/src/index.ts |
| connector.attio.search | Registry | packages/apps/mcp-server/src/index.ts |
| connector.attio.write | Registry | packages/apps/mcp-server/src/index.ts |
| connector.notion.context.query | Registry | packages/apps/mcp-server/src/index.ts |
| connector.notion.hydrate | Registry | packages/apps/mcp-server/src/index.ts |
| connector.notion.item.get | Registry | packages/apps/mcp-server/src/index.ts |
| connector.notion.item.override | Registry | packages/apps/mcp-server/src/index.ts |
| connector.notion.items.list | Registry | packages/apps/mcp-server/src/index.ts |
| connector.notion.search | Registry | packages/apps/mcp-server/src/index.ts |
| connector.notion.sources.configure | Registry | packages/apps/mcp-server/src/index.ts |
| connector.notion.sources.list | Registry | packages/apps/mcp-server/src/index.ts |
| connector.notion.write | Registry | packages/apps/mcp-server/src/index.ts |
| connector.notion.write.plan | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.asset-lineage-get | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.brief-create | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.calendar-get | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.canonical-generate | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.learning-capture | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.packet-advance | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.packet-create | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.packet-get | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.packet-list | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.publish-mark | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.qa-verify | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.rewrite-run | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.schedule-set | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.scoreboard-compute | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.scoreboard-weekly-get | Registry | packages/apps/mcp-server/src/index.ts |
| content-ops.slice-generate | Registry | packages/apps/mcp-server/src/index.ts |
| contractspec.codebase.analyze | Registry | packages/apps/mcp-server/src/index.ts |
| contractspec.contract.read | Registry | packages/apps/mcp-server/src/index.ts |
| contractspec.contracts.list | Registry | packages/apps/mcp-server/src/index.ts |
| contractspec.spec.evolve | Registry | packages/apps/mcp-server/src/index.ts |
| correlation.run | Registry | packages/apps/mcp-server/src/index.ts |
| engineering.context-bundle.get | Registry | packages/apps/mcp-server/src/index.ts |
| engineering.incident-bundle.get | Registry | packages/apps/mcp-server/src/index.ts |
| engineering.incident-feed.list | Registry | packages/apps/mcp-server/src/index.ts |
| engineering.traceability.get | Registry | packages/apps/mcp-server/src/index.ts |
| feedback.delete-item | Registry | packages/apps/mcp-server/src/index.ts |
| feedback.delete-items | Registry | packages/apps/mcp-server/src/index.ts |
| feedback.get-item | Registry | packages/apps/mcp-server/src/index.ts |
| feedback.ingest | Registry | packages/apps/mcp-server/src/index.ts |
| feedback.list-items | Registry | packages/apps/mcp-server/src/index.ts |
| feedback.search | Registry | packages/apps/mcp-server/src/index.ts |
| feedback.update-item | Registry | packages/apps/mcp-server/src/index.ts |
| focus.create | Registry | packages/apps/mcp-server/src/index.ts |
| focus.delete | Registry | packages/apps/mcp-server/src/index.ts |
| focus.get | Registry | packages/apps/mcp-server/src/index.ts |
| focus.list | Registry | packages/apps/mcp-server/src/index.ts |
| focus.update | Registry | packages/apps/mcp-server/src/index.ts |
| governance.approval.request | Registry | packages/apps/mcp-server/src/index.ts |
| governance.approval.respond | Registry | packages/apps/mcp-server/src/index.ts |
| governance.audit-pack.get | Registry | packages/apps/mcp-server/src/index.ts |
| governance.evidence-graph.get | Registry | packages/apps/mcp-server/src/index.ts |
| governance.evidence-publication.get | Registry | packages/apps/mcp-server/src/index.ts |
| governance.policy.get | Registry | packages/apps/mcp-server/src/index.ts |
| governance.policy.set | Registry | packages/apps/mcp-server/src/index.ts |
| governance.policy.simulate | Registry | packages/apps/mcp-server/src/index.ts |
| governance.risk-assessment.evaluate | Registry | packages/apps/mcp-server/src/index.ts |
| governance.schedule-policy.apply.set | Registry | packages/apps/mcp-server/src/index.ts |
| governance.schedule-policy.draft.get | Registry | packages/apps/mcp-server/src/index.ts |
| governance.sla.get | Registry | packages/apps/mcp-server/src/index.ts |
| graph.daily-note.get | Registry | packages/apps/mcp-server/src/index.ts |
| graph.node.archive | Registry | packages/apps/mcp-server/src/index.ts |
| graph.node.create | Registry | packages/apps/mcp-server/src/index.ts |
| graph.node.get | Registry | packages/apps/mcp-server/src/index.ts |
| graph.node.list | Registry | packages/apps/mcp-server/src/index.ts |
| graph.node.move | Registry | packages/apps/mcp-server/src/index.ts |
| graph.node.reference.create | Registry | packages/apps/mcp-server/src/index.ts |
| graph.node.update | Registry | packages/apps/mcp-server/src/index.ts |
| graph.search.execute | Registry | packages/apps/mcp-server/src/index.ts |
| graph.search.list | Registry | packages/apps/mcp-server/src/index.ts |
| graph.supertag.apply | Registry | packages/apps/mcp-server/src/index.ts |
| graph.supertag.define | Registry | packages/apps/mcp-server/src/index.ts |
| graph.supertag.get | Registry | packages/apps/mcp-server/src/index.ts |
| graph.supertag.list | Registry | packages/apps/mcp-server/src/index.ts |
| growth-operator.drift-summary | Registry | packages/apps/mcp-server/src/index.ts |
| growth-operator.interventions-list | Registry | packages/apps/mcp-server/src/index.ts |
| growth-operator.outcome-history | Registry | packages/apps/mcp-server/src/index.ts |
| growth-operator.pause | Registry | packages/apps/mcp-server/src/index.ts |
| integration-data.analytics-events.list | Registry | packages/apps/mcp-server/src/index.ts |
| integration-data.calendar-events.list | Registry | packages/apps/mcp-server/src/index.ts |
| integration-data.feed.list | Registry | packages/apps/mcp-server/src/index.ts |
| integration-data.health.get | Registry | packages/apps/mcp-server/src/index.ts |
| integration-data.messages.list | Registry | packages/apps/mcp-server/src/index.ts |
| integration-data.record.get | Registry | packages/apps/mcp-server/src/index.ts |
| integration-data.slack-threads.list | Registry | packages/apps/mcp-server/src/index.ts |
| integration-data.social-posts.list | Registry | packages/apps/mcp-server/src/index.ts |
| integration-data.summary.get | Registry | packages/apps/mcp-server/src/index.ts |
| integration-data.vcs-commits.list | Registry | packages/apps/mcp-server/src/index.ts |
| integration-data.vcs-issues.list | Registry | packages/apps/mcp-server/src/index.ts |
| integration-data.vcs-pull-requests.list | Registry | packages/apps/mcp-server/src/index.ts |
| loop.evidence.get | Registry | packages/apps/mcp-server/src/index.ts |
| loop.metrics.get | Registry | packages/apps/mcp-server/src/index.ts |
| loop.run.cancel | Registry | packages/apps/mcp-server/src/index.ts |
| loop.run.checkpoints.get | Registry | packages/apps/mcp-server/src/index.ts |
| loop.run.get | Registry | packages/apps/mcp-server/src/index.ts |
| loop.run.replay_from_checkpoint | Registry | packages/apps/mcp-server/src/index.ts |
| loop.run.replay_preview.get | Registry | packages/apps/mcp-server/src/index.ts |
| loop.run.start | Registry | packages/apps/mcp-server/src/index.ts |
| loop.run.wait.resume | Registry | packages/apps/mcp-server/src/index.ts |
| loop.step.patch | Registry | packages/apps/mcp-server/src/index.ts |
| meeting.decision.extract | Registry | packages/apps/mcp-server/src/index.ts |
| meeting-execution.followthrough-draft.preview | Registry | packages/apps/mcp-server/src/index.ts |
| meeting-execution.outcome-update | Registry | packages/apps/mcp-server/src/index.ts |
| meeting-execution.pilot-scorecard.get | Registry | packages/apps/mcp-server/src/index.ts |
| meeting-execution.review-approve | Registry | packages/apps/mcp-server/src/index.ts |
| meeting-execution.review-edit | Registry | packages/apps/mcp-server/src/index.ts |
| meeting-execution.review-item.get | Registry | packages/apps/mcp-server/src/index.ts |
| meeting-execution.review-queue.list | Registry | packages/apps/mcp-server/src/index.ts |
| meeting-execution.review-reject | Registry | packages/apps/mcp-server/src/index.ts |
| meeting-execution.sync-apply | Registry | packages/apps/mcp-server/src/index.ts |
| meeting-execution.sync-preview | Registry | packages/apps/mcp-server/src/index.ts |
| meeting.history.list | Registry | packages/apps/mcp-server/src/index.ts |
| meeting-intelligence.meeting.list | Registry | packages/apps/mcp-server/src/index.ts |
| meeting.provider.ingest | Registry | packages/apps/mcp-server/src/index.ts |
| meeting.recording.ingest | Registry | packages/apps/mcp-server/src/index.ts |
| meeting.search | Registry | packages/apps/mcp-server/src/index.ts |
| meeting.signal.quality.score | Registry | packages/apps/mcp-server/src/index.ts |
| meeting.summary.normalize | Registry | packages/apps/mcp-server/src/index.ts |
| meeting.transcript.generate | Registry | packages/apps/mcp-server/src/index.ts |
| patch.delete | Registry | packages/apps/mcp-server/src/index.ts |
| patch.get | Registry | packages/apps/mcp-server/src/index.ts |
| patch.update | Registry | packages/apps/mcp-server/src/index.ts |
| pattern.delete | Registry | packages/apps/mcp-server/src/index.ts |
| pattern.get | Registry | packages/apps/mcp-server/src/index.ts |
| pattern.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.actionitem.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.attachment.create | Registry | packages/apps/mcp-server/src/index.ts |
| pm.attachment.delete | Registry | packages/apps/mcp-server/src/index.ts |
| pm.attachment.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.board-config.get | Registry | packages/apps/mcp-server/src/index.ts |
| pm.board-config.set | Registry | packages/apps/mcp-server/src/index.ts |
| pm.cycle.commit | Registry | packages/apps/mcp-server/src/index.ts |
| pm.cycle.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.cycle.plan | Registry | packages/apps/mcp-server/src/index.ts |
| pm.cycle.review | Registry | packages/apps/mcp-server/src/index.ts |
| pm.dependency.detect | Registry | packages/apps/mcp-server/src/index.ts |
| pm.dependency.resolve | Registry | packages/apps/mcp-server/src/index.ts |
| pm.feedback.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.focus.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.issue.auto-enrich | Registry | packages/apps/mcp-server/src/index.ts |
| pm.issue.close | Registry | packages/apps/mcp-server/src/index.ts |
| pm.issue.create | Registry | packages/apps/mcp-server/src/index.ts |
| pm.issue.link.create | Registry | packages/apps/mcp-server/src/index.ts |
| pm.issue.link.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.issue.link.remove | Registry | packages/apps/mcp-server/src/index.ts |
| pm.issue.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.issue.update | Registry | packages/apps/mcp-server/src/index.ts |
| pm.notification.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.notification.read | Registry | packages/apps/mcp-server/src/index.ts |
| pm.pattern.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.project.create | Registry | packages/apps/mcp-server/src/index.ts |
| pm.project.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.project.plan | Registry | packages/apps/mcp-server/src/index.ts |
| pm.project.rebaseline | Registry | packages/apps/mcp-server/src/index.ts |
| pm.release.create | Registry | packages/apps/mcp-server/src/index.ts |
| pm.release.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.release.update | Registry | packages/apps/mcp-server/src/index.ts |
| pm.view.list | Registry | packages/apps/mcp-server/src/index.ts |
| pm.workload.recommend | Registry | packages/apps/mcp-server/src/index.ts |
| rag.query-knowledge | Registry | packages/apps/mcp-server/src/index.ts |
| runtime.target.capability-check | Registry | packages/apps/mcp-server/src/index.ts |
| runtime.target.render | Registry | packages/apps/mcp-server/src/index.ts |
| runtime.ui-block.generate | Registry | packages/apps/mcp-server/src/index.ts |
| runtime.view-model.compile | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.availability.compute | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking.cancel | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking.create | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking.hold.create | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking.hold.release | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking-link.create | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking-link.disable | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking-link.route | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking-link.update | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking.list | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking.mark-no-show | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking-poll.cancel | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking-poll.create | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking-poll.finalize | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking-poll.list | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking-poll.public.get | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking-poll.vote | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking.reschedule | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.booking.slots.query | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.calendar.connection.upsert | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.calendar.sync.pull | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.calendar.sync.push | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.conflict.resolve | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.plan.apply | Registry | packages/apps/mcp-server/src/index.ts |
| schedule.plan.preview | Registry | packages/apps/mcp-server/src/index.ts |
| triad.churn-decomposition.get | Registry | packages/apps/mcp-server/src/index.ts |
| triad.feature-activation-rate | Registry | packages/apps/mcp-server/src/index.ts |
| triad.metrics.get | Registry | packages/apps/mcp-server/src/index.ts |
| triad.next-action | Registry | packages/apps/mcp-server/src/index.ts |
| triad.suggestions.get | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.branches.create | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.branches.list | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.deployments.list | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.file.create-or-update | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.issue.create | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.issue.list | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.managed-delivery.execute | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.pr.create | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.pr.diff | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.pr.get | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.pr.list | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.pr.merge | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.pr.review-comment.create | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.pr.review.create | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.pr.update | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.releases.list | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.repo-context.get | Registry | packages/apps/mcp-server/src/index.ts |
| vcs.workflow-runs.list | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.dataview.archive | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.dataview.create | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.dataview.get | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.dataview.list | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.dataview.preview | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.dataview.restore | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.dataview.update | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.page.archive | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.page.create | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.page.get | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.page.list | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.page.restore | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.page.update | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.personalization.get | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.personalization.reset | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.personalization.set | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.template.archive | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.template.create | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.template.get | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.template.install | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.template.list | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.template.release | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.template.rollback | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.template.share | Registry | packages/apps/mcp-server/src/index.ts |
| workspace.template.update | Registry | packages/apps/mcp-server/src/index.ts |

### MCP endpoints

| Path | Methods | Description | Source file |
| --- | --- | --- | --- |
| /api/mcp | POST, GET, DELETE | StreamableHTTP endpoint (Next.js web-application) | packages/apps/web-application/src/app/api/mcp/route.ts |
| / | POST, GET, DELETE | Primary StreamableHTTP endpoint (standalone mcp-server) | packages/apps/mcp-server/src/index.ts |
| /mcp | POST, GET, DELETE | Compatibility StreamableHTTP endpoint | packages/apps/mcp-server/src/index.ts |
| /sse | GET | Legacy SSE transport endpoint | packages/apps/mcp-server/src/index.ts |
| /messages | POST | Legacy SSE message endpoint | packages/apps/mcp-server/src/index.ts |
| /health | GET | Health probe endpoint | packages/apps/mcp-server/src/index.ts |
| /try | GET | Interactive docs/demo playground | packages/apps/mcp-server/src/index.ts |
| /assets/* | GET | Static widget assets | packages/apps/mcp-server/src/index.ts |

- Generated catalog file: /var/task/packages/apps/web-marketing/generated/docs/surface-catalog.json
- Generated manifest file: /var/task/packages/apps/mcp-server/src/generated/tool-catalog.json
- Generated from: runtime