@adrata/multiverse-mcp

Let Claude Code or Codex work in your Multiverse repos: make documents, spreadsheets, presentations and designs, change the ones you can change, comment, and bring back an older version. What they make shows up in Multiverse as they make it.

claude mcp add multiverse --scope user -- npx -y @adrata/multiverse-mcp
codex mcp add multiverse -- npx -y @adrata/multiverse-mcp

This is a thin product profile over @adrata/adrata-mcp, not a fork. It shares authentication, policy, audit logging, handlers and releases with the Adrata server. The Multiverse profile advertises only the Multiverse tools (named galaxy_*) and the workspace connection tools; CRM, email, calendar, boards and the broad Adrata API bridge are omitted from tools/list.

Every write uses the same documents, revisions and access checks as the app: product access and the caller's permission to each item are required, a write previews by default, and a live write carries approval, a reason and an idempotency key.

An agent never silently overwrites someone else's file. A change to a file that is not your own, or to any file in a repo whose policy says agents propose, becomes a decision: galaxy_propose_change sends the after with a title, a one-paragraph why and its sources, and a person approves, requests changes or rejects it in Multiverse › Decisions. galaxy_list_decisions and galaxy_get_decision read the queue and the verdict (with what to change, when changes were requested); answer a change request by proposing again with the decisionId. There is no tool that approves, and the API refuses a verdict from any agent credential.

Inside the client, run connect_workspace, then workspace_status. A process starting successfully proves only installation; workspace_status proves the credential.

Set ADRATA_MCP_ENABLED_DOMAINS only when an operator intentionally needs a custom pack list. An explicit value wins over the Multiverse default and is never widened by this wrapper.