mono

This MCP server, mono, provides an interface for AI assistants to retrieve and format Monobank transactions and statements. It uses the Monobank API key you supply to fetch transactional data and returns it in a structured form suitable for natural language querying. The server exposes a tool named get_monobank_statement_from_to_date, which retrieves bank statements within a specified date range and formats the results for easy consumption by an AI assistant. To use it, start the server, ensure your environment variable MONO_API_KEY is set, and invoke the MCP-enabled tooling from your AI integration as documented by the MCP interface. The server is designed to securely access your own Monobank data and present it in a readable format for downstream tools and assistants.

Prerequisites:

• Bun v1.2.2 or higher
• Monobank API key

Installation steps:

1. Clone the repository: git clone https://github.com/yourusername/mono-mcp.git cd mono-mcp

2. Install dependencies using Bun: bun install

3. Create configuration in the project root:

   • Create a .env file
   • Add your Monobank API key: MONO_API_KEY=your_monobank_api_token_here

4. Run the MCP server: bun run dev

5. Verify the server is running and accessible through the MCP interface (as per your environment).

Tips and common issues:

• Ensure MONO_API_KEY is set in the environment or in a .env file loaded at startup.
• If bun run dev fails due to missing dependencies, try bun install again or verify Bun version compatibility.
• The get_monobank_statement_from_to_date tool expects valid date formats (e.g., YYYY-MM-DD). Validate inputs before invoking the tool.
• If you encounter API key errors, check Monobank API access and permissions for the key.
• This MCP server is designed for local or private deployments; expose it securely when used in production scenarios.