Firefly III MCP Server

What is Firefly III MCP Server?

A Model Context Protocol (MCP) server for Firefly III, a free and open-source personal finance manager. It allows AI tools to programmatically manage Firefly III accounts and transactions, enabling the creation of AI assistants for personal finance and accounting.

How to use Firefly III MCP Server?

Obtain a Personal Access Token from your Firefly III instance and provide it together with your Firefly III URL to the server. You can run the server locally via npx @firefly-iii-mcp/local, as an Express HTTP server (@firefly-iii-mcp/server), deploy to Cloudflare Workers, or run from source. Configure credentials via environment variables, request headers, or query parameters, and optionally filter the available tools using presets or custom tags to reduce token usage.

Key features of Firefly III MCP Server

• Interact with Firefly III instances via AI
• Programmatically manage accounts and transactions
• Extensible toolset for various financial operations
• Support for both local and cloud deployment
• Compatible with the Model Context Protocol standard
• Tool filtering via presets or custom tags to reduce token usage

Use cases of Firefly III MCP Server

• Automate personal finance management with an AI assistant
• Create AI-powered accounting tools for Firefly III
• Integrate Firefly III with MCP-compatible clients like Claude Desktop
• Focus on specific areas such as budgeting, reporting, or administration via tool presets

FAQ from Firefly III MCP Server

What are the prerequisites for using Firefly III MCP Server?

You need a running Firefly III instance. For Cloudflare Workers deployment, a Cloudflare account is also required.

How do I obtain a Personal Access Token for Firefly III?

Log in to your Firefly III instance, go to Options > Profile > OAuth, and create a new Personal Access Token. Copy the token immediately – it will not be shown again.

How do I configure authentication for the MCP server?

Authentication can be supplied via request headers (X-Firefly-III-Url and Authorization), query parameters (baseUrl and pat), or environment variables (FIREFLY_III_BASE_URL and FIREFLY_III_PAT). Headers are recommended for security.

Can I filter which tools the server exposes?

Yes. Use a preset (default, full, basic, budget, reporting, admin, automation) or specify exact tool tags (e.g., accounts,transactions,categories) via environment variables or command-line options.

What deployment options are available?

You can run the server locally via npx, as an Express-based HTTP server, deploy to Cloudflare Workers with a single click, or run from the source repository.