Jipup CRM workflows · MCP server
MCP server Model Context Protocol · HTTP

The B2B data MCP server: your agent writes the message, Jipup tells it who to send it to.

Twelve revenue data tools, plugged into Claude, Cursor, n8n or the agent you built yourself. Your teams describe what they need in plain English, the agent calls the tools, and you only pay for what is found.

claude · jipup (mcp)
you

→ find_companies saas · united states · 50-200 employees 40 accounts
→ find_people title ≈ "vp sales" across 40 accounts 38 people
→ find_linkedin_profile 38 identities 36 URLs
→ scrape_linkedin_profile 36 URLs · title, tenure, experience 36 profiles
→ enrich_email 36 contacts · verification included 29 emails
29 contacts ready · 7 without email · 0 credits charged for those One sentence in plain English, five tool calls, zero exports.
Works with
Claude Codex Cursor Hermes-Agent OpenClaw
...and any client that speaks MCP.
What breaks today

Agents don't get stuck on reasoning. They get stuck on data.

Your teams already know how to write the prompt that segments, prioritizes and drafts. The chain always breaks at the same point: when it is time to fetch a fact about a real person, the model has nothing to work with.

01

It makes up the email

With no source, a model outputs firstname.lastname@domain.com and lets you find out the bounce rate mid-campaign. A plausible pattern is not a verified address.

The cost: your sender reputation.
02

It can't read LinkedIn

A browser driven by the agent gets blocked within a few dozen pages, and job title, tenure and headcount are exactly the data that decides who you target.

The cost: the automation never gets past the demo.
03

It makes you stack subscriptions

One provider for email, another for mobile, a third for scraping: three API keys, three invoices, and coverage that stays partial on each of them. How the provider cascade enriches your CRM →

The cost: three licenses for one use case.
The server

Twelve tools, five verbs.

Each tool does one thing and returns a structured result, not a sentence. The agent reads their descriptions and picks which ones to call and in what order: no chain to wire up, no schema to write.

Identify

Find the right page from what you already have.
find_linkedin_profile

A first name, a last name and a company, and you get back the matching LinkedIn profile URL, with a confidence score when several people share the same name.

In
first name, last name, company or domain
Out
linkedin_url, confidence
Sources
find_linkedin_company

A company name or a domain, and you have the company page. It is the key that then unlocks headcount, industry and the right people to talk to.

In
company name or domain
Out
linkedin_company_url, normalized name
Sources

Read

What is published on the day of the call, not last year's cache.
scrape_linkedin_profile

The full profile: current role, tenure, experience, location, education. Enough to decide whether the person is in your target before you write a word.

In
linkedin_url
Out
title, company, tenure, experience, location
Sources
scrape_linkedin_company

The company profile: actual headcount, industry, headquarters, description, hiring pace. The context that tells a target account apart from a company with the same name.

In
linkedin_company_url or domain
Out
headcount, industry, headquarters, website, description
Sources
enrich_legal

Official legal data for companies registered in France: SIREN, SIRET, NAF industry code, legal form, officers, incorporation date. Pulled from the public French registry, 1 credit when found.

In
company name, domain or SIREN
Out
siren, siret, naf, legal form, officers, incorporation
Source
detect_job_change

Compares what you know about a contact with what is published today, and flags both the departure and the arrival: previous company, new company, new title, estimated date. The buying signals you can draw from it →

In
identity + known company (or linkedin_url)
Out
status, previous and new company, new title, date
Chain

Reach

A cascade of providers behind every call, until something is found.
enrich_email

The work email, verified before it is returned. Providers are queried one after another until the address is found, and you only see a single call.

In
identity + company or linkedin_url
Out
email, verification status, source
Sources +10
enrich_phone

The direct mobile number, in international format. It is the scarcest data on the market: the tool tells you plainly when it exists nowhere instead of handing you the switchboard.

In
identity + company or linkedin_url
Out
mobile (E.164), line type
Sources +10

Recognize

The reverse path: from a bare identifier to a person.
reverse_email

An address on its own, and you know who is on the other end: identity, company, title, LinkedIn profile. For sequence replies, sign-ups and export rows where only an email is left.

In
email
Out
identity, company, title, linkedin_url
Sources +10
reverse_phone

A number on its own, and you know who called. For missed calls, half-filled forms and databases where the phone number outlived everything else.

In
phone (E.164)
Out
identity, company, title
Sources +10

Search

When you don't have a list yet, only criteria.
find_people

Criteria instead of a list: job title, seniority, department, country, company size. You get back identities ready to go through the enrichment tools.

In
title, seniority, department, country, headcount, target accounts
Out
identities, company, title, linkedin_url
Source
find_companies

The same idea at account level: industry, headcount, country, tech stack, hiring pace. Enough to sketch an ICP in one sentence and refine it in the next.

In
industry, headcount, country, technologies, keywords
Out
companies, domain, headcount, linkedin_company_url
Sources
Setup

Three minutes, one key, nothing to install.

The server is remote: nothing to run on your side, nothing to update. Your MCP client connects to it over HTTP with your key and discovers the twelve tools on its own.

  1. 01

    Create a key in your Jipup workspace

    It draws on your workspace credits. You can create one per tool or per team, and revoke one without breaking anything else.

  2. 02

    Add the server to your client

    From the command line:

    # Claude Code, Codex, Cursor, Hermes-Agent, OpenClaw... claude mcp add --transport http jipup https://app.jipup.com/api/mcp \ --header "Authorization: Bearer jipup_••••••••"

    Or in the configuration file:

    { "mcpServers": { "jipup": { "url": "https://app.jipup.com/api/mcp", "headers": { "Authorization": "Bearer jipup_••••••••" } } } }
    http transport sse 12 tools one key per workspace call log
  3. 03

    Ask in plain English

    Nothing left to wire up: the agent reads the tool descriptions, picks which ones to call and in what order, chains the results and hands you the list. Your teams write a sentence, not a pipeline.

In the field

What your teams build with a single sentence.

GrowthBuild the list

"Give me 200 US SaaS companies with 50 to 200 employees, the VP of Sales at each one, their LinkedIn and their work email."

  • find_companies
  • find_people
  • find_linkedin_profile
  • enrich_email
A list ready to sequence, without a single export.
SalesKnow who you're talking to

"This number called during my meeting and this address just replied to the sequence: who are these two people?"

  • reverse_phone
  • reverse_email
  • scrape_linkedin_profile
The context before you call back, not after.
MarketingWake up the database

"Out of my 3,000 contacts, pull the ones who changed companies this quarter and find their new email."

  • detect_job_change
  • scrape_linkedin_company
  • enrich_email
An audience to reactivate, with dead addresses filtered out.
What it costs

A call that finds nothing costs nothing.

MCP calls use the same credits as your Jipup agents, billed on results. A profile that can't be found, a mobile that exists nowhere, an address nobody publishes: none of it is charged, so an agent that fumbles around won't drain your balance. The one exception is the job-change scan, billed per scan. A credit costs €0.0120 down to €0.0090 excl. VAT, depending on your plan.

5work email
50direct mobile number
1contact enriched from LinkedIn
3LinkedIn URL found for a contact
1company enriched from LinkedIn
8identity from an email
3job-change scan
1French legal data

Prices in credits, per result found (the job-change scan is per scan; a contact's LinkedIn URL is only searched for once). Unused credits roll over. See every plan and the full rate card →

A cascade, not a single provider

Behind each tool, 15+ data providers are queried in order until something is found. No Kaspr, Lusha or Apollo license to pay for on your side.

The same engines as the workflows

What your agent calls over MCP is exactly what the Jipup workflows (Duplicate detection and merging, CRM enrichment, Job change tracking and New hire detection) write into your CRM. Same data, same cascade, same billing.

Every call is traceable

Each call is logged in your workspace: which tool, which input, which result, what it cost. An agent going off the rails shows up right away.

Your lists stay yours

What you send to the server is used to answer your call, not to feed a shared dataset. Hosted in Europe, with contractually bound subprocessors.

Get started

Create the key, paste the line, ask your question.

12tools available from the first call
250free credits, no credit card
0provider subscriptions to take out

The MCP server is included in your Jipup workspace: the key is available as soon as you create your account, and the credits are the same ones your CRM agents use, alongside the native integration with HubSpot and Salesforce (OAuth connection to your CRM →). Plans start at €120 a month (about $139) for 10,000 credits, with no commitment. Compare plans and pricing →

Start for free 250 free credits, no credit card. Or book a demo and we'll connect it together.