Stocktwits

What Stocktwits MCP server does

The Stocktwits MCP server exposes read-only access to StockTwits data for agent workflows focused on market discussion and ticker activity. It retrieves messages associated with a symbol, messages posted by a user, messages linked to a watchlist, and the platform's trending messages.

Symbol discovery is supported through trending symbols, editorially suggested symbols, and text-based symbol search. The chart_data tool provides OHLCV price bars for a ticker. Supported chart periods include 1D, 1W, 1M, 3M, 6M, YTD, 1Y, 5Y, and ALL; 1D is the default and uses five-minute bars.

This is a read-only interface. The provided material does not describe tools for posting messages, editing watchlists, placing trades, or accessing private account data.

How it works

The Stocktwits MCP server can be connected in two ways. A hosted connection uses the Pipeworx gateway at https://gateway.pipeworx.io/stocktwits/mcp. A local installation runs the npm package with npx and communicates through standard input and output. Both modes expose the Stocktwits pack's tools, while their surrounding gateway behavior differs.

The hosted pack endpoint also lists shared Pipeworx meta-tools, so its tools/list response contains more tools than the Stocktwits-specific set. Those shared tools can route questions across the wider Pipeworx catalog. The standalone process exposes only the Stocktwits tools and does not provide that gateway routing layer.

The underlying data comes from StockTwits API endpoints for streams, trends, search, and watchlists. Chart data comes from the chart feed used by StockTwits' website. The tools accept optional parameters such as since, max, limit, and filter where applicable.

Setup and configuration

For a hosted MCP connection, add the gateway URL to an MCP client's server configuration:

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

For local stdio execution, use the package through npx:

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

No environment variables or account credentials are specified for the standalone setup. The hosted endpoint can also be called through the Pipeworx HTTP tools API, for example by posting JSON to /v1/tools/symbol_stream.

Tools and capabilities

• symbol_stream: find messages mentioning a ticker, with optional time, count, limit, and filter controls.
• user_stream: retrieve messages from a specified user.
• trending_symbols and trending_messages: inspect current platform trends.
• suggested_symbols: retrieve editorially suggested symbols.
• symbol_search: search for symbols by query.
• chart_data: retrieve OHLCV bars for a ticker and selected period.
• watchlists and watchlist: list a user's watchlists or retrieve messages associated with one.

Limitations and notes

Public reads do not require an API key, but the stated limit is 200 requests per hour per IP. Hosted gateway traffic uses a shared egress IP, so frequent use by multiple callers can trigger throttling. When the upstream service returns HTTP 429, the pack surfaces that condition.

The gateway and local package are not identical in their advertised tool lists: the gateway adds shared Pipeworx meta-tools, while the local server does not. The gateway documentation also notes that the exact hosted scope can change, so the connection's initialize response is the authoritative source for that session.