Pocketsmith MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POCKETSMITH_API_KEY | Yes | Your Pocketsmith API key. Generate this in your Pocketsmith account under Settings > API & Developers. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pocketsmith_list_transactionsB | List transactions from Pocketsmith with optional filters. Transfers excluded by default. |
| pocketsmith_get_transactionB | Get details of a specific transaction by ID |
| pocketsmith_update_transactionB | Update a transaction's category, payee, note, labels, or review status |
| pocketsmith_list_categoriesA | List all categories. Returns a flat list with full category paths for easy lookup. |
| pocketsmith_search_transactionsA | Search transactions by keyword (payee, category, notes). Transfers excluded by default. |
| pocketsmith_categorize_transactionA | Categorize a transaction by setting its category. This is a convenience wrapper around update_transaction. |
| pocketsmith_create_category_ruleB | Create a rule to automatically categorize future transactions matching a payee pattern |
| pocketsmith_get_statusB | Get connection status and authenticated user info |
| pocketsmith_list_accountsA | List all accounts with balances and details |
| pocketsmith_get_accountB | Get details of a specific account by ID |
| pocketsmith_get_budget_summaryC | Get budget summary for a period and date range |
| pocketsmith_list_budgetC | List per-category budget analysis |
| pocketsmith_get_trend_analysisB | Get trend analysis across categories and scenarios |
| pocketsmith_create_transactionC | Create a new transaction |
| pocketsmith_list_labelsA | List all labels used in transactions |
| pocketsmith_list_transactions_by_accountA | List transactions for a specific account with optional filters. Transfers excluded by default. |
| pocketsmith_list_transactions_by_categoryB | List transactions for one or more categories. Transfers excluded by default. |
| pocketsmith_create_categoryC | Create a new category |
| pocketsmith_list_eventsB | List events (recurring transactions) for a date range |
| pocketsmith_create_eventB | Create a new event (recurring transaction) |
| pocketsmith_delete_transactionB | Delete a transaction by ID |
| pocketsmith_list_transaction_accountsA | List all transaction accounts with balances and details |
| pocketsmith_list_category_rulesA | List all category rules (automatic categorization rules) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Each tool targets a specific resource and action (e.g., get, list, create, update, search) with no overlapping purposes. Even similar tools like list_transactions and list_transactions_by_account are clearly distinguished by scope.
All tools follow a consistent 'pocketsmith_verb_noun' pattern in snake_case, with verbs like get, list, create, update, delete, search, categorize. No mixing of styles.
23 tools is well-scoped for a personal finance management server covering accounts, transactions, categories, budgets, events, labels, trends, and status. Each tool serves a distinct purpose without redundancy.
The tool set covers core CRUD operations for transactions and basic operations for categories, events, and accounts. However, missing update/delete for categories and events are minor gaps that agents can work around.