ChatGPT
Open the SiftingIO app in ChatGPT and connect your account.
Open in ChatGPT (opens in a new tab)Real-time stock, forex and crypto data in ChatGPT and Claude. Retrieve historical OHLCV bars and market calendars, or connect the open-source MCP server to Cursor, VS Code and Claude Code.
View on GitHubUse the hosted SiftingIO connector in ChatGPT or Claude without installing a server or entering an API key. For Cursor, VS Code, Claude Code, or a broader set of data tools, run the open-source server locally with your SiftingIO API key. These are separate editions: the hosted connector has 10 read-only tools; the local npm server has 36.
Choose your assistant, sign in to SiftingIO, and start asking for market data. Both use the same hosted connector with 10 read-only tools.
Open the SiftingIO app in ChatGPT and connect your account.
Open in ChatGPT (opens in a new tab)Open SiftingIO in the Claude connector directory and connect your account.
Open in Claude (opens in a new tab)market-data:read lets the assistant retrieve market data on your behalf. Your SiftingIO plan determines market access and request limits; each tool call uses your existing API quota. Access is read-only and does not allow trading or billing changes. Manage or disconnect each app in Connected apps.These tools are available in the ChatGPT and Claude directory connections. The local edition below has a broader toolset and a separate setup.
Prices are retrieved when you ask. For a continuously updating feed in your own application, use the WebSocket API.
Copy a question into ChatGPT or Claude with SiftingIO enabled. Each example uses the hosted tools above.
Enable SiftingIO in the conversation and confirm you completed the SiftingIO permission screen. Your assistant account or workspace must allow connectors. If an organization manages your assistant, ask its administrator to enable access.
Reconnect from the SiftingIO listing in ChatGPT or Claude, sign in to the intended SiftingIO account, and approve access again. Refresh Connected apps to check its status.
Check your plan and remaining quota in the dashboard. Confirm the symbol in the symbol catalog, then try a smaller date range. For further help, contact support with the tool name and error message. Keep credentials out of your message.
Use the local edition in Claude Desktop, Claude Code, Cursor or VS Code when you need company fundamentals, SEC filings, ownership data, economic events or on-chain tools alongside prices and history. Its 36 tools use the Model Context Protocol and authenticate with your SiftingIO API key. Data access and request limits follow your plan.
npx, so there is nothing to clone, build, or deploy. It reads your key from the SIFTING_API_KEYenvironment variable and uses it to authenticate requests to the SiftingIO API. You do not paste it into your assistant's prompts. Both runtimes are MIT-licensed: the TypeScript server (siftingio-mcp on npm) and a Python server, with source in the repository.Connecting takes three things:
npx command that runs the server.From your dashboard, create an API key. It looks like sft_... and is what the assistant uses to authenticate. Keep it private, the same way you would any password.
The server is published on npm as siftingio-mcp, so there is nothing to clone and nothing to build. Run it once to check it starts, or skip straight to the config block below and let your client launch it for you. If you would rather build from source, the repository has the steps.
# Run the published server straight from npm. No clone, no build step.npx -y siftingio-mcp # Or register it with Claude Code in one command:claude mcp add siftingio -e SIFTING_API_KEY=sft_... -- npx -y siftingio-mcpAdd a local MCP server to your client's config: Claude Desktop's claude_desktop_config.json, Cursor's MCP settings, or claude mcp add on Claude Code. Point the command at npx and pass your key through the env block. Use this example for Claude Desktop or Cursor:
{ "mcpServers": { "siftingio": { "command": "npx", "args": ["-y", "siftingio-mcp"], "env": { "SIFTING_API_KEY": "sft_..." } } }}In VS Code, run MCP: Add Server, choose Command (stdio) and enter npx -y siftingio-mcp. Add SIFTING_API_KEYto the generated server configuration's environment. VS Code supports different configuration destinations; follow its MCP setup guide for the format used by your agent.
env configuration as SIFTING_API_KEY. The server uses it to authenticate requests to SiftingIO. Keep it out of prompts, shared files and source control.Instead of launching the server per client, you can run one process over MCP's Streamable HTTP transport and point HTTP-capable clients at http://127.0.0.1:3000/mcp. The npm package ships a second command, siftingio-mcp-http, for exactly this:
SIFTING_API_KEY=sft_... npx -y -p siftingio-mcp siftingio-mcp-http# → MCP endpoint at http://127.0.0.1:3000/mcp claude mcp add --transport http siftingio http://127.0.0.1:3000/mcpPORT to change the port (it defaults to 3000), and set MCP_AUTH_TOKEN if you want it to require an Authorization: Bearer token on every request.Once connected, the assistant picks the right tool for each question. The local edition provides 36 tools across these areas:
The tools return the same normalized data shapes as the REST API, so what the assistant sees is what your production app gets. The server also ships guided prompts, company_snapshot, compare_companies, and market_now, that clients can surface as slash-commands. See the repository for the full tool list and the parameters each one takes.
You do not call tools yourself. Ask a normal question and the assistant chooses and runs the right ones. For example:
For a focused research workflow, ask for a company's latest filings and its daily prices over the same period. The assistant can combine the relevant tools while keeping the dates and sources in its answer.
BTCUSD for crypto and EURUSDfor forex. The assistant usually maps a name like “Bitcoin” to the right symbol on its own.Alongside the TypeScript server, an open-source Python server offers the same idea for Python-first setups. It also runs locally, connects over stdio by default, and reads your key from an environment variable:
{ "mcpServers": { "siftingio": { "command": "siftingio-mcp", "env": { "SIFTING_API_KEY": "sft_..." } } }}SIFTING_API_KEY to your key so the server can authenticate.A market data MCP server lets an AI assistant retrieve financial data through the Model Context Protocol. SiftingIO provides current prices, historical OHLCV bars and market calendars, so the assistant can answer using retrieved data and timestamps.
Open SiftingIO in the Claude connector directory, choose Connect, sign in to SiftingIO and approve market-data:read access. Enable SiftingIO in your conversation. The directory connection does not need an API key, manual client ID or client secret.
Open the SiftingIO app in ChatGPT and connect your SiftingIO account. Approve read-only access, then select SiftingIO in your conversation and ask for a symbol, date range or market schedule. Your SiftingIO plan determines available data and request limits.
The hosted connector runs on SiftingIO infrastructure and provides 10 tools in ChatGPT and Claude. The local open-source server runs on your machine and provides 36 tools, adding company fundamentals, SEC filings, insider and institutional holdings, economic events and on-chain data. Hosted connections use account sign-in; the local server uses your SiftingIO API key.
Yes. The hosted connector includes stocks_bars, forex_bars and crypto_bars for US stock, forex and crypto history. Specify the symbol, interval and date range in your question. Available history depends on the dataset and symbol; historical depth follows the underlying SiftingIO API.
Yes. Use the local open-source server with npx -y siftingio-mcp and configure SIFTING_API_KEY in the server environment. Follow your client's configuration format. The guide includes a Claude Desktop and Cursor example, a Claude Code command and VS Code setup guidance.
Yes. A free account can authorize the hosted connector or create a key for the local server, with no card. Free limits are 10,000 REST calls per month and 60 requests per minute, with full available historical depth. Each data tool call uses your API quota. There is no separate MCP charge; your assistant's own plan must support the connection method you choose.
The hosted connector requests market-data:read permission through OAuth. It can retrieve market data within your account's permissions, but cannot place trades or change billing. Review and disconnect each app in Connected apps in your SiftingIO dashboard.
MCP tools retrieve real-time snapshots when called. They do not maintain a continuous price stream in the conversation. Use the SiftingIO WebSocket API for continuously updating charts, alerts or application feeds.
With stdio, your client launches the server as a local command. The local TypeScript server also supports Streamable HTTP at http://127.0.0.1:3000/mcp, binding to loopback and rejecting non-local origins. This local address is separate from the hosted ChatGPT and Claude connector.
Yes. SiftingIO also provides an MIT-licensed Python server that runs locally and reads SIFTING_API_KEY from its environment. Follow the Python repository's installation instructions and tool documentation.
Connect the hosted app with your SiftingIO account, or use an API key with the local server. The open-source repositories have the local edition's full tool list and setup notes.