Skip to main content
Glama
horsfallnathan

Firefly III MCP Server

Related Servers

Alternatives to Firefly III MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage Firefly III personal finance accounts and transactions through the Model Context Protocol.
      14 npm
      85
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with a Firefly III personal finance instance, programmatically managing accounts, transactions, and related financial operations through the Model Context Protocol.
      14 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      This server gives AI assistants controlled read and write access to a Firefly III personal finance instance over MCP, exposing 139 operations across 24 entities with optional read-only mode and support for both stdio and authenticated HTTP transport.
      5
      80 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that allows AI assistants to interact with Lunch Money accounts, enabling management of transactions, categories, budgets, and other financial data through natural language commands.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects any MCP-compatible AI assistant to your Firefly III personal finance instance, enabling natural language queries about your finances.
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server that enables AI-powered interaction with YNAB (You Need A Budget) data, allowing users to query their budgets through conversational interfaces.
      23
      304 npm
      144
      MIT

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Tools have distinct purposes: echo for testing, get_version for server info, and the firefly_ tools for dynamic API access. However, firefly_execute is a broad catch-all that could be confused with many specific operations, but its name clearly indicates dynamic execution.

    Naming Consistency3/5

    Three tools follow a consistent firefly_ prefix pattern, but echo and get_version break this convention. This inconsistency could confuse agents expecting uniform naming.

    Tool Count5/5

    Five tools is well-scoped for a dynamic API wrapper. The single executor tool reduces the need for many individual endpoints, making the set compact and manageable.

    Completeness5/5

    The dynamic firefly_execute tool can perform any Firefly III operation, ensuring full coverage. Supporting meta-tools for schema and operation listing compensate for the lack of explicit endpoints.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive