Skip to main content
Glama
leafeye

lunchmoney-mcp-v2

by leafeye

Related Servers

Alternatives to lunchmoney-mcp-v2

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to interact with your Lunch Money personal finance data, providing tools for managing transactions, categories, budgets, assets, and accounts.
      15
      27 npm
      ISC
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and MCP clients to access and manage LunchMoney personal finance data, including transactions, budgets, accounts, categories, tags, recurring items, and crypto holdings through natural language.
      59
      3,698 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-enabled assistants to access and interact with your Lunch Money financial data, including transactions, spending, and uncategorized items, through natural language.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables natural-language exploration of Lunch Money transactions, budgets, accounts, and recurring expenses via MCP, with read-only financial access.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables reading and writing YNAB budget data, such as listing budgets, accounts, categories, transactions, and creating or updating transactions, through natural language commands.
      8
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables interaction with You Need A Budget (YNAB) through their API, allowing users to manage budgets, accounts, categories, transactions, payees, and scheduled transactions through natural language.
      12
      16 npm
      1
      GPL 3.0

    TDQS

    A4.1/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct resource or operation. Read (list/get), write (manage), batch (bulk_update), and structural operations (split/group) are clearly separated, minimizing the chance of misselection.

    Naming Consistency4/5

    The naming follows a verb_noun convention with intuitive prefixes like get_/list_, manage_, bulk_update_, split_, and group_. The only minor inconsistency is mixing get_ and list_ for read operations (e.g., get_accounts vs list_transactions), but the pattern is still predictable.

    Tool Count5/5

    With 14 tools, the server covers user info, transactions, categories, tags, accounts, recurring items, and budget summaries—each earning its place. This is within the ideal 3-15 range and feels well-scoped.

    Completeness4/5

    The tool set provides solid coverage for core CRUD on transactions, categories, tags, and accounts, plus advanced transaction operations (split/group/bulk update). Minor gaps exist, such as recurring items being read-only and no bulk delete, but agents can work around these.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues