LinkedIn actions for AI agents: search, messaging, posts and invites, as hosted MCP tools.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Manual Client & Custom JSON ConfigExpand JSON â–¾
No confirmed setup config for this listing yet. We only publish a config block when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for Curviate/curviate-mcp, and we’d rather show nothing than a guess you’d paste into your client. Follow the project’s own setup instructions for the current steps.
Documentation Overview
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:
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.
You need a Curviate workspace and one connected LinkedIn account. Full walkthrough: MCP quickstart.
Your client
Claude Code
OAuth:
Then run /mcp in Claude Code, select curviate, choose Authenticate, and approve access in the browser.
API key:
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.
Details and caveats: docs.curviate.com/reference/mcp/client-setup#claude-code
Codex
OAuth:
Codex prints an authorization URL. Open it, sign in to Curviate, and approve access. To sign in again later, run codex mcp login curviate.
API key, read from the environment each time Codex connects:
Check with codex mcp list.
Details and caveats: docs.curviate.com/reference/mcp/client-setup#codex
Gemini CLI
OAuth:
Then start gemini, run /mcp auth curviate, open the printed URL, sign in to Curviate, and approve access.
API key:
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.
Details and caveats: docs.curviate.com/reference/mcp/client-setup#gemini-cli
Another client
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.
Full rules: Authentication.
Things to ask your agent
Links
| MCP quickstart | Connect a client and make a first call |
| Client setup | Per-client commands and UI paths |
| Authentication | OAuth, the Bearer header, and ?token= |
| Toolsets | Which tools your client sees, and how to turn more on |
| Errors and limits | The error shape, rate limits, safety limits |
| Troubleshooting | 401s, a missing tool, a dropped session |
| curviate.com | What Curviate is |
| CLI | The same actions from a terminal or a shell script |
| TypeScript SDK | The same actions from your own code |
License
MIT. See LICENSE.
Related MCP Servers
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Curviate MCP
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/curviate-curviate-mcp)HTML Embed
<a href="https://allmcps.com/mcp/curviate-curviate-mcp"><img src="https://allmcps.com/api/badge/curviate-curviate-mcp?style=directory" alt="Curviate MCP on AllMCPs" /></a>