Track what 1,000+ VCs follow on X to surface startups before their round. Signal for AI agents.
VC follow intelligence for AI agents. Track what top investors follow on X — detect new follows, convergence signals, and trending companies before they're announced.
33 tools. Version 2.5.2.
No API key needed. Log in with your frontrun.vc account:
# Step 1: Log in — opens browser, saves credentials locally
npx frontrun-mcp-server --login
# Step 2: Auto-configure your client
npx frontrun-mcp-server --setup # Claude Desktop
npx frontrun-mcp-server --setup-code # Claude Code (uses `claude mcp add`)
Credentials are saved to ~/.frontrun/credentials.json. Other commands:
npx frontrun-mcp-server --status # Check auth status
npx frontrun-mcp-server --logout # Clear saved credentials
The server is also hosted at https://www.frontrun.vc/mcp (streamable HTTP). Point any
remote-capable MCP client at it with your API key:
claude mcp add --transport http frontrun https://www.frontrun.vc/mcp --header "Authorization: Bearer sig_your_key_here"
If you prefer to use an API key directly, go to frontrun.vc → Settings > API Keys and generate a key (starts with sig_).
claude mcp add frontrun -e FRONTRUN_API_KEY=sig_your_key_here --scope user -- npx frontrun-mcp-server
Or add to .mcp.json in any project:
{
"mcpServers": {
"frontrun": {
"command": "npx",
"args": ["frontrun-mcp-server"],
"env": {
"FRONTRUN_API_KEY": "sig_your_key_here"
}
}
}
}
Add to your config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"frontrun": {
"command": "npx",
"args": ["frontrun-mcp-server"],
"env": {
"FRONTRUN_API_KEY": "sig_your_key_here"
}
}
}
}
Add to .cursor/mcp.json in your project:
{
"mcpServers": {
"frontrun": {
"command": "npx",
"args": ["frontrun-mcp-server"],
"env": {
"FRONTRUN_API_KEY": "sig_your_key_here"
}
}
}
}
FRONTRUN_API_KEY=sig_your_key_here npx frontrun-mcp-server
Open your AI tool and try:
"What's trending in my tracked accounts this week?"
Here are real prompts that work out of the box. Just type them into Claude Code, Claude Desktop, or Cursor.
Frontrun monitors the X (Twitter) follow graphs of VCs and investors you choose to track. When a VC follows a new account, Frontrun detects it, classifies the entity (startup, protocol, founder, etc.), and makes it queryable through AI.
The signal: VCs typically follow companies 2-8 weeks before a funding announcement. Convergence — multiple VCs independently following the same account — is the strongest signal.
Receipts: @techdollarhq flagged at 13 followers, $3M pre-seed announced 123 days later · @orthogonal_sh flagged 184 days before its $4.3M round led by Pantera · @rialto_xyz flagged at 18 followers, 26 days before its Robinhood partner announcement.
What you're paying for: Every response is computed intelligence, not raw data. Sectors are classified by AI, convergence is detected algorithmically, and company profiles are synthesized from multiple sources.
API + MCP access is included with the Pro plan ($99/mo) — it comes with 10,000 credits every month, and you can add more (or turn on auto-refill) at frontrun.vc/api/billing. Each query costs credits:
| What you're doing | Credits |
|---|---|
| Check your balance, list tracked accounts, manage rules/tags | Free |
| Preview an account, search, view sectors, pull a report | 4 |
| New follows, enriched follows, feed, company signals | 16 |
| Trending scan, VC activity | 24 |
| Thesis search, webhook setup (then 8/delivery) | 40 |
| Company deep-dive: overview, funding, convergence, resources, discover, similar VCs | 60 |
| Founder intelligence | 100 |
A typical daily check-in (feed + convergence + a few company deep-dives) runs ~300 credits — an included month covers it more than 30x over. Agent-scale usage is what auto-refill is for.
The agent has access to these tools automatically. You don't need to call them by name — just ask your question and the agent picks the right tool.
| Tool | What it does |
|---|---|
frontrun_status | Your balance, tracked count, usage stats |
frontrun_list_tracked | All accounts you're monitoring |
frontrun_track | Start monitoring an X account |
frontrun_untrack | Stop monitoring an account |
frontrun_preview | Preview an account before tracking — signal score, sector hints, recommendation |
| Tool | What it does |
|---|---|
frontrun_new_follows | New follows detected across your tracked accounts |
frontrun_snapshot | Current follow list for a specific tracked account |
frontrun_enriched_follows | New follows + AI classification + custom rules applied |
frontrun_convergence | Multiple tracked accounts following the same entity |
frontrun_trending | Entities ranked by follow velocity |
frontrun_search | Search discovered entities by sector, keyword, type |
frontrun_thesis_search | Semantic search — describe a thesis in plain language, get matching companies |
frontrun_feed | Real-time activity feed across all tracked accounts |
frontrun_sectors | Sector breakdown of discovered entities |
frontrun_discover | Personalized recommendations — "accounts your VCs follow that you're not tracking" |
frontrun_reports | Generated intelligence reports for your tracked accounts |
| Tool | What it does |
|---|---|
frontrun_company | Company overview — what they do, sector, stage |
frontrun_company_founders | Founder profiles, backgrounds, previous companies |
frontrun_company_signals | Social buzz, sentiment, notable engagements |
frontrun_company_resources | Website, GitHub, docs, community links |
frontrun_company_funding | Funding rounds, investors, amounts |
| Tool | What it does |
|---|---|
frontrun_vc_activity | VC follow patterns — velocity, sector focus, recent follows |
frontrun_vc_similar | Find VCs with overlapping follow patterns |
| Tool | What it does |
|---|---|
frontrun_classify | Run AI classification on specific entities |
frontrun_create_rule | Create a custom classification rule |
frontrun_list_rules | List your rules |
frontrun_update_rule | Update a rule |
frontrun_delete_rule | Delete a rule |
frontrun_tag | Tag an entity with custom labels |
frontrun_list_tags | List your tagged entities |
| Tool | What it does |
|---|---|
frontrun_list_webhooks | List your registered webhooks |
frontrun_create_webhook | Register a webhook for new_follows / convergence events |
frontrun_delete_webhook | Delete a webhook |
Prefer HTTP? Every tool maps to a REST endpoint. Base URL: https://frontrun.vc/v1
# Set your key
export FR_KEY="sig_your_key_here"
# Check your account
curl -sL -H "X-API-Key: $FR_KEY" "https://frontrun.vc/v1/status"
# What's trending?
curl -sL -H "X-API-Key: $FR_KEY" "https://frontrun.vc/v1/trending?since=168h"
# Convergence signals
curl -sL -H "X-API-Key: $FR_KEY" "https://frontrun.vc/v1/convergence?since=168h"
Full REST docs: frontrun.vc/docs/api
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y frontrun-mcp-serverMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-jongall45-frontrun-mcp-server": {
"command": "npx",
"args": [
"-y",
"frontrun-mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencefrontrun-mcp-servernpmio.github.jongall45/frontrun-mcp-server works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.