tf_btc_price — terminalfeed MCP Tool
tf_btc_price
(tf btc price) is one of 27 tools on the
terminalfeed
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call tf_btc_price from your client
- Claude Code terminalfeed tf_btc_price run in your project directory
- Claude Desktop terminalfeed tf_btc_price ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor terminalfeed tf_btc_price ~/.cursor/mcp.json
- VS Code terminalfeed tf_btc_price .vscode/mcp.json
- Zed terminalfeed tf_btc_price ~/.config/zed/settings.json
- Windsurf terminalfeed tf_btc_price ~/.codeium/windsurf/mcp_config.json
- Cline terminalfeed tf_btc_price ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI terminalfeed tf_btc_price ~/.gemini/settings.json
- Grok terminalfeed tf_btc_price .mcp.json (in your project root)
- ChatGPT terminalfeed tf_btc_price Settings → Connectors → Advanced → Developer mode
- Claude.ai terminalfeed tf_btc_price Settings → Connectors → Add custom connector
- LangChain terminalfeed tf_btc_price pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http terminalfeed https://terminalfeed.io/api/mcp
Other tools on this server
- tf_briefing
- tf_fear_greed
- tf_crypto_movers
- tf_predictions
- tf_earthquakes
- tf_climate_earthquakes
- tf_climate_weather_alerts
- tf_service_status
- tf_economic_data
- tf_forex
- tf_hf_trending
- tf_harnesses
- tf_solana_network
- tf_ai_stack_cves
- tf_premium_briefing
- tf_premium_macro
- tf_premium_github_velocity
- tf_premium_feed_reliability
- tf_premium_feed_reliability_history
- tf_premium_correlation_matrix
- tf_premium_agent_context
- tf_premium_world_deltas
- tf_payment_buy_credits
- tf_payment_confirm
- tf_payment_balance
- tf_payment_history
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.