Tickerbot in your AI tool.

what you’ll ask it

Every endpoint, addressable in chat.

Once installed, the SQL grammar Tickerbot speaks becomes something you describe in English. A few prompts that land out of the box:

• ›What’s NVDA up to?
• ›Find stocks gapping up with earnings this week.
• ›Replay yesterday: which megacaps hit a golden cross?
• ›Alert me when AAPL hits oversold.

tier 1 · marketplace

One-click from inside your chat app or IDE. Coming soon

The lowest-friction path. Open your chat app or IDE’s built-in connector library, find Tickerbot, click install. No URLs, no config files, no terminal.

tier 2 · desktop extension

Download an installer, double-click. Coming soon

Anthropic’s Desktop Extensions (.dxt) are the install-button experience for Claude Desktop — native install dialog, UI prompt for your API key, no config-file editing.

tier 3 · chat-app custom connector

Paste a URL and your API key into chat-app settings. Coming soon

For Claude.ai or ChatGPT power users on Pro / Team plans who don’t want to wait for marketplace approval. Paste https://api.tickerbot.io/mcp in your chat app’s custom-connector settings.

tier 4 · CLI command

One line in your terminal.

For terminal-native AI coding agents. Each tool exposes an mcp add command that wires Tickerbot in one step, no JSON editing.

claude mcp add tickerbot --env TICKERBOT_API_KEY=tb_live_... -- npx -y @tickerbot/mcp-server

tier 5 · JSON config

Edit a config file, paste the snippet, restart.

Universal install path for every MCP-aware desktop app and IDE. Same npx command everywhere — only the config file location changes.

~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
%APPDATA%\Claude\claude_desktop_config.json (Windows)

{
  "mcpServers": {
    "tickerbot": {
      "command": "npx",
      "args": ["-y", "@tickerbot/mcp-server"],
      "env": { "TICKERBOT_API_KEY": "tb_live_..." }
    }
  }
}

~/.cursor/mcp.json

{
  "mcpServers": {
    "tickerbot": {
      "command": "npx",
      "args": ["-y", "@tickerbot/mcp-server"],
      "env": { "TICKERBOT_API_KEY": "tb_live_..." }
    }
  }
}

.vscode/mcp.json (workspace) or ~/.config/Code/User/mcp.json (user)

{
  "servers": {
    "tickerbot": {
      "command": "npx",
      "args": ["-y", "@tickerbot/mcp-server"],
      "env": { "TICKERBOT_API_KEY": "tb_live_..." }
    }
  }
}

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "tickerbot": {
      "command": "npx",
      "args": ["-y", "@tickerbot/mcp-server"],
      "env": { "TICKERBOT_API_KEY": "tb_live_..." }
    }
  }
}

~/.config/zed/settings.json (under "context_servers")

{
  "context_servers": {
    "tickerbot": {
      "command": {
        "path": "npx",
        "args": ["-y", "@tickerbot/mcp-server"],
        "env": { "TICKERBOT_API_KEY": "tb_live_..." }
      }
    }
  }
}

tier 6 · BYO runtime

Writing your own agent loop?

If you’re building with LangChain, the Vercel AI SDK, the OpenAI SDK, the Anthropic SDK, or raw HTTP, you can skip MCP entirely. Drop the Tickerbot tool definitions into your runtime’s tool-use schema.

See /api/agents for the raw JSON: Claude tool-use shape, OpenAI function-calling shape, and MCP tools/list shape. Same tools, three formats. Pick the one your runtime expects.

polish layer · skills, gems, agents

Make the LLM smarter at using Tickerbot. Coming soon

Not an install path — these ride on top of the tool surface. Bundled instructions that teach the LLM the q-grammar, schema, and scan/replay/subscribe playbook so it picks the right tool every time. One playbook, different distribution per vendor.

the tool surface

19 tools cover every public endpoint.

Strategies are intentionally not exposed via MCP — see the REST API docs for those.

• tickerbot_scanRun a SQL WHERE against the live universe — or against a past day with `asof`.
• tickerbot_get_tickerFull current row for one ticker (or as of a past date).
• tickerbot_list_tickersWalk or bulk-lookup the ticker universe.
• tickerbot_get_ticker_historyThe full wide row for one ticker as of a past date.
• tickerbot_get_ticker_eventsSplits, dividends, analyst rating changes for one ticker.
• tickerbot_list_signals_catalogBuilt-in signals plus the caller’s custom signals.
• tickerbot_get_signals_matchTickers that match one signal (now or asof).
• tickerbot_get_signal_historyTime series of one signal for one ticker, at 1m/1h/1d/1w resolution.
• tickerbot_list_signal_eventsDiscrete firings of a boolean signal for one ticker.
• tickerbot_list_universesSaved ticker universes.
• tickerbot_get_universeOne universe by slug, including its ticker list.
• tickerbot_create_universeCreate a named ticker universe.
• tickerbot_create_custom_signalSave a SQL WHERE expression as a named custom signal.
• tickerbot_search_newsSearch the news archive (back to 2015) with SQL WHERE — title, source, sentiment, tickers, etc. Scale+ plan.
• tickerbot_subscribe_scanWebhook that fires when matches for a scan query change. Delivers to your https URL or in-app.
• tickerbot_subscribe_signalWebhook that fires when a signal turns true / crosses a threshold.
• tickerbot_subscribe_tickerWebhook that fires when one ticker matches a condition.
• tickerbot_list_webhooksList existing webhook subscriptions.
• tickerbot_delete_webhookRemove a webhook subscription by id.