MCP SERVER

120+ LinkedIn actions.
One connector.

The Curviate MCP server gives your agent LinkedIn as native tools. Add one connector to Claude, ChatGPT or Cursor and the model can search, message, publish and recruit through the LinkedIn account you connect. No wrapper code, no browser puppetry.

Try for freeRead the docs
Curviate/curviate-mcp· open source on GitHub
120+ LinkedIn actionsWorks in Claude, ChatGPT, Cursor20+ webhook event typesEU data residency
ConnectorsMCP client settings
CurviateCurviatepreferredhttps://app.curviate.com/mcp · Streamable HTTPconnected
Local MCP clientnpx @curviate/mcp · stdioavailable
search_peoplesend_messagesend_invitecreate_postlist_notificationsrecruiter_pipeline+ 70 more

Curviate connects over Streamable HTTP, the quickest way in: paste one URL, nothing to install. Prefer to run it yourself? The local MCP client is open source on GitHub.

01ADD THE CONNECTOR

Connect Claude or ChatGPT in two steps.

One connector sits between your agent and LinkedIn. Paste a single URL, sign in, approve once. No code, no key to copy.

Your agent
Claude, ChatGPT, Cursor, CLI
MCP
One connector
Curviate
app.curviate.com/mcp
LinkedIn
searchmessagepostinviterecruit
120+ actions, scoped to your seat
1
Add a custom connector and paste this URL.
https://app.curviate.com/mcp
Claude: SettingsConnectorsAdd custom connectorChatGPT: Developer modePluginsNew connector
2
Sign in and approve once.

Curviate signs you in, so there is no API key to copy. Approve once and your agent runs LinkedIn natively. Revoke access anytime from your dashboard.

Curviate connected120+ LinkedIn tools available
AdvancedConnect with an API key instead
Cursor and other clients authenticate with your Curviate API key. Clients that support custom headers send it as a Bearer token; the rest append ?token=cvt_live_YOUR_KEY to the URL. The transport is Streamable HTTP on the official MCP SDK, so any spec-conforming client connects. Your key is a full-access workspace credential, so keep it secret. Per-client walkthroughs live in the docs.
Try for freeView on GitHub
02TERMINAL AGENTS

Claude Code and Codex, one command.

The same connector, straight from your terminal. Run one command, approve in your browser, and your agent runs LinkedIn natively. No wrapper code, no SDK to install, no key to paste.

terminal
claude mcp add --transport http curviate https://app.curviate.com/mcp
A browser opens to approve. Nothing long-lived is stored in your config.
Advanced
Prefer a key? Pass it as a Bearer header, or append ?token=cvt_live_YOUR_KEY to the URL. To run the client yourself, the open-source @curviate/mcp is developed in the open at github.com/Curviate/curviate-mcp, or drive the Curviate CLI directly with your key. Your key is a full-access workspace credential, so keep it secret.
03THE SURFACE

What can your agent do?

The platform behind the connector exposes 120+ LinkedIn actions, and the MCP server puts them in your agent's reach as intent-named tools: people and company search, messaging and inbox triage, posting and commenting, connection requests, jobs, Sales Navigator lead work and Recruiter pipelines, with 30+ actions dedicated to the two premium surfaces.

searchPeople, companies, posts, jobs, groups; filter resolutionCore seat
messagingChats, messages, InMail, inbox triage, reactionsCore seat
networkConnection requests, accepts, withdrawals, followsCore seat
publishingPosts, comments, reactions, saved posts, company pagesCore seat
jobsPostings, applicants, budgets, publish and closeCore seat
sales-navigatorLead and account lists, SN search, SN messagingSN premium
recruiterHiring projects, pipelines, Recruiter search and chatsRecruiter premium

The full action inventory, honestly labelled: the LinkedIn actions catalogue.

04WHERE IT FITS

Where MCP fits

Curviate MCPBrowser-using agents
SetupOne connector URLInstall and script a browser
Coverage120+ platform actions, scoped to your seatWhatever the DOM allows today
MaintenanceCurviate maintains the surfaceBreaks when the page changes
FitChat and IDE agents (Claude, ChatGPT, Cursor)Demos; unreliable for real operations
Time to first actionPaste one connector URL and start callingScript a browser per site

The connector fronts the REST API; developers embedding LinkedIn get the typed SDK, and terminal loops get the CLI.

05FAQ

Questions, answered

Yes. Curviate ships a hosted MCP server that exposes 120+ LinkedIn actions to any MCP-capable agent. You add https://app.curviate.com/mcp as a custom connector. Claude and ChatGPT sign you in with OAuth (no key to copy), while Cursor and other clients use your API key. The tools appear in your client scoped to what your connected account holds.

06REFERENCE

Open the reference

Getting startedConnector setup, per clientAuthentication and accountsKeys, seats, connect flowsWebhooksThe return path: 20+ event types

Your agent, on LinkedIn.

Paste one connector URL and the tools appear, scoped to your seat.

Try for freeRead the docs
COMPANY · LEGAL

Privacy Policy

Redmer Holding GmbHLast updated July 25, 2026

Who we are

Curviate is operated by Redmer Holding GmbH ("Curviate", "we", "us"), a German GmbH registered at Amtsgericht Bonn, HRB 29957, registered address Hostertstraße 16, 53332 Bornheim, Germany. Full company details are on our Imprint. We haven't appointed a statutory Data Protection Officer, since our processing doesn't reach the scale or sensitivity that requires one. Privacy questions go to privacy@curviate.com.

The two roles we play

When you create an account and use Curviate, we process your own data (identity, billing, API keys, connector authorizations). For that data, we are the controller.

When you use Curviate to act on your own connected LinkedIn account, viewing profiles, sending messages, managing engagement, that content and those contacts belong to that account and its people. You are the controller of that data; we are the processor, acting only on your instructions, under the Data Processing Agreement between us. If one of your contacts has a question about being reached through Curviate, you're who they should contact first; email privacy@curviate.com if you need help routing it.

What we collect, and why

DataWhy
Account identity (name, email, sign-in method)Create and secure your account
Your LinkedIn credentialsOperate the actions you request
LinkedIn content returned by an API callFulfil that specific request, nothing more
API keys and connector (OAuth) authorizationsAuthenticate your API, CLI, MCP, or SDK requests
Billing detailsCharge you correctly and meet our tax obligations
Usage and security logsKeep the service reliable and abuse-free
Support messagesRespond to you
Website analytics, only if you opt inUnderstand how the site is used

We rely on our contract with you, our legitimate interest in running and securing the service, our legal obligations (tax law, for example), and, for analytics, your consent. We never sell your data or use it to train models.

Where it's processed, and who else touches it

Our infrastructure runs in the EU. Hosting: Railway. Database and auth: Supabase, Ireland. Email: Resend. Payments: Stripe. Network security: a DDoS-protection provider sits in front of our app and never sees or stores request content. LinkedIn connectivity: a third-party infrastructure provider that lets us execute LinkedIn actions on your behalf. Error tracking: Sentry, Frankfurt. Product analytics: PostHog, Frankfurt. Uptime monitoring: Better Stack.

We give the current, named list of every provider above, plus our Data Processing Agreement, to any customer who asks: security@curviate.com.

Outside the EU

All customer LinkedIn data, account data, and telemetry are processed and stored exclusively in EU regions of our sub-processors. A few providers we rely on (Stripe and Sentry, for example) are headquartered outside the EU/EEA; where that applies, it's covered by their own GDPR safeguards, typically the EU Standard Contractual Clauses.

How long we keep it

DataRetention
Account and workspace dataWhile your account is active
Closed accountRecoverable for 7 days, then deleted on day 8
LinkedIn credentialsUntil you disconnect that account
LinkedIn contentNot stored; any transient cache clears within 1 hour, never indexed, never used for training
API keysUntil you revoke or rotate them
Connector (OAuth) authorizationsAccess token ~1 hour; refresh token up to ~12 months, or until you revoke it, whichever comes first
Billing recordsAs required by German tax law, currently up to 10 years
LogsA short operational window; metadata only, never message content

The 12-month figure above is a server-side credential for a connected AI agent or app. It is not a cookie and doesn't touch your browser session; see Cookies below for that. You can see and revoke every connector from Authorized applications in your dashboard at any time.

Cookies

We keep cookies to a minimum, and ask before anything beyond the essentials runs.

Strictly necessary, no consent needed:

NamePurposeExpiry
cc_cookieRemembers your cookie choice12 months
curviate-themeRemembers light/dark mode (local storage, not a cookie)Persistent
sb-*-auth-tokenKeeps you signed inWhile active; cleared on sign-out

Analytics, only if you accept:

NamePurposeExpiry
_gaGoogle Analytics: distinguishes visitors2 years
_gidGoogle Analytics: distinguishes visitors24 hours
_ga_<container id>Google Analytics: persists session state2 years

No advertising cookies, ever. Accept and reject are equally easy, and you can change your mind any time via Cookie Preferences in the footer; we won't ask again for 12 months unless something material changes. Our LinkedIn connect flow and OAuth authorization screen never set anything beyond the essentials, so no banner appears there.

Connecting an AI agent or app

Curviate is built for AI agents and automated clients as much as for people. If you connect an app like Claude, or your own code, via an API key or an OAuth connector, it can act on your workspace within the access you gave it. What it does with anything it receives back, including what it sends to its own AI model, is between you and that provider; review its practices before connecting it. Review and revoke any connection any time from your dashboard.

Your rights

You can access, correct, delete, restrict, or object to your data, port it elsewhere, and withdraw consent at any time: email privacy@curviate.com. Closing your account starts the 7-day recoverable window above. We don't make automated decisions about you that have a legal or similarly significant effect. You can also complain to a supervisory authority; ours is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen (LDI NRW), www.ldi.nrw.de, though you're free to complain to the one in your own country instead.

Keeping it secure

Credentials are encrypted and never logged, returned, or shared. LinkedIn actions run through native, humanized flows; full detail is on our Security & Compliance page. If a breach puts your rights at risk, we'll notify the authorities and you, as GDPR requires. Curviate isn't directed at, or offered to, anyone under 16.

Changes

We'll update this page when our practices change, and reset the cookie prompt if the change is material.

Contact