easy-equities-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EE_MCP_ENV_FILE | No | Explicit path to a .env file. | |
| EE_MCP_COOKIE_DIR | No | Directory where session cookies are cached. | ~/.easy-equities-mcp |
| EE_SESSION_PERSONAL_PASSWORD | Yes | Password for the session. | |
| EE_SESSION_PERSONAL_PLATFORM | No | Platform for the session: 'easyequities' or 'satrix'. | easyequities |
| EE_SESSION_PERSONAL_USERNAME | Yes | Username for a session named PERSONAL (replace PERSONAL with your chosen session name). At least one session is required. |
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 |
|---|---|
| list_sessionsA | List all active logged-in sessions. |
| refresh_sessionA | Re-authenticate one session using credentials from the environment/.env. Call this from chat when a tool call fails because cookies have expired or to force a fresh login. Credentials are never passed through chat. Args: session: The session name, e.g. "personal". |
| refresh_all_sessionsA | Re-authenticate every configured session. Returns a per-session report. |
| list_accountsA | List all accounts for a session. Args: session: The session name (from list_sessions). |
| get_holdingsA | Get holdings (stocks/ETFs) for an account. Args: session: The session name (from list_sessions). account_id: The account ID (from list_accounts). include_shares: If true, fetch number of shares per holding (slower). |
| get_valuationsA | Get the valuation summary for an account. Args: session: The session name (from list_sessions). account_id: The account ID (from list_accounts). |
| get_transactionsA | Get transactions for the last year for an account. Args: session: The session name (from list_sessions). account_id: The account ID (from list_accounts). |
| get_transactions_for_periodA | Get transactions for an account between two dates. Args: session: The session name (from list_sessions). account_id: The account ID (from list_accounts). start_date: Start date in YYYY-MM-DD format. end_date: End date in YYYY-MM-DD format. |
| get_historical_pricesA | Get historical prices for an instrument. Args: session: The session name (from list_sessions). contract_code: The instrument contract code, e.g. "EQU.ZA.SYGJP". period: One of "OneMonth", "ThreeMonths", "SixMonths", "OneYear", "Max". |
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 9 tools
Most tools are clearly distinct (list_sessions vs list_accounts vs get_holdings), but refresh_session and refresh_all_sessions overlap in purpose (one is a subset of the other), and get_transactions vs get_transactions_for_period are similar except for the date range. Descriptions mitigate ambiguity well.
All tool names follow a consistent verb_noun pattern in snake_case: list_*, refresh_*, get_*. The verbs clearly reflect the action, and no mixed naming conventions or style inconsistencies are present.
With 9 tools, the server is well-scoped for its apparent purpose of managing sessions and retrieving account/investment data. Each tool earns its place, and the count is neither sparse nor overwhelming.
The tool surface covers session management, account listing, holdings, valuations, transactions, and historical prices—a solid read-only domain. Minor gaps exist, such as no account detail endpoint or instrument search, but agents can complete common workflows without major dead ends.