0

tv-mcp

worthwhile

Solid MCP bridge to a specialized options API — genuine capability, not a thin wrapper over Claude's existing knowledge.

Source ↗
tv-mcp icontv-mcp social preview

What it is

An MCP server that proxies requests from an AI agent to Trading Volatility's v2 API, exposing 15 tools for querying options market structure (GEX, gamma flips, dealer positioning, skew, max pain, volume, trade setups). Stateless, read-only, supports stdio and HTTP+SSE transports.

How it differs from vanilla Claude

A base Claude agent cannot query real-time options data or perform market-structure analysis — it knows textbook definitions but has no access to live GEX curves, gamma flip levels, or dealer positioning. This MCP server bridges that gap by exposing a structured API through standard tools.

Skill, plugin, or workflow shift?

MCP integration is the correct choice — it's a plugin that adds a new data modality to any MCP-compatible agent, requiring no workflow shift. The agent retains full autonomy, just gains new tools.

Devil's advocate — is this just complexity?

This is a thin wrapper around a specific API. A vanilla Claude agent with web search and a few prompt templates could replicate the most common queries (e.g., 'get AAPL gamma levels') by hitting the TV API directly via HTTP tool calls. The MCP server saves maybe 20 lines of boilerplate per tool. For a user who already has an MCP client, it's convenient; for someone building a custom pipeline, it's unnecessary abstraction.

What would make it better

Add local caching for historical series to reduce API calls. Provide a prebuilt dashboard or visualization layer for gamma curves. Support configurable alerting (e.g., 'notify when GEX flips above X'). Publish benchmark latency data for the HTTP transport.

The honest case for it

If you trade options and use an MCP-compatible agent, this tool gives you instant access to a specialized, curated data source that would otherwise require manual scraping or a custom script. The server is well-architected (stateless, per-request auth, two transports), and the tool names are aligned with an agent's conversational flow.

Who it's for

Audience fit

Primarily forAI-first Engineer
AI-first Engineer85

Depth and leverage for a technical engineer who wants to understand it and level up their workflow — not just offload work.

Vibe Coder30

Value for someone who wants a more capable tool without the technical depth — accessible, does-it-for-you.

Deeply technical, requires understanding of options market structure and MCP integration. Vibe coders won't get value without domain knowledge.