project_tvl_history — AlphaGrowth MCP Tool
project_tvl_history
(project tvl history) is one of 32 tools on the
AlphaGrowth
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call project_tvl_history from your client
- Claude Code AlphaGrowth project_tvl_history run in your project directory
- Claude Desktop AlphaGrowth project_tvl_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AlphaGrowth project_tvl_history ~/.cursor/mcp.json
- VS Code AlphaGrowth project_tvl_history .vscode/mcp.json
- Zed AlphaGrowth project_tvl_history ~/.config/zed/settings.json
- Windsurf AlphaGrowth project_tvl_history ~/.codeium/windsurf/mcp_config.json
- Cline AlphaGrowth project_tvl_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AlphaGrowth project_tvl_history ~/.gemini/settings.json
- Grok AlphaGrowth project_tvl_history .mcp.json (in your project root)
- ChatGPT AlphaGrowth project_tvl_history Settings → Connectors → Advanced → Developer mode
- Claude.ai AlphaGrowth project_tvl_history Settings → Connectors → Add custom connector
- LangChain AlphaGrowth project_tvl_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http data https://alphagrowth.io/mcp
Other tools on this server
- find_projects
- project_metrics
- project_community
- rank_projects
- categories
- upcoming_projects
- upcoming_tges
- project_funding
- recent_funding_rounds
- top_investors
- investor_profile
- chains
- chain_metrics
- fees
- volumes
- token_prices
- token_price_history
- stablecoins
- stablecoin_chains
- treasury_companies
- yield_pools
- yield_pool
- token_unlocks
- grants
- spaces
- space
- dao_treasuries
- dao_treasury_snapshot
- dao_treasury_history
- dao_holdings_history
- dao_treasury
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.