Claude Code plugin

The metatate plugin for Claude Code packages governance workflows on top of your workspace's MCP server: eight slash commands plus a skill that teaches Claude the tool contract and answer model. The plugin supplies the workflows; the MCP connection itself is registered separately with an access token.

Install the plugin

In Claude Code:

/plugin marketplace add metatateai/metatate-claude-plugins
/plugin install metatate@metatate-claude-plugins

Restart Claude Code if prompted.

Register the MCP server

You need two values from your workspace's MCP module: the endpoint URL (Connect tab) and an access token (Tokens tab — admin or owner only, shown exactly once, revocable). See Connect an agent for details.

If you cloned the marketplace repository, use the bundled helper so the token never lands in shell history:

./plugins/metatate/bin/metatate-cloud-mcp-add \
  --url https://<workspace-mcp-host> \
  --config-scope user \
  --run

With --run, the helper reads the token from the METATATE_MCP_TOKEN environment variable, or prompts for it with input hidden, then registers the server as metatate. It accepts the base URL or the full endpoint and appends /mcp automatically. Without --run, it only prints a claude mcp add-json command containing a placeholder — a real token is never printed.

Without a clone, run the equivalent claude mcp add-json command shown on your workspace's Connect tab (and in Connect an agent), accepting the shell-history trade-off.

Commands

Command	What it does
/metatate:discover-context	Find governed assets and their canonical scenario keys by database or schema.
/metatate:inspect-data	Explain governed data meaning, classification, sensitivity, PII, and masking facts for a table or column.
/metatate:inspect-rules	Inspect active governance, usage, validation, and transfer rules for a governed asset.
/metatate:authorize-use	Ask whether a proposed data use is allowed, denied, conditional, or needs review.
/metatate:validate-query	Validate SQL or query context against active governance before execution or release.
/metatate:explain-decision	Explain a prior authorization decision from its decision_id.
/metatate:policy-review	Review governed policy coverage and likely gaps for an asset, query, workflow, or intended use.
/metatate:release-gate	Run an advisory governance review of a repository change before merge or release.

The plugin also ships the metatate-governance skill, which Claude invokes automatically when you ask about governed data context, data meaning, policy rules, data-use authorization, query validation, decision explanation, or release readiness — no slash command required. It keeps Claude honest about typed answer states: missing published state is relayed as-is, never guessed around.

Smoke test

Check the connection — /mcp should show metatate as connected immediately (there is no OAuth step). Then run:

/metatate:discover-context

Ask for governed assets, pick one, and test a decision workflow with /metatate:authorize-use ("Can we use <database>.<schema>.<table> for <your intended use>?"). Claude returns an advisory decision with rationale and a decision_id; feed that ID to /metatate:explain-decision to see the decision's evidence.

If your workspace has nothing published yet, load the AcmeCloud demo first — see the quick start.

To remove: claude mcp remove metatate, uninstall the plugin, and revoke the token in the Tokens tab — removing the local registration does not invalidate the token.