fintable-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FINTABLE_COOKIES | No | Full cookie string from Chrome DevTools for manual authentication. | |
| FINTABLE_SESSION_COOKIE | No | Just the session cookie value for simple manual authentication. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fintable_list_accountsA | List all bank accounts connected to Fintable with balances and latest transaction dates. Returns account names, balances, latest transaction dates, and provider/bank/account IDs. Use this to get an overview of all connected financial accounts. Returns: str: JSON list of accounts with name, balance, latest_transaction, provider, bank_id, account_id. |
| fintable_list_categoriesA | List all transaction categories configured in the Fintable categorizer. Categories are organized into groups (e.g., COGS, Expense, Income). Use this to see what categories exist before creating new ones or rules. Returns: str: JSON list of categories with their names. |
| fintable_list_rulesA | List all categorization rules. Rules auto-categorize transactions based on description patterns. Each rule has a pattern (e.g., 'Home Depot') and a target category (e.g., 'COGS'). When 'Run All Rules' is triggered, transactions matching the pattern get categorized. Args: params: page number for pagination (rules are paginated). Returns: str: JSON list of rules with id, pattern, category, and display text. |
| fintable_list_transactionsA | List transactions from the Fintable transactions page. Supports searching by description and pagination. Shows date, description, amount, category, and account for each transaction. |
| fintable_create_categoryA | Create a new transaction category in Fintable. The category will appear in the categorizer sidebar and can be used in rules. Use group_header to place the category under a group (e.g., 'Expense', 'COGS', 'Income'). |
| fintable_create_bulk_categoriesA | Create multiple transaction categories at once — the batch operation that saves you from clicking through the UI 20 times! Each category is created sequentially with proper page state management. |
| fintable_create_ruleA | Create a new simple categorization rule. A simple rule matches transaction descriptions containing the pattern text and assigns them to the specified category. After creating rules, use fintable_run_all_rules to apply them. |
| fintable_create_bulk_rulesA | Create multiple categorization rules at once — batch rule creation! Each rule maps a transaction description pattern to a category. Optionally runs all rules after creation to categorize existing transactions. |
| fintable_run_all_rulesA | Run all categorization rules to auto-categorize transactions. This triggers the same action as clicking 'Run All Rules' in the Fintable UI. All rules are applied to uncategorized transactions in priority order. |
| fintable_delete_ruleA | Delete a categorization rule by its ID. Use fintable_list_rules to find rule IDs. This is irreversible. |
| fintable_sync_accountsA | Trigger a sync of all connected bank accounts via Plaid. This fetches the latest transactions and balances from your connected banks. |
| fintable_resync_spreadsheetsA | Re-sync categories and transactions to connected Airtable/Google Sheets integrations. Use this after making category changes to push updates to your spreadsheets. |
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 12 tools
Each tool targets a distinct action and resource. Bulk operations are clearly named and separate from single operations, and all list/delete/sync tools have unique purposes.
All tools follow the predictable fintable_verb_noun pattern with snake_case. 'Bulk' modifiers are consistently used for batch operations, and verbs like create, list, delete, run, sync are used appropriately.
12 tools cover the core functionality of managing categories, rules, accounts, and transactions without redundancy or excessive granularity.
The set provides create/list/delete for rules, create/list for categories, and sync operations. Missing update operations for categories and rules, and no direct transaction categorization tool, but the domain is still functional.