Mercury MCP

Mercury MCP is the hosted Model Context Protocol server for Mercury, the banking platform used by startups and small companies. It runs as a remote endpoint that an assistant connects to after an OAuth sign in, so there is nothing to install locally and no long lived key sitting in a client config file. The server is deliberately read only. It exposes accounts and their balances, transaction history with per transaction detail, statements, cards, saved recipients and treasury accounts, which gives an agent enough context to answer questions about cash position and spending. Money movement is not part of it: initiating payments, paying bills and issuing invoices stay on Mercury's API and command line surface, where token scoping, permissions and IP controls apply. That split is the main design decision to understand before adopting it, because it caps the blast radius of a misfiring agent to disclosure rather than transfer. In practice it replaces exporting a CSV and loading it into a spreadsheet. A founder or finance operator asks what the balance is, how spend with a given vendor has moved over recent months, which transactions look unusual, or how runway is trending, and gets an answer computed against live account data. It pairs naturally with an assistant that can chart the result in the same reply.