← tickerbot.io
View as markdown
Getting started

MCP

The same API, as tools. Every call an agent should make is an MCP tool with the same name, params, and shape, so an agent in Claude, ChatGPT, Cursor, or any MCP runtime queries the table directly. Install it below.

Pick your AI tool

One server, one URL: https://api.tickerbot.io/mcp. Every client takes it and signs you in with OAuth in the browser, which creates your free account if you don't have one. No key to copy. A coding agent can do the whole thing itself from the setup prompt.

Any coding agent

Claude Code, Cursor, Codex. Paste one line in the chat; the agent adds the server, waits for you to sign in, and verifies with three reads.

Claude Code

One command. Signs you in with OAuth in the browser. No key to copy.

Claude.ai (web + mobile + desktop)

Paste Tickerbot’s MCP URL as a custom connector. OAuth handles the rest. Install once on web or desktop. Mobile inherits the connector automatically.

ChatGPT Plugin

Add Tickerbot as a plugin in ChatGPT. OAuth handles the rest.

Cursor

JSON config. Paste into ~/.cursor/mcp.json, reload, sign in when Cursor prompts.

VS Code (Copilot)

JSON config. Workspace or user file. Sign in when VS Code prompts.

Windsurf

JSON config. Single MCP file (Windsurf spells the key serverUrl). Sign in when Windsurf prompts.

Zed

JSON config under the context-servers section of settings. Local server with a key; Zed has no remote OAuth.

View the mcp-server source on GitHub →

Without OAuth

For a client that can't sign in through the browser, run the server locally with an API key instead. Same tools. A key is free, no card: tickerbot.io/dashboard/keys.

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

Claude Code equivalent: claude mcp add tickerbot --env TICKERBOT_API_KEY=tb_live_... -- npx -y @tickerbot/mcp-server. VS Code uses the key servers, Zed context_servers (the Zed card above carries that shape).

Not on MCP?

The live tool catalog is GET https://api.tickerbot.io/mcp/tools — the same array the server serves, with each tool’s JSON Schema and the endpoint it maps to, ready to drop into any function-calling runtime. The REST surface behind every tool is at /openapi.yaml.

32 tools

One for every call an agent should make; each maps to one REST endpoint with the same name, params, and shape.

FamilyTools
Tickers
tickerbot_list_tickerstickerbot_get_tickertickerbot_subscribe_tickertickerbot_get_ticker_coverage
Signals
tickerbot_list_signalstickerbot_create_custom_signaltickerbot_update_custom_signaltickerbot_delete_custom_signaltickerbot_get_signaltickerbot_subscribe_signal
Scan
tickerbot_scantickerbot_subscribe_scan
Series
tickerbot_get_series
Bars
tickerbot_get_bars
Events
tickerbot_list_eventstickerbot_subscribe_events
News
tickerbot_search_news
ETF
tickerbot_get_etf_holdingstickerbot_get_etf_sectors
Universes
tickerbot_list_universestickerbot_create_universetickerbot_get_universetickerbot_update_universetickerbot_delete_universe
Webhooks
tickerbot_list_webhookstickerbot_create_webhooktickerbot_get_webhooktickerbot_update_webhooktickerbot_delete_webhooktickerbot_list_webhook_deliveriestickerbot_enable_webhooktickerbot_test_webhook