LinkedIn actions for AI agents: search, messaging, posts and invites, as hosted MCP tools.
com.curviate/mcp (MCP) Server
This MCP server provides LinkedIn actions for AI agents, exposed as hosted MCP tools. It supports operations for search, messaging, posts, and invites. The server is described under the slug com-curviate-mcp and is tagged for integration with AI agents and LLM toolchains via MCP.
LinkedIn actions for AI agents, as MCP tools. One hosted URL, nothing to install.
Connect in 30 seconds
Point any MCP client that speaks remote Streamable HTTP at one URL:
code
https://app.curviate.com/mcp
Sign in with OAuth where the client offers it, otherwise send your Curviate API key as an Authorization: Bearer header. Your agent then has LinkedIn search, messaging, posts and connection requests as native tools. Sales Navigator and Recruiter tools are off by default and switch on per workspace, and they answer only for a connected account that holds the product: see Toolsets.
Your shell expands $CURVIATE_API_KEY when you run that command, so the key itself lands in Claude Code's config file. Prefer the OAuth path above unless you need a key.
Check either setup with claude mcp list: curviate reads Connected.
Keep the single quotes: Gemini CLI stores ${CURVIATE_API_KEY} as written and fills it from the environment when it connects, so the key stays out of the settings file.
Check with gemini mcp list: curviate reads Connected. Gemini CLI will not start MCP servers in a folder you have not trusted, where the server reads Disabled instead.
Any client that speaks remote Streamable HTTP can connect. Try OAuth with the bare URL first, then the Authorization: Bearer header. A client that connects but fails tool calls with 401 is usually sending the header only on connect: see Troubleshooting.
Authentication
Method
Use it when
OAuth 2.1
The client supports it. Always the first choice: no key leaves the dashboard, and you revoke the client on its own under Settings, Authorized applications.
Authorization: Bearer cvt_live_YOUR_KEY
The client can set a header but has no OAuth, or runs unattended.
?token=cvt_live_YOUR_KEY
Last resort, for a client that can set no header. The header wins if a request carries both.
Your API key is a full-access workspace credential: anyone holding it can act on every LinkedIn account in the workspace. Create, rotate and revoke it from the key chip in the dashboard top bar, keep it in an environment variable, and reference the variable from the client config rather than the literal key.
Find heads of engineering at Series B fintech companies in Berlin who posted about hiring in the last month.
code
Triage my LinkedIn inbox: summarize every thread still waiting on me, then draft a reply to each one.
code
Show me the five most relevant people who commented on my last post, and draft a connection request note for each referencing what they said. I will say which ones to send.
code
Draft a post about what we shipped this week, in my voice, and show it to me before anything goes out.
code
Review the Sales Navigator leads I saved this week and flag the ones who recently changed jobs.
