Skip to main content
Glama
joeswann

PocketSmith MCP Server

by joeswann

Related Servers

Alternatives to PocketSmith MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      A personal MCP server that gives Claude native access to YNAB budget data.
      46
      -
    • F
      license
      B
      quality
      D
      maintenance
      MCP server that bridges Claude to Monarch Money for personal-finance analysis and lightweight edits.
      18
      -
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server implementation that provides programmatic access to personal finance data through LunchMoney's API, enabling AI assistants to manage transactions, budgets, categories, and assets.
      59
      2,639 npm
      109
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A personal finance tracker MCP server that imports Rocket Money data or connects banks via SimpleFIN to a local SQLite database, enabling Claude to analyze spending, subscriptions, cash flow, and debt payoff with complete privacy.
      15
      42 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A comprehensive MCP server for managing personal finances, enabling users to track expenses, manage budgets, monitor financial goals, and analyze spending patterns through an AI assistant. All data is stored locally in SQLite for complete privacy.
      9 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server providing full integration with the Lunch Money API to manage financial data including transactions, budgets, assets, and categories. It enables AI assistants to perform CRUD operations on financial records through a standardized HTTP interface.
      26
      MIT

    TDQS

    C2.9/5.0

    Scored across 56 tools

    Disambiguation3/5

    Tools are grouped by resource, but there are many similar list endpoints (e.g., list_accounts, list_institution_accounts, list_transaction_accounts, list_transaction_account_transactions) that could be confused, especially without reading descriptions carefully. The distinction between 'account' and 'transaction account' is not immediately obvious from names alone.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (list_*, get_*, create_*, update_*, delete_*). Minor deviations exist (get_me, reorder_accounts, assign_attachment, unassign_attachment, delete_forecast_cache) but these are understandable and do not break the overall pattern.

    Tool Count1/5

    With 56 tools, this far exceeds the 'typical' range of 3-15 and falls into the extreme mismatch category. Even for a comprehensive API, the sheer number creates a heavy, unwieldy surface that is likely to overwhelm agents and users.

    Completeness4/5

    The tool set covers CRUD for most major resources (accounts, transactions, categories, institutions, events, attachments) and includes read-only access for budgets, trends, currencies, and time zones. However, there is no delete or update for category rules, no delete for saved searches, and no create/delete for labels, which are minor but notable gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues