benepass-mcp
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_loginB | Start Benepass email OTP login. Sends a one-time code to the email and returns a short-lived challenge session. |
| complete_loginA | Complete Benepass login with the email OTP and challenge session from start_login. Persists a local session; never returns tokens. |
| auth_statusA | Show whether a local Benepass session exists, and the logged-in email. Never returns secrets. |
| logoutB | Delete the local Benepass session file. |
| list_workspacesA | List Benepass workspaces for the logged-in user (employment and personal). Does not require a workspace header. |
| list_accountsA | List benefit accounts and balances for the current workspace. |
| list_benefitsA | List enrolled benefits derived from accounts (Benepass has no /v2/me/benefits/ endpoint). Includes available balance. |
| list_transactionsB | List transactions for the current workspace. Paginate with limit/offset; optionally filter by benefit_id. |
| get_hsa_account_detailsA | Fetch Health Savings Account details (US HSA). May 404 for non-US users. |
| get_hsa_investmentsA | Read HSA investment data by trying known GET paths on an HSA account. First 2xx wins. Reverse-engineered; paths may 404. |
| list_documentsA | List documents available in the current workspace (statements, plan docs, tax forms). |
| get_documentA | Fetch a single document by id. |
| get_current_userA | Fetch the current Benepass user profile (GET /v2/me/). |
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 13 tools
Each tool targets a distinct operation (auth, list, get) on distinct resources (user, workspaces, accounts, benefits, transactions, HSA, documents). No two tools appear to overlap in purpose, making selection unambiguous.
Most tools follow a verb_noun pattern (list_*, get_*, start_login, complete_login). Minor deviations include auth_status (noun-like) and logout (single verb), but overall the convention is clear and predictable.
13 tools is within the ideal 3-15 range and aligns well with the server's scope of accessing Benepass data. Each tool serves a clear purpose without redundancy, making the set well-proportioned.
The surface covers core read operations (auth, lists, details) with no obvious dead ends. Minor gaps include the lack of individual transaction detail fetch and potential reverse-engineering fragility of HSA investments, but the main workflows are supported.