Corpus MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your personal API Key generated from the Corpus Tracker settings. | |
| API_URL | Yes | The URL of your Corpus Tracker backend API (e.g., https://my-corpus.vercel.app/api/v1). |
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 |
|---|---|
| get_my_profileB | Get the current user's profile and settings. |
| list_corporaB | List all corpora (profiles) the user belongs to. |
| get_portfolio_summaryA | Get aggregated net worth, asset breakdown, and liabilities. |
| get_top_holdingsC | Get top holdings by value. |
| get_portfolio_historyC | Get portfolio history. |
| list_gold_holdingsB | List all gold holdings. |
| add_gold_holdingC | Add a new gold holding. purchase_date: YYYY-MM-DD format |
| delete_gold_holdingC | Delete a gold holding by ID. |
| live_gold_priceB | Get live gold price. |
| history_of_gold_priceD | Get history of gold price. |
| list_stock_holdingsB | List all stock holdings. |
| add_stock_holdingC | Add a new stock holding. symbol: Stock Symbol (e.g. RELIANCE.NS) |
| update_stock_holdingC | Update an existing stock holding. |
| delete_stock_holdingC | Delete a stock holding by ID. |
| search_stock_symbolC | Get history of stock price. |
| add_stock_transactionC | Add a new transaction to a stock holdind transaction_type: BUY or SELL |
| list_transactionsC | List transactions with filters. Dates in YYYY-MM-DD. Type: 'income', 'expense', or 'all'. |
| add_transactionB | Add a new income or expense transaction. type: "income" or "expense" category: get user category from get_categories tool |
| delete_transactionC | Delete a transaction by ID. |
| get_categoriesB | Get user budget categories. |
| get_cashflow_trendB | Get income vs expense trend for the last N days. |
| list_mutual_fund_holdingsB | List all mutual fund holdings. |
| list_emergency_fund_holdingsA | List all emergency fund holdings. |
| add_emergency_fund_contributionC | Add a new emergency fund contribution. |
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 24 tools
Most tools have distinct purposes, but some overlap exists: 'add_stock_transaction' and 'add_transaction' could be confused as both handle transactions, and 'search_stock_symbol' (which gets stock price history) overlaps with 'add_stock_holding' (which involves stock data). Descriptions help clarify, but minor ambiguity remains.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'add_emergency_fund_contribution', 'list_gold_holdings', 'get_cashflow_trend', and 'delete_transaction'. There are no deviations in style or convention, making the set predictable and readable.
With 24 tools, the count is borderline heavy for a personal finance server, as it may overwhelm agents with many similar listing and adding operations. While comprehensive, it could be streamlined without losing functionality, placing it in the upper range of typical scopes.
The server provides strong coverage for personal finance management, including CRUD operations for holdings and transactions, analytics like cashflow trends, and portfolio summaries. Minor gaps exist, such as no update tools for emergency funds or mutual funds, but agents can work around these with available tools.