A2A INTEGRATION · MCP-NATIVE

Use GitDealFlow A2A with Continue

Open-source IDE assistant for VS Code and JetBrains. Developer-investors using a self-hosted or BYOK alternative to Cursor.

Crunchbase API: $20K/yr. GitDealFlow A2A: free, no signup.

Continue supports MCP servers natively via its config.yaml. Add our server once and every Continue chat can pull engineering signals while you read code. The A2A endpoint is useful when you want a one-shot inline edit ('explain this commit pattern in context of the broader sector') without leaving the editor.

Endpoint facts for Continue users

Whatever wiring you choose, the target is the same single endpoint. These are the fixed facts; nothing on this page changes them:

Protocol	A2A JSON-RPC 2.0 (protocolVersion 0.3.0)
Endpoint URL	`https://signals.gitdealflow.com/api/a2a`
Skills exposed	5, mirrored 1:1 with the MCP server tools (trending, sector, lookup, summary, methodology)
Auth	None; free in perpetuity, read-only
Freshness	Recomputed weekly; responses carry the data-as-of date
Best Continue path	Continue speaks MCP natively, so the MCP server is the shortest path (below); raw A2A remains available for sub-agents and curl.

MCP server in config.yaml

# ~/.continue/config.yaml (Continue v1.0+)
mcpServers:
  - name: gitdealflow
    command: npx
    args:
      - "@gitdealflow/mcp-signal@latest"

# Reload Continue, then in chat:
#   "Use gitdealflow to find AI/ML breakouts this week"
#   "What does breakout signal mean?"

Custom slash command via A2A

# ~/.continue/config.yaml
slashCommands:
  - name: signal
    description: "Look up engineering signal for the current repo"
    prompt: |
      Run this curl and summarize the result for the user:
      curl -X POST https://signals.gitdealflow.com/api/a2a \\
        -H 'Content-Type: application/json' \\
        -d '{"jsonrpc":"2.0","id":1,"method":"message/send","params":{"message":{"role":"user","parts":[{"kind":"text","text":"signal {{{ input }}}"}]}}}'

What you can ask

While reviewing a PR: 'is this commit cadence unusual for this org?'
When opening a new repo: 'what's the engineering signal on this org?'
In a code-review chat: 'show me ai-ml breakouts that ship at this velocity.'
Before a meeting: 'pull last week's trending in fintech.'

Gotchas

Continue caches MCP responses per chat session, start a fresh chat after Monday's data refresh if you want the latest.
On Windows, use the absolute path to npx in the command field; PATH resolution from the IDE process is flaky.

When to pick which path

Because Continue supports MCP natively, the split is simple: use the MCP server for anything you want persistent and always-available (it reconnects, caches, and shows up as first-class tools), and the raw A2A endpoint for one-off curls, sub-agents without MCP access, or quick tests from CI.

4example prompts are listed under "What you can ask" below, and the gotchas section covers the 2 known failure modes Continue users hit with this endpoint. If a prompt fails, check the gotchas first: most misses are shape mismatches, not endpoint outages.

References

Try it without setup

The interactive playground lets you send live JSON-RPC requests against the A2A endpoint with no install, no auth. Pick a skill, hit send, see the response.

Full launch story: I made my VC deal flow callable by Claude.