start for free
start for free

Verified contact data in Cursor

Add the MoltSets MCP server from Cursor Settings or .cursor/mcp.json, sign in over OAuth, and Cursor’s agent can look up emails, mobiles and companies, and write MoltSets code against the real schemas.

add to .cursor/mcp.json

.cursor/mcp.json
{ "mcpServers": { "moltsets": { "url": "https://mcp.moltsets.com/mcp", "transport": "http" } } }
transport
HTTP
on first connect
Cursor asks for your Client ID and Client Secret

credentials never stored in the file

what it is

MoltSets in Cursor

Cursor’s agent uses MoltSets two ways. It can look up data for you: a work email, a mobile, the company behind an IP. And when it writes code that calls MoltSets, it reads the real tool schemas over the MCP server instead of guessing at endpoints and parameter names.

Add it from Cursor Settings → MCP or a .cursor/mcp.json file. Either way it signs in over OAuth, and calls run on your MoltSets plan.

What you can do

  • / 01Look up a work email, mobile or company from the chat
  • / 02Write MoltSets API calls with the right endpoints and fields
  • / 03Test a request against real data before you ship it
  • / 04Share the config with your repo, with no secrets in it
setup

Connect MoltSets to Cursor

  1. 01

    Create connector credentials

    Log in at app.moltsets.com, open Connectors and create a connector. You get a Client ID and a Client Secret.

  2. 02

    Add a server

    Open Cursor Settings → MCP and select Add new MCP server. Or skip to the file: add the config above to .cursor/mcp.json.

  3. 03

    Set the transport and URL

    Choose HTTP (or Streamable HTTP, depending on your version) and enter:

    https://mcp.moltsets.com/mcp
  4. 04

    Sign in over OAuth

    Cursor sees that the server needs authentication and asks for your Client ID and Client Secret.

  5. 05

    Approve the connection

    Approve access in the browser tab that opens. If MoltSets doesn’t appear, restart Cursor.

which tool

Ask with what you already have

Cursor’s agent picks the tool from what you ask, and uses the same tools when it writes code. I have X, I want Y covers every combination.

you have →you want ↓LinkedIn URLName + company domainEmail(s)Title, industry, locationWebsite visitor IP
Work email linkedin_to_business_email search_business_email_by_name · · ·
Best email (work, else personal) linkedin_to_best_email · · · ·
Mobile number linkedin_to_mobile_phone · · · ·
LinkedIn profile · · email_to_linkedin · ·
Send-safety grades · · validate_emails · ·
People list · · · search_people ·
Company list · · · search_companies ·
Company · · · · ip_to_company
example

Code that gets it right first time

you ask

“Write a function that takes a LinkedIn URL and returns a work email, or null if there isn’t one or it’s graded D.”

Cursor reads

linkedin_to_business_emailthe tool’s real schema: endpoint, parameters and response fields

you get

async function workEmail(linkedinUrl) {
  const res = await fetch('https://api.moltsets.com/api/v1/tools/linkedin_to_business_email', {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      'Authorization': `Bearer ${process.env.MOLTSETS_API_KEY}`,
      'User-Agent': 'my-app'
    },
    body: JSON.stringify({ linkedin_url: linkedinUrl })
  });
  const { results, status } = await res.json();
  if (status !== 'ok' || results.risk_score === 'D') return null;
  return results.email;
}

It checks status, not the HTTP code: a miss comes back as a 200 with status: "not_found", and costs nothing. It also sends the User-Agent header MoltSets requires.

use cases

What teams use it for

  1. 01

    Build an integration

    Ask the agent to wire MoltSets into your app. It reads the real schemas, so endpoints, parameters and response fields are right first time.

    over MCP

  2. 02

    Lookups while you code

    Need a contact’s email or the company behind an IP? Ask in the chat without switching to a browser.

    tool linkedin_to_business_email

  3. 03

    Test against real data

    Have the agent run a call before it writes the code around it, so you see the actual response shape.

  4. 04

    Handle misses properly

    The agent learns that a miss is a 200 with status: "not_found", not an error, and writes the fallback.

    read status

  5. 05

    Seed test data

    Pull a small, real list of people or companies to build and test against.

    tool search_people

  6. 06

    Check your headroom

    Ask for your token balance and usage before a test run. Account, billing and usage checks are free.

    tool get_usage

good to know

Before you build on it

  1. 01No secrets in mcp.json

    Don’t: Put your Client ID, Client Secret or ms_ API key in .cursor/mcp.json.

    Do: Keep the file to the URL and transport. Cursor asks for the credentials on first connect and stores the token itself.

  2. 02The URL has to be exact

    Don’t: Add a trailing slash or an extra path to the server URL.

    Do: Use exactly https://mcp.moltsets.com/mcp, then restart Cursor if it doesn’t connect.

  3. 03Read status, not the HTTP code

    Don’t: Treat a 200 as a hit in code the agent writes. A miss is a 200 too.

    Do: Check status: "ok" is a hit, "not_found" is a free miss.

  4. 04Every request needs a User-Agent

    Don’t: Send bare requests from your own code. Without a User-Agent header MoltSets returns 403.

    Do: Set any non-empty User-Agent, such as your app’s name.

pricing

What it costs

Calls from Cursor run on your MoltSets plan, with the same data and limits as the API. A lookup that finds nothing isn’t charged, and account, billing and usage checks are free.

Start free with 1,000 calls, then move to a flat-rate unlimited plan. Full detail on the pricing page.

free

$0to start
Enrichment records1klifetime

Try before you commit, no card required.

get started
  • 1k data calls total
  • 100 search records total
  • Personal email included 

solo

$27/ month
Enrichment records1k/ 5 hours

For solo builders and small lists.

get started
  • Unlimited data
  • 500 search records / 5h
  • Personal email included 

pro MOST POPULAR

$97/ month
Enrichment records15k/ 5 hours

For teams enriching at scale.

get started
  • Unlimited data
  • 7.5k search records / 5h
  • Personal email included 

team

$397/ month
Enrichment records150k/ 5 hours

For teams that have outgrown the $97 limits.

get started
  • Unlimited data
  • 75k search records / 5h
  • Personal email: 75k / week 
help

Questions & answers about MoltSets in Cursor

Every step is in the cursor setup guide.

Either works and both end in the same OAuth sign-in. Settings is quickest for you alone; .cursor/mcp.json can live in your repo, since it holds only the URL and transport, never credentials.

Log in at app.moltsets.com, go to Connectors and create a new connector. Cursor asks for both values the first time it connects.

No. The MCP signs Cursor in over OAuth. Code that calls the REST API uses an API key (ms_...) from API keys in the MoltSets app, sent as a Bearer token.

Restart Cursor after adding the server; most clients need a full restart to see a new one. Check the URL is exactly https://mcp.moltsets.com/mcp, with no trailing slash. If you see invalid credentials, copy the Client ID and Secret again from Connectors.

The call succeeds with status: "not_found" and nothing is charged. Over REST that’s still a 200, so code should read status to tell a hit from a miss.

For lookups and short lists, the MCP is fine. For whole CSV files, have the agent run the MoltSets CLI in the terminal, which enriches a file in one command on the same plan.

other ways to connect

Not using Cursor?

MoltSets Console - SIGN UP
SYS: ACCESS GRANTED

Get your API key

1,000 API calls, no card. Sign up and start calling the API today.