Read your Mercury accounts, cards, statements, and invoices from the terminal
Ask about balances mid-incident or mid-close without opening the banking dashboard. Mercury MCP is Mercury's official server, in beta, and it is read-only: accounts, cards, statements, attachments, customers, and invoices come back as data, and mutations are blocked on Mercury's side. Luumen connects over DCR OAuth. Every call, including MERCURY_MCP_GET_ACCOUNTS, is classified as a write here, so expect an approval prompt by default; administrators can adjust that per tool.
30 tools: 0 read, 30 write. Reads answer instantly. Writes require approval by default. Everything is logged.
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as getaccount, getaccountcards, getaccounts, getaccountstatements, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Mercury MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.