tell-mcp

MCP server for tell, the open-source buying-signals pipeline. It lets Claude Desktop, Cursor or any MCP client ask which accounts are in market and why, with a receipt URL behind every signal (a job board, an SEC Form D filing, a news item). It runs locally over stdio and reads tell's public static JSON: no key, no account.

Quickstart

uvx tell-mcp --help

Claude Desktop (claude_desktop_config.json) or Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "tell": {
      "command": "uvx",
      "args": ["tell-mcp"],
      "env": { "TELL_BASE_URL": "https://karank2512.github.io/tell-data" }
    }
  }
}

Restart the app and ask: "Which of these ten domains are in market and why?"

Tools

Prompt why_now_email(domain): the two-sentence "why now" for an outreach email, built from the top two signals with their receipt URLs. Tool descriptions ask the agent to cite the url of every signal it mentions and to call explain before writing outreach copy.

Configuration

v0 limitations

• watch_accounts returns a prefilled link; it does not create the watchlist.
• in_market reads public watchlists only (api/v0/watchlists/{slug}.json).
• events has no raw event endpoint to read: it lists the scored contributions and the counted postings behind them.
• Data refreshes with each ingest run (four a day); a domain quiet for 180 days has no file and reads as "not monitored".

When the FastAPI service is deployed, setting TELL_API_KEY and TELL_API_URL switches company and watchlist reads to it without any other change.

Full docs: docs/mcp.md. License: Apache-2.0.