polygon

The Polygon MCP Server exposes a set of tools that interface with the Polygon.io market data API. It provides capabilities for retrieving ticker details, real-time quotes, aggregates (historical bars), daily open/close prices, market status, ticker news, ticker search/listing, and ticker snapshots. These tools can be invoked via the MCP protocol by specifying the tool name and the required arguments, returning structured data suitable for integration into trading dashboards, analytics pipelines, or alerting systems.

To use the server, ensure the Polygon API key is configured in the environment (POLYGON_API_KEY). Start the Node.js server as configured in your MCP settings, then call tools such as get_market_status, get_ticker_details, get_aggregates, get_daily_open_close, get_ticker_news, list_tickers, or get_snapshot with the appropriate arguments. Responses will contain the requested market data in a consistent, machine-readable format compatible with your MCP client.

Prerequisites:

• Node.js (npm) installed on your system
• Access to this repository and build artifacts

Installation steps:

1. Clone the repository: git clone https://github.com/your-org/jwaresolutions-polygon-mcp-server.git cd jwaresolutions-polygon-mcp-server

2. Install dependencies: npm install

3. Build the server: npm run build

4. Prepare environment variables:

   • Create a .env file or export POLYGON_API_KEY with your Polygon.io API key: POLYGON_API_KEY=your-api-key

5. Run the server (as configured in MCP settings): Ensure you start the server using the mcp config that points to the built index.js, for example: node /path/to/polygon-server/build/index.js

6. Verify the server is running by invoking a test tool call through your MCP client.

Notes and tips:

• Ensure POLYGON_API_KEY is kept secret and not checked into version control.
• If you modify build outputs, remember to rebuild before deploying to production.
• The server exposes several tools; ensure your MCP client requests include the correct arguments (e.g., ticker symbols, date ranges, and limits).
• For historical data via get_aggregates, the timespan may be day, minute, etc., depending on Polygon.io support; validate against the API docs.
• When troubleshooting, check container or process logs for startup errors, especially related to environment variables or missing build artifacts.