Signalbase + Claude Code integration

Signalbase runs as an MCP server, which means Claude Code can query live company signals the same way it reads your codebase. Ask for funded companies in your market, companies hiring for a specific role, or executives who just changed jobs, and Claude pulls verified signals with sources attached and works with them directly: filtering, cross-referencing, writing them to a file, or feeding them into whatever you are building.

No SDK, no wrapper, no glue code. One config block and the signals are available as a tool.

What you can do

  • Build a prospect list in one prompt. "Find companies that raised Series A in the Netherlands in the last 30 days and are hiring engineers" returns a filtered, sourced list you can write straight to CSV.

  • Qualify an existing list. Point Claude at a file of domains and have it check each one against live signals, so you know which accounts have something happening right now.

  • Cross-reference signals. Funding plus hiring plus a new executive is a much stronger trigger than any one alone. Claude can chain those queries in a single session.

  • Monitor a market overnight. Give Claude a niche and a schedule, and have it report what changed since yesterday.

Setup

  1. 1
    Get your API key from the Signalbase dashboard.
  2. 2
    Select where you want your live data:

    Run this in your terminal:

    claude mcp add signalbase \
      --transport http \
      --url https://mcp.trysignalbase.com \
      --header "Authorization: Bearer YOUR_API_KEY"
  3. 3
    Restart your client. The Signalbase tools appear automatically, so you can ask for signals in plain language.

Example

You

Find companies in fintech that raised in the last two weeks and are hiring senior engineers. Give me the decision makers.

Claude Code

Queries funding signals, filters by sector and date, cross-references hiring signals, pulls people-level data. Returns a table of companies with round type, amount, investors, open roles, named decision-makers, and the source URL for every signal.

Want to see this run for real? Tanay Mishra built a signal-based prospecting list this way: 25 funded companies pulled, 11 qualified, 4 minutes of runtime, no code written. Read the guide →

How teams use it

Sales

A prospect list with real triggers, built and qualified in one session instead of an afternoon of tabs.

GTM engineering

The signal layer under agent workflows, queried directly instead of through a wrapper you maintain.

Market research

Cross-referenced funding, hiring and leadership moves across a niche, written to a file you can keep.

Alerts and monitoring

A scheduled session that reports what changed in your market since yesterday, with sources.

Signals available through the MCP

Fundinground type, amount, currency, announced date, investors with lead flags, sources
M&Aacquirer, target, deal type, amount, percentage, date, sources
Job changesperson, previous and new role, company, seniority, department
Hiringopen roles, seniority, department, full job description, source
Company profilesindustry, HQ, employee count, LinkedIn URL, decision-makers
Investorstype, geography, ticket size, portfolio

Want the full MCP reference? Tool schemas, transport details and every client config live on the MCP server page →

MCP access included

Ask for signals in plain language

Every plan includes the MCP server alongside the API and webhooks, so Claude Code is two minutes from your first query.

Tested by 700+ GTM teams · 500 trial credits included

Claude Code integration FAQ

Model Context Protocol is an open standard that lets AI assistants connect to external tools and data sources. Signalbase runs as an MCP server, so any MCP-compatible client can query it directly.