Mercury-multiorg-mcp Server

Mercury-multiorg-mcp is an MCP integration. Unofficial read-only MCP server exposing several Mercury banking organizations to one AI session.

Packages and local setup

The published pypi package is mercury-multiorg-mcp, version 0.1.6. Its declared MCP transport is stdio.

The package declares MERCURY_TOKEN_ACME_MAIN: Example only. Each organization needs one read-only Mercury API token in the environment variable named by its token_env in your registry. Names are yours to choose but must match MERCURY_TOKEN_[A-Z0-9_]+ (for example MERCURY_TOKEN_ ); set one per organization and rename this example to match.; MERCURY_ENTITIES_FILE: Alternative to --entities: path to the entity registry YAML. Ignored when --entities is passed.; MERCURY_API_BASE: Mercury API host. Allowed without extra flags: https://api.mercury.com, https://api-sandbox.mercury.com (with sandbox tokens), or a loopback mock.; MERCURY_ALLOW_DOCUMENTS: Set to true to register get_statement_pdf and get_invoice_pdf, which return statement and invoice PDFs unredacted. Off by default..

This package has launch arguments in its registry record. Use the maintainer’s configuration for those arguments rather than launching it with only the package name.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.6 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.