get_portfolio_history — FinBridge MCP Tool Read-only
get_portfolio_history
(get portfolio history) is one of 26 tools on the
FinBridge
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_portfolio_history from your client
- Claude Code FinBridge get_portfolio_history run in your project directory
- Claude Desktop FinBridge get_portfolio_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FinBridge get_portfolio_history ~/.cursor/mcp.json
- VS Code FinBridge get_portfolio_history .vscode/mcp.json
- Zed FinBridge get_portfolio_history ~/.config/zed/settings.json
- Windsurf FinBridge get_portfolio_history ~/.codeium/windsurf/mcp_config.json
- Cline FinBridge get_portfolio_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FinBridge get_portfolio_history ~/.gemini/settings.json
- Grok FinBridge get_portfolio_history .mcp.json (in your project root)
- ChatGPT FinBridge get_portfolio_history Settings → Connectors → Advanced → Developer mode
- Claude.ai FinBridge get_portfolio_history Settings → Connectors → Add custom connector
- LangChain FinBridge get_portfolio_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http finbridge https://mcp.gronox.kr/mcpOther tools on this server
- screen_etfs
- import_portfolio
- restore_portfolio_snapshot
- get_portfolio
- get_watchlist
- manage_watchlist
- get_peers
- search_dart_company
- get_dart_financials
- get_dart_document
- get_dart_filings
- get_dart_major_events
- get_dart_insider_trades
- search_edgar_company
- get_edgar_financials
- get_edgar_filings
- get_edgar_insider_trades
- compare_financials_kr_us
- get_db_schema
- query_db
- get_stock_prices
- get_tw_insider_transfers
- get_valuation
- get_disclosure_feed
- get_edgar_13f
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.