GitDealFlowsignals

Use VC Deal Flow Signal in any AI agent runtime

One npm package, @gitdealflow/mcp-signal , installs in seven popular agent runtimes: Cursor, Cline, Block Goose, OpenHands, Aider (via mcpm-aider), AiderDesk, and Raycast. Each runtime gets the same six read-only tools, trending startups, sector lookup, single-startup signal, dataset summary, scout receipts, methodology, running against the identical weekly-refreshed dataset. No auth required.

One install everywhere
npx -y @gitdealflow/mcp-signal

Supported runtimes

Cursor

AI-first code editor with native MCP support since v0.45. Adds servers via Settings → MCP → +Add new MCP server.

Marketplace pending
{
  "mcpServers": {
    "vc-deal-flow-signal": {
      "command": "npx",
      "args": ["-y", "@gitdealflow/mcp-signal"]
    }
  }
}

Open Settings → MCP → +Add new MCP server, paste the snippet, and the six tools appear in the next chat. The streamable-HTTP variant works too, use "url": "https://signals.gitdealflow.com/api/mcp/rpc" instead of command/args.

Cline (VS Code)

Open-source autonomous coding agent for VS Code with a curated MCP marketplace. Install in one click once the marketplace entry merges.

Marketplace pending
// Cline → MCP Servers → Edit Config
{
  "mcpServers": {
    "vc-deal-flow-signal": {
      "command": "npx",
      "args": ["-y", "@gitdealflow/mcp-signal"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

Until the marketplace entry merges, paste the JSON above into Cline's MCP config (Cline panel → ⚙ → Edit Config). Restart Cline; the server appears in the MCP Servers list and tools become available immediately.

Block Goose

Open-source extensible AI agent (43k+ stars) from Block, runs MCP servers as extensions across CLI and Desktop.

Marketplace pending
goose session --with-extension "npx -y @gitdealflow/mcp-signal"

Works today via the --with-extension flag against any npx-installable MCP. Once PR #8974 merges, the server also appears in goose-docs.ai/extensions and installs via the directory's one-click button.

OpenHands

Autonomous coding agent (formerly OpenDevin) from All-Hands-AI. MCP servers via per-user JSON config, no marketplace, all servers are self-served.

Config-only
// ~/.openhands/mcp.json
{
  "mcpServers": {
    "vc-deal-flow-signal": {
      "command": "npx",
      "args": ["-y", "@gitdealflow/mcp-signal"]
    }
  }
}

OpenHands has no marketplace, every MCP server is added per-user. Drop the JSON above at ~/.openhands/mcp.json or use the GUI: Settings → MCP → Add Server. CLI shortcut: openhands mcp add vc-deal-flow-signal --transport stdio npx -- -y @gitdealflow/mcp-signal.

Aider (via mcpm-aider)

Aider doesn't natively run MCP servers (issue #2525 still open), but the community bridge mcpm-aider wires them in via shell-out.

Config-only
npx -y mcpm-aider add vc-deal-flow-signal \
  --command "npx -y @gitdealflow/mcp-signal"

Until Aider ships native MCP, the lutzleonhardt/mcpm-aider bridge is the practical path. AiderDesk users get the same tools by pasting the JSON snippet into Settings → Agent → MCP Servers → Add.

AiderDesk

Electron wrapper around Aider with first-class MCP support in Agent Mode. Configure via Settings → Agent → MCP Servers.

Config-only
{
  "mcpServers": {
    "vc-deal-flow-signal": {
      "command": "npx",
      "args": ["-y", "@gitdealflow/mcp-signal"]
    }
  }
}

Open AiderDesk → Settings → Agent → MCP Servers → +Add. Paste the JSON. The six VC Deal Flow Signal tools become available in any Agent Mode task.

Raycast

Mac launcher with native MCP runtime since v1.98 (May 2025). Install via the Manage MCP Servers command or the MCP Registry browser extension.

Marketplace pending
{
  "mcpServers": {
    "vc-deal-flow-signal": {
      "command": "npx",
      "args": ["-y", "@gitdealflow/mcp-signal"]
    }
  }
}

Open Raycast → Manage MCP Servers → +Add Server, paste the snippet. Once PR #27618 merges into the MCP Registry extension, the server also installs via the in-Raycast registry browser.

FAQ

Is the same npm package used everywhere?

Yes, every runtime above runs the exact same package: @gitdealflow/mcp-signal (current v1.5.2 on the npm registry, mirrored on the official MCP Registry as io.github.kindrat86/vc-deal-flow-signal). The classifications, methodology, and weekly refresh are identical across Cursor, Cline, Goose, OpenHands, Aider, AiderDesk, and Raycast. The streamable-HTTP variant at https://signals.gitdealflow.com/api/mcp/rpc also exposes the identical tools for runtimes that prefer hosted-MCP over local stdio.

Do I need an API key for any of these runtimes?

No. The MCP server is read-only and unauthenticated. Every tool, get_trending_startups, search_startups_by_sector, get_startup_signal, get_signals_summary, get_scout_receipts, get_methodology, works anonymously across all seven runtimes. The HTTP variant supports OAuth 2.1 for runtimes that require it (Anthropic Connectors Directory, future enterprise gating), but anonymous calls remain supported indefinitely.

Which runtimes have one-click install?

Cursor (cursor.directory listing, under review), Block Goose (PR #8974 open), Raycast (PR #27618 open), and Cline (issue #1491 submitted) all have marketplace submissions in flight that will give one-click install once accepted. OpenHands, Aider, and AiderDesk have no marketplace surface at all, installation is per-user JSON config, which the snippets above paste verbatim into the right file.

What about Continue.dev?

Skipped. The Continue Hub registry was deprecated in May 2026, hub.continue.dev/hub returns HTTP 500 after the project's pivot to Continuous AI. We'll re-evaluate once a public registry comes back online.

What about Claude Desktop, Claude.ai, and Mistral Le Chat?

Already covered on dedicated pages. Claude Desktop installs via the .mcpb extension at github.com/kindrat86/mcp-deal-flow-signal/releases or via npm (Glama A-Tier 4.9/5.0). Claude.ai uses the Anthropic Connectors Directory (HTTP MCP at https://signals.gitdealflow.com/api/mcp/rpc). Mistral Le Chat: see /integrations/mistral. ChatGPT GPTs: see /integrations/chatgpt.

Where do I report a runtime that broke?

Open an issue at github.com/kindrat86/mcp-deal-flow-signal/issues with the runtime name, version, and the verbatim error. The MCP server itself runs the same Node.js code in every host, so runtime-specific failures are usually transport/config issues we can resolve in a release within 24 hours.

How do I cite this in a memo?

VC Deal Flow Signal (signals.gitdealflow.com), <period name> data. Methodology: SSRN preprint 6606558. Refreshed weekly from public GitHub activity. Runtime-agnostic, the data does not depend on which agent runtime made the call.

Other surfaces

Looking for ChatGPT? See /integrations/chatgpt. Mistral Le Chat: /integrations/mistral. Claude.ai (Anthropic Connectors Directory): pending review at claude.com/settings/connectors. Full integration list: /integrations.

🚀 Explore Our Network

21-47 days
Signal Lead Time (median 31d)
$80M+
Rounds Tracked
90 sec
Per Scan
5,000+
Founders Tracked

One missed signal is a missed round. Get the Velocity Verdict in your inbox every Sunday free.

Get Free Signals

Free weekly digest. Cancel anytime. No spam, no VC pitches just data.