Chase MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| chase_auth_checkA | Check if user is logged in to Chase. Returns login status and instructions if not authenticated. Call this before any other Chase operations. |
| chase_auth_clearA | Clear stored Chase session cookies. Use this to log out or reset authentication state. |
| chase_accountsA | Get all Chase accounts - checking, savings, credit cards, investments, and loans. |
| chase_balanceC | Get the current balance for a specific account. |
| chase_transactionsC | Get recent transactions for an account. |
| chase_billsA | Get bills and payees set up in Chase Bill Pay. |
| chase_transfersC | Get recent transfer history. |
| chase_statementsC | Get available statements for an account. |
| chase_rewardsA | Get Ultimate Rewards points and cash back balance. |
| chase_transfer_previewA | Preview a transfer between accounts. Does NOT execute the transfer - provides instructions for completing it manually. |
| chase_bill_pay_previewA | Preview a bill payment. Does NOT execute the payment - provides instructions for completing it manually. |
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 11 tools
Each tool targets a distinct aspect of Chase banking: accounts, auth, balance, bills, rewards, statements, transactions, and transfers. There is no overlap in purposes.
All tools follow a consistent 'chase_verb_noun' pattern (e.g., chase_accounts, chase_balance, chase_transactions). Naming is uniform and predictable.
With 11 tools covering account management, authentication, balances, transactions, bills, rewards, statements, and transfers, the count is well-scoped for a personal banking MCP.
Core read operations are present, but critical write actions (bill pay execution, actual transfers) are only previews without execution. Missing features like credit card details (beyond balance) and investment account actions. This creates gaps for full financial management.