AmexAnalysis-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMEX_DEBUG | No | Optional. Enable debug mode with 'true'. | false |
| AMEX_DATA_DIR | No | Optional. Set custom path for data directory. | |
| AMEX_OUTPUT_DIR | No | Optional. Set custom path for output directory. |
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 |
|---|---|
| analyze_amex_spendingB | Analyze Amex credit card spending from CSV file |
| find_subscriptionsB | Find all subscriptions in Amex transactions |
| analyze_vendorC | Get detailed analysis of a specific vendor |
| find_anomaliesC | Find spending anomalies and potential fraud |
| spending_by_categoryB | Analyze spending broken down by category |
| export_analysisC | Export comprehensive spending analysis |
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 6 tools
Each tool targets a distinct analytical aspect: overall spending, subscriptions, specific vendors, anomalies, category breakdown, and export. No meaningful overlap exists between them.
Five of six tools follow a clear verb_noun convention (analyze_*, find_*, export_*). The outlier, spending_by_category, uses a noun phrase but is still readable and not jarringly inconsistent.
Six tools is a well-scoped count for a specialized spending-analysis server. Each tool covers a distinct need without redundancy or bloat.
The surface covers the core analysis lifecycle: overall analysis, drill-downs (vendor, category), anomaly detection, and export. Minor gaps like time-period comparison or raw transaction listing could be added, but the current set supports typical workflows.