Curviate x Cursor

Build and run LinkedIn workflows inside Cursor. Give Cursor the Curviate CLI or the MCP server, and let it run LinkedIn work for you.

Start for free See the setup

No card required

What is Cursor?

Cursor is an AI-powered code editor built on VS Code with chat, code completion and agent features. Software developers use it to write and refactor code across a project.

Visit cursor.com

How Cursor works with Curviate

Cursor connects to Curviate’s MCP server from .cursor/mcp.json, so its agent can read LinkedIn while you write the code that works with it. Sign in with OAuth or send your key from an environment variable. The Curviate CLI works from Cursor’s terminal too, for scripts you check in.

Commands and toolscurviate core search peoplecurviate core inbox listsend_message

Set up Cursor with Curviate

Two ways in: the Curviate CLI, which Cursor runs like any command, or the same MCP server Claude and ChatGPT use.

1
Paste one line into Cursor
Cursor installs the Curviate CLI and walks you through signing in. You approve once in the browser; the key is saved without being printed.
Set up https://curviate.com/INSTALL.md
2
Or add the MCP server
Add Curviate to .cursor/mcp.json. Keep the key in an environment variable if your setup allows it.
{ "mcpServers": { "curviate": {
"url": "https://app.curviate.com/mcp",
"headers": { "Authorization": "Bearer cvt_live_…" }
} } }
3
Ask for the work
Give Cursor a goal. It picks the commands or tools, reads the results and drafts what comes next.
› Find heads of RevOps in Germany and draft a connection note for each.

What Cursor can do with it

Real LinkedIn work, run from your editor or terminal.

“Write scripts/sync.ts that posts each row of leads.csv to Curviate as a Contact and adds the new Contacts to the Q4 Motion.”

POST /v1/contactsPOST /v1/motions/{id}/contacts

“Look up the five people who last messaged me on LinkedIn and add their companies to accounts.md.”

list_chatsget_company

“Export the Contacts tagged hot to data/hot.csv with the CLI, LinkedIn URL and email only.”

curviate contact export --tag hot

Cursor details that matter

From Cursor’s MCP docs and Curviate’s client setup guide.

1
Project or global
.cursor/mcp.json in a project adds Curviate there; ~/.cursor/mcp.json adds it to every project. Turn a server on or off from Customize in the sidebar.
2
OAuth or an environment variable
With only the url, Cursor opens Curviate’s sign-in in your browser. For a key, Cursor fills ${env:…} from the environment it was started in, so the key stays out of the file.
"headers": { "Authorization": "Bearer ${env:CURVIATE_API_KEY}" }
3
Approvals
Cursor asks before each MCP tool call by default. Curviate marks its reading tools read-only; keep writes such as send_message on approval, even if you allowlist the reads.

Questions about Curviate x Cursor

Should Cursor use the CLI or MCP?

Either works. The CLI gives Cursor plain commands with JSON output it can read and script; MCP gives it the same tools Claude and ChatGPT use. Many teams set up both.

Where does my API key live?

With the CLI, curviate setup saves it in a local profile without ever printing it. With MCP, keep it in an environment variable or sign in with OAuth where Cursor supports it.

Which LinkedIn actions can Cursor use?

All of them: search, profiles, companies, the inbox, invitations, posts, scheduled drafts, plus Sales Navigator and Recruiter for premium seats.