mcpField
T
tell: buying signals with receipts

tell: buying signals with receipts

Local
github.comBusiness & Marketing0Updated 1w ago
RepositoryVisit website

About tell: buying signals with receipts

tell-mcp lets MCP clients query tell’s buying-signal data to identify accounts showing market interest and inspect the evidence. Each signal includes a receipt URL, such as a job posting, SEC Form D filing, or news item.

Key features

  1. 01Find accounts currently in market
  2. 02Explain signals with receipt URLs
  3. 03List scored events by domain
  4. 04Check monitoring coverage
  5. 05Draft a sourced why-now email prompt

Use cases

  1. 01Prioritize accounts for sales outreach
  2. 02Review evidence behind an account signal
  3. 03Check whether a domain is monitored

MCP support

Exposes tell’s buying-signal data and related tools to MCP clients. It runs locally over stdio and reads public static JSON, or can use the FastAPI service when its API settings are configured.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "karank2512-tell": {
      "command": "uvx",
      "args": [
        "tell-mcp"
      ],
      "env": {
        "TELL_BASE_URL": "<TELL_BASE_URL>",
        "TELL_API_KEY": "<TELL_API_KEY>",
        "TELL_API_URL": "<TELL_API_URL>"
      }
    }
  }
}
Run commanduvx tell-mcp
Environment variables to set
TELL_BASE_URLRoot of the static site tell-mcp reads; a fork's own GitHub Pages URL works too.
TELL_API_KEYSecretOptional Bearer key for tell's v1 API (not deployed yet). Used only together with TELL_API_URL.
TELL_API_URLOptional base URL of tell's v1 API (not deployed yet). Used only together with TELL_API_KEY.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypitell-mcp0.1.0

Tools

5

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
domainsarrayYes
watchliststringYes

Details

From the project README

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

ToolInputOutput
watch_accountsdomains, watchlistv0: the intake form link prefilled with the domains; the watchlist appears after the nightly job
in_marketwatchlist, since_days (7), min_score (6.0), families[{domain, name, score, heat, top_contributions[:3]}], highest score first
explaindomainEvery contribution with its receipt URL, plus "why not higher" (signals that decayed in the last 30 days)
eventsdomain, since, typesContributions and counted postings, newest first, at most 200, each with a URL
coveragedomainsPer domain: job board, SEC CIK, news feed, or "not monitored"

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

VariableDefaultMeaning
TELL_BASE_URLhttps://karank2512.github.io/tell-dataThe static site to read
TELL_API_KEY, TELL_API_URLunsetBoth set: read companies and watchlists from the FastAPI service with a Bearer key
TELL_INTAKE_FORM_URLunsetIntake form for watch_accounts (default: the repo's "Watch these domains" issue form)

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.