options-chain

The options-chain MCP server exposes access to Tradier Sandbox data for an options chain and historical prices for a given symbol. It supports filtering by option type (calls, puts, or both), filtering strikes around the current price, and returning a concise set of relevant strikes to keep context sizes manageable. You can query for the options chain of a specific stock on a selected expiration date and also retrieve historical price data for a stock or a specific option contract within a time range. To use it, configure Claude Desktop to point at this MCP server and supply your Tradier sandbox API token in the environment. The server will handle the translation of natural language queries into Tradier API calls and return structured results that you can display or summarize in your assistant.

Prerequisites:

• Node.js installed on your machine
• Access to Tradier Sandbox API with a sandbox token

Installation steps:

1. Install Node.js from https://nodejs.org/en/download
2. Clone this repository to a local folder
3. Navigate to the project folder in your terminal
4. Install dependencies: npm install
5. Build the server (if required): npm run build
6. Run the MCP server: node path/to/build/index.js (or use your preferred start command)
7. In Claude Desktop, configure the MCP server with the appropriate command, path, and token environment variable as described in the Connecting section of the README.

Notes:

• The server relies on the Tradier Sandbox API, so ensure your sandbox token is valid and has the necessary scopes.
• The sandbox data is delayed, and the server is intended for informational use and development.

Tips and caveats:

• Ensure the full path to the built server entry (index.js) is correct in the mcp_config. If Claude/Desktop cannot locate node, provide the absolute path to the node executable.
• The token environment variable should be kept secret; do not share your sandbox token publicly.
• If you experience mismatches with data, verify that the Tradier Sandbox token is valid and that you are querying the correct symbol and expiration date.
• The server may throttle or limit responses based on Tradier API rate limits; design your prompts to request concise, batched results.
• When testing, you can start with simple queries like getting the options chain for a single symbol and a single expiration date to validate connectivity before enabling more advanced filters.