mono

This MCP server provides a Python-based integration for Nigerian banking operations via the Mono Open Banking API. It exposes 12 core banking tools (such as list_linked_accounts, get_account_balance, get_account_info, get_account_details, get_transaction_history, verify_account_name, initiate_payment, verify_payment, get_nigerian_banks, lookup_bvn, initiate_account_linking, and more) along with real-time webhook handling for events like account.connected and account.updated. The server is designed to run with FastMCP Cloud and includes webhook verification (HMAC-SHA256), event storage, and an HTTP webhook endpoint at /mono/webhook, plus a health check at /health. You can connect an AI assistant (such as Claude or Gemini) to the MCP server to issue natural language commands like listing accounts, checking balances, initiating payments, or verifying recipients, with the assistant translating those requests into the corresponding MCP tool calls.

Prerequisites:

• Python 3.12+ installed on your system
• Access to a Python package manager (pip)
• Optional: uv (Fast Python package manager) if you prefer uv-based execution

Installation steps (via uvx, recommended):

1. Install the MCP package from PyPI (or your preferred source):

   • uvx mono-banking-mcp
   • If you are installing directly from source, clone the repo and install dependencies: git clone https://github.com/your-org/mono-banking-mcp.git cd mono-banking-mcp python -m pip install -e .

2. Configure environment variables (examples):

   • MONO_API_BASE_URL=https://mono.co
   • WEBHOOK_SECRET=your-webhook-secret
   • DATABASE_URL=sqlite:///webhooks.db
   • HMAC_SECRET=your-hmac-secret

3. Run the server:

   • uvx mono-banking-mcp
   • Or if running directly from source: python -m mono_banking_mcp.server

4. Verify the server is up by hitting the health endpoint:

   • https://your-host/health

5. Optional: connect with an AI assistant (Claude, Gemini, etc.) by pointing it to the MCP URL:

   • https://your-host/mcp

Tips and common issues:

• Ensure your WEBHOOK_SECRET and HMAC_SECRET are securely stored and never exposed in logs or code.
• The /mono/webhook endpoint validates incoming requests using HMAC-SHA256; restart the server if you rotate secrets.
• The DATABASE_URL should point to a persistent database in production; SQLite works for development but consider PostgreSQL/MySQL for production.
• If you plan to deploy on FastMCP Cloud, you can use the provided configuration snippet to autostart with the cloud environment.
• The 12 tools and webhook features assume access to Mono Open Banking API v2 endpoints; ensure your API keys and sandbox credentials are correctly configured.
• For debugging, examine webhook events in the database and use the get_webhook_events tool to retrieve and inspect them.