A2A INTEGRATION · MCP-NATIVE

Use GitDealFlow A2A with Cline

Autonomous Claude agent for VS Code. Developer-investors who let an agent run multi-step workflows in their editor.

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

Cline has native MCP support via its MCP servers settings panel. Add our package and Cline can autonomously chain a research step ('check engineering signals for this org') with a downstream action ('open a Linear ticket if breakout'). The A2A endpoint is the cleaner path when you want Cline to call us inside a single Bash step without MCP context overhead.

Endpoint facts for Cline 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 Cline path	Cline speaks MCP natively, so the MCP server is the shortest path (below); raw A2A remains available for sub-agents and curl.

MCP server (Cline UI)

// In VS Code: Cline panel → MCP Servers → Edit Config
// Or directly edit ~/Documents/Cline/MCP/cline_mcp_settings.json:
{
  "mcpServers": {
    "gitdealflow": {
      "command": "npx",
      "args": ["@gitdealflow/mcp-signal@latest"],
      "disabled": false
    }
  }
}

// Then in Cline chat:
//   "Pull trending ai-ml startups, then for the top 3 open a Linear issue
//    titled 'Diligence: <name>' with the signal data in the description."

A2A from Cline's Bash tool

// Ask Cline:
// "Use the bash tool to call https://signals.gitdealflow.com/api/a2a with body
//  {jsonrpc:'2.0',id:1,method:'message/send',params:{message:{role:'user',parts:[{kind:'text',text:'trending'}]}}}
//  then summarize."

// Cline will execute and structure the response in its plan view.

What you can ask

'Pull trending fintech, then open a Linear ticket for each.'
'Check signal on each org I have starred this month and write a markdown summary to ~/notes.'
'Watch the next breakout and email me when commit_velocity_change exceeds 200%.' (Cline will set up a cron via crontab.)
'Compare three orgs and explain the engineering tell.'

Gotchas

Cline runs in autonomous mode by default, review its plan view before approving multi-step workflows that include external API calls.
MCP server output is included in Cline's context window for every subsequent step; for big trending lists, ask Cline to summarize before chaining further.

When to pick which path

Because Cline 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 Cline 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.