Ghostfolio MCP Server
Related Servers
Alternatives to Ghostfolio MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for managing and analyzing investment portfolios. It enables users to create and update portfolios, fetch real-time stock data and news, generate performance reports, and receive investment recommendations through natural language.-
- AlicenseBqualityDmaintenanceEnables interaction with the Morpho GraphQL API, providing tools for accessing market data, vaults, positions, and transactions through a Model Context Protocol (MCP) server.144 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Folio financial data through the Model Context Protocol, covering accounts, transactions, events, receipt bytes, categories, and payment drafts with preview-and-confirm writes.MIT
- FlicenseNot gradedqualityFmaintenanceIntegrates with Wealthfolio to provide real-time portfolio data, valuations, account management, and historical performance analytics through a Model Context Protocol interface compatible with OpenWebUI and automation tools.1-
- AlicenseNot gradedqualityDmaintenanceA read-only Model Context Protocol server that connects your Schwab brokerage account to LLM applications for portfolio monitoring and market data retrieval.MIT
- AlicenseNot gradedqualityDmaintenanceFastMCP server exposing brokerage and market tools (Angel One, Coinbase, News) via the Model Context Protocol, enabling portfolio queries and trade execution through natural language.1MIT
TDQS
Scored across 39 tools
Several tool clusters overlap: get_symbol_data, get_market_data_for_asset, get_historical_data, get_position, and get_asset_profile all retrieve symbol/asset-level data, and get_portfolio_details, get_portfolio_holdings, get_portfolio_performance, get_investments, and get_dividends all return time-grouped portfolio breakdowns. Descriptions do differentiate them (e.g. current price vs. historical date vs. position quantity vs. company metadata), which keeps selection mostly possible, but an agent must read carefully to pick correctly.
Nearly all tools are snake_case with a leading verb, but the verb set is broad (get/create/update/delete/add/upsert/remove/lookup/transfer/export/import) and there are minor inconsistencies like lookup_symbols vs get_*, upsert_asset_profile vs update_activity, and remove_from_watchlist vs delete_*. Still, the pattern is largely predictable and readable.
39 tools is heavy even for a full portfolio-management API, spanning accounts, activities, balances, asset profiles, market data, watchlist, benchmarks, import/export, and health. It exceeds the 25+ 'too many' threshold and could be consolidated (e.g. merging the asset-data getters).
Coverage is broad: CRUD for accounts and activities, balance history, asset profiles, market data, watchlist add/remove, benchmarks, portfolio reporting, import/export, and health. Minor gaps exist (no create/update benchmark, no get-single-activity by ID), but most workflows are fully covered.