Stocktwits MCP server

@pipeworx/stocktwits

StockTwits MCP — stock-focused social sentiment. Keyless read endpoints, 200 req/hr per IP.

Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.

Tools

• symbol_stream(symbol, since?, max?, limit?, filter?) — messages mentioning a ticker
• userstream(userid, since?, max?, limit?) — messages from a user
• trending_symbols(limit?) — top trending tickers
• trending_messages(limit?) — trending messages
• suggested_symbols(limit?) — editorial suggested
• symbol_search(q, limit?) — symbol search
• chart_data(symbol, period?) — OHLCV price bars for a ticker; period is 1D (default, 5-minute bars), 1W, 1M, 3M, 6M, YTD, 1Y, 5Y or ALL
• watchlists(user_id) — user's watchlists
• watchlist(watchlist_id, since?, max?, limit?) — messages from a watchlist

Notes

StockTwits public read endpoints are keyless but rate-limited (200/hr/IP). The gateway egress IP is shared so heavy use may be throttled; the upstream returns 429 in that case and this pack surfaces it cleanly.

Data source

https://api.stocktwits.com/api/2 for streams, trending, search and watchlists; https://ql.stocktwits.com/chart (the chart feed behind stocktwits.com) for chart_data.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "stocktwits": {
      "url": "https://gateway.pipeworx.io/stocktwits/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/stocktwits/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1679+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/symbol_stream \
  -H 'Content-Type: application/json' \
  -d '{"symbol":"TSLA"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/symbolstream. Find one: POST https://gateway.pipeworx.io/v1/tools/searchpacks with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "stocktwits": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-stocktwits"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-stocktwits

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Shortened. The full README is on GitHub.