emma-transactions-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EMMA_SHEET_GID | No | Optional sheet GID (tab ID) within the spreadsheet. Defaults to 0. | 0 |
| EMMA_SHEET_URL | Yes | URL or ID of the Google Sheet containing Emma transaction export (e.g., https://docs.google.com/spreadsheets/d/YOUR_SHEET_ID/pub?output=csv) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_transactionsB | List normalized Emma transactions with optional filters |
| get_spending_summaryB | Summarize income, spending, net movement, and totals by category, account, and month |
| get_metadataA | Return available categories, accounts, currencies, row count, and date range |
| validate_sheetB | Fetch and validate that the configured sheet can be parsed without returning transaction rows |
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 4 tools
Each tool serves a distinct function: metadata retrieval, spending summary, transaction listing, and sheet validation. No overlap in purposes.
All tool names follow a consistent verb_noun pattern (get_metadata, get_spending_summary, list_transactions, validate_sheet) with clear, descriptive verbs.
4 tools is well-scoped for a transaction management server, covering essential operations without being excessive or insufficient.
The server provides metadata, summaries, and transaction listing, but lacks write operations or advanced filtering. This seems intentional for a read-only analysis tool, so the gap is minor.