OptionContext
# OptionContext MCP Server
Official Model Context Protocol (MCP) Server for the OptionContext Stock and Options Data APIs. This premium integration delivers rich analytical and structural data for Indian Stock Markets directly into LLM agents and clients supporting the Model Context Protocol.
## Installation
You can install the OptionContext MCP package using `pip`, or run it on-demand with Node and LLM-centric workflows.
### Installation via pip
```bash
pip install optioncontext_mcp
```
### Direct Run with uvx (Python environment)
```bash
uvx optioncontext-mcp
```
## Configuration
To use the OptionContext MCP Server, you must specify your API key and base endpoint URL. You can configure these options via environment variables:
- `OPTIONCONTEXT_API_KEY`: Your Agent-as-a-Service API key.
- `OPTIONCONTEXT_BASE_URL`: The OptionContext endpoint gateway URL (defaults to `https://mcp.optioncontext.com` if omitted).
For local or custom API gateway environments, `OPTIONCONTEXT_BASE_URL` will fallback automatically to `FASTAPI_BASE_URL` if defined.
## Available Tools
The MCP Server exposes the following powerful market analytical tools to any connected client:
1. **`suggest_symbols`**
- **Description**: Search and resolve correct ticker symbols (e.g., searching 'Reliance' to get 'RELIANCE').
- **Arguments**:
- `query` (string): The search text or company name.
2. **`get_market_context`**
- **Description**: Fetch live quote details, last traded price (LTP), volume, and context for Stocks, Indices, and Futures.
- **Arguments**:
- `symbol` (string): Ticker symbol (e.g. 'NIFTY', 'BANKNIFTY', 'RELIANCE').
- `expiry` (string, optional): Expiry cycle ('SPOT', 'NEAR', 'FAR', 'NEXT'). Default is 'SPOT'.
- `asset_type` (string, optional): Asset category ('stock', 'index', 'future', 'auto'). Default is 'auto'.
- `api_key` (string, optional): Override API Key. If omitted, uses environment key.
3. **`get_option_chain`**
- **Description**: Fetch complete option chain matrix including PCR, ATM strike, CE/PE quotes, volume, and Greeks.
- **Arguments**:
- `symbol` (string): Underlying index or stock ticker (e.g. 'NIFTY', 'BANKNIFTY').
- `api_key` (string, optional): Override API Key. If omitted, uses environment key.
4. **`get_historical_data`**
- **Description**: Fetch historical daily/intraday OHLCV candles (Requires Plan B subscription).
- **Arguments**:
- `symbol` (string): Ticker symbol.
- `from_date` (string): YYYY-MM-DD.
- `to_date` (string): YYYY-MM-DD.
- `interval` (string, optional): Candle interval ('ONE_MINUTE', 'FIVE_MINUTE', 'FIFTEEN_MINUTE', 'ONE_DAY'). Default is 'ONE_DAY'.
- `api_key` (string, optional): Override API Key.
---
Disclaimer & Risk Warning:
- Data Delay: All market prices, quotes, and option chains provided represent the last completed minute (minimum 1-minute delayed feed) and are not real-time tick feeds.
- Accuracy: Data is provided on an 'as-is' basis without warranties of absolute accuracy or timeliness.
- No Liability: The service is strictly for analytical/educational purposes. We assume no liability for any trading losses or investment decisions.
- Regulatory Risk Disclosure: Trading in derivatives (options and futures) involves high risk. Past performance is not indicative of future results.
TDQS
Scored across 6 tools
Each tool serves a clearly distinct purpose: market context for a single symbol, batch market context, option chain, historical data, symbol search, and API key info. The single versus batch distinction is clear, and option chain/historical data are fundamentally different data types.
All tools use lowercase snake_case, and five of six follow a consistent 'get_' prefix pattern. The exception is 'suggest_symbols', which still uses a verb but deviates from the 'get_' convention, making it slightly inconsistent.
Six tools is well within the ideal range for a market data server. Each tool covers a necessary function without unnecessary bloat, making the count appropriate for the server's stated purpose.
The tool surface covers the core needs of a market data context server: live quotes (single and batch), option chains, historical data, symbol resolution, and API key validation. No obvious dead ends or missing operations for the intended use case.