Mercury Multiorg MCP

Mercury Multiorg MCP runs locally from a Python package published to PyPI: mercury-multiorg-mcp version 0.1.6. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install — the usual command is uvx mercury-multiorg-mcp. It reads these environment variables: MERCURY_TOKEN_ACME_MAIN (secret), MERCURY_ENTITIES_FILE, MERCURY_API_BASE and MERCURY_ALLOW_DOCUMENTS; set them in the client's configuration for this server. Required arguments: --entities.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mercury-multiorg-mcp": {
      "command": "uvx",
      "args": [
        "mercury-multiorg-mcp"
      ],
      "env": {
        "MERCURY_TOKEN_ACME_MAIN": "<secret>",
        "MERCURY_ENTITIES_FILE": "<value>",
        "MERCURY_API_BASE": "<value>",
        "MERCURY_ALLOW_DOCUMENTS": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect