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
credentials never stored in the file
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
Connect MoltSets to Cursor
-
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.
-
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. -
03
Set the transport and URL
Choose HTTP (or Streamable HTTP, depending on your version) and enter:
https://mcp.moltsets.com/mcp -
04
Sign in over OAuth
Cursor sees that the server needs authentication and asks for your Client ID and Client Secret.
-
05
Approve the connection
Approve access in the browser tab that opens. If MoltSets doesn’t appear, restart Cursor.
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 URL | Name + company domain | Email(s) | Title, industry, location | Website visitor IP |
|---|---|---|---|---|---|
| Work email | linkedin_ |
search_ |
· | · | · |
| Best email (work, else personal) | linkedin_ |
· | · | · | · |
| Mobile number | linkedin_ |
· | · | · | · |
| LinkedIn profile | · | · | email_ |
· | · |
| Send-safety grades | · | · | validate_ |
· | · |
| People list | · | · | · | search_ |
· |
| Company list | · | · | · | search_ |
· |
| Company | · | · | · | · | ip_ |
Code that gets it right first time
you ask
Cursor reads
linkedin_to_business_emailthe tool’s real schema: endpoint, parameters and response fieldsyou 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.
What teams use it for
-
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 -
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 -
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.
-
04
Handle misses properly
The agent learns that a miss is a
200withstatus: "not_found", not an error, and writes the fallback.read
status -
05
Seed test data
Pull a small, real list of people or companies to build and test against.
tool
search_people -
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
Before you build on it
-
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.
-
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. -
03Read status, not the HTTP code
Don’t: Treat a
200as a hit in code the agent writes. A miss is a200too.Do: Check
status:"ok"is a hit,"not_found"is a free miss. -
04Every request needs a User-Agent
Don’t: Send bare requests from your own code. Without a
User-Agentheader MoltSets returns403.Do: Set any non-empty
User-Agent, such as your app’s name.
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
Try before you commit, no card required.
get started- 1k data calls total
- 100 search records total
- Personal email included
solo
For solo builders and small lists.
get started- Unlimited data
- 500 search records / 5h
- Personal email included
pro MOST POPULAR
For teams enriching at scale.
get started- Unlimited data
- 7.5k search records / 5h
- Personal email included
team
For teams that have outgrown the $97 limits.
get started- Unlimited data
- 75k search records / 5h
- Personal email: 75k / week
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.
Not using Cursor?
I use an AI agent
I write code
I prospect on LinkedIn
Something else? See every integration.
Get your API key
1,000 API calls, no card. Sign up and start calling the API today.