The LinkedIn MCP Server for AI Agents
Give Claude, ChatGPT, or any AI agent one key to work LinkedIn: find people, send invites and messages, and pull enriched profiles, on accounts that stay safe by design.
A LinkedIn MCP server is a typed set of tools an AI agent calls to act on LinkedIn: search, connect, message, and enrich. gtm-api.com is the agent-native, account-based LinkedIn API: add a single API key to Claude, Cursor, or ChatGPT and your agent runs real LinkedIn outreach through 160+ typed tools, with the account safety enforced server-side. It’s the same infrastructure running 20,000+ LinkedIn accounts at under 1% monthly ban.
Most “LinkedIn + AI” content stops at drafting a message. An MCP server is the layer that lets the agent do the work itself (send the invite, reply in the thread, enrich the lead) with no browser extension and no scraping. The rest of this page covers what an MCP server is, how to connect it to Claude in three steps, what the agent can do, and why it doesn’t get your account banned.
On this page
What is a LinkedIn MCP server?
A LinkedIn MCP server is a program that exposes LinkedIn actions (search, connect, message, enrich) as Model Context Protocol tools that an AI agent can call. Instead of a person clicking through a dashboard, the agent reads the tool list and runs the action itself. gtm-api.com is a managed one: hosted and typed, wired into the safety stack that keeps accounts alive.
MCP is the open standard introduced by Anthropic in late 2024 and since adopted across Claude, OpenAI’s ChatGPT, Cursor, and the wider agent ecosystem. People describe it as “a USB-C port for AI”: one connector that lets any model plug into any tool. A LinkedIn MCP server applies that standard to a single channel, LinkedIn.
GTM API is MCP-first: every capability is defined once as a typed schema, which generates the MCP tools, a REST API, and webhooks from the same contract. A Claude or Cursor agent and a custom backend therefore act on LinkedIn through exactly the same validated operations, with no drift between them and no glue code to maintain.
How to connect LinkedIn to Claude
Connect LinkedIn to Claude in three steps: get an API key, add the GTM API MCP server to your client config with that key, then prompt Claude in plain English. Claude discovers the LinkedIn tools automatically and runs them on your connected account. The same flow works in Cursor and any MCP client.
Step 1: Get your API key
Sign up at app.gtm-api.com, connect a LinkedIn account (it opens in its own cloud browser session on a dedicated residential IP), and copy your API key. The 7-day trial needs no card.
Step 2: Add the MCP server to your client
Drop the GTM API server into your MCP config with your key. In Claude Desktop or Cursor that’s a few lines:
“mcpServers”: {
“gtm-api”: {
“url”: “https://mcp.gtm-api.com”, // your exact endpoint + key: gtm-api.com/docs
“headers”: { “Authorization”: “Bearer YOUR_API_KEY” }
}
}
}
Step 3: Prompt in plain English
Restart the client and just ask. The agent sees the LinkedIn tools and picks the right ones:
“Every morning, accept new connection invitations from founders, reply with a short welcome, and add anyone hiring SDRs to a ‘warm’ list.”
Under the hood the agent calls get_my_latest_linkedin_connection_invitations, accept_linkedin_connection_invitation, and send_linkedin_message. Every outward action runs a preview → confirm step and a server-side daily-limit check before it ever touches LinkedIn.
Can ChatGPT or an AI agent send LinkedIn messages?
Yes. Through a LinkedIn MCP server, ChatGPT, Claude, or a custom agent can actually send LinkedIn messages, connection requests, and InMail, not just draft them. gtm-api.com exposes send_linkedin_message, send_linkedin_connection_request, and send_linkedin_inmail as tools. The agent calls them and the message goes out from your account.
Most “ChatGPT for LinkedIn” advice stops at teaching the model to write a message you then paste in yourself. An MCP server closes the loop. The agent sends it, reads the reply with get_my_latest_linkedin_messages, and can hand a thread back to a human by marking it unread when judgment is needed, so a person still owns the calls that matter. Plenty of tools can “send” through MCP now, HeyReach and Salesforge among them, so sending is no longer the differentiator. What separates the tools is where the send fires from: an owned, warmed account, behind a preview → confirm step and a server-side daily-limit check.
What can the agent do?
A GTM API agent can run the full LinkedIn outreach loop: find people, send and accept connections, message across every LinkedIn surface, track and engage with posts, enrich profiles and companies, and read its own account health. That’s 160+ typed tools across 10 LinkedIn toolsets, all behind one key.
| Toolset | What your agent can do |
|---|---|
| Messaging | Send DMs, voice notes, InMail and Sales Navigator messages. Sync and search the whole inbox. Read reply metrics |
| Network | Send & withdraw connection requests, accept/ignore invitations, list connections, followers and their growth |
| Content | Track posts and their metrics, comment, like/react, pull the engagers and commenters on any post |
| Enrichment | Lite & full profile, experience, skills, education, posts, plus company data, returned as typed JSON |
| Scraping / search | People, company and post search by URL or params. Similar profiles, employees, decision-makers, post engagers |
| Accounts & pacing | Connect accounts, set smart daily limits, read the self-profile, reset a stale sync |
| Account monitor | Health snapshots, benchmarks, quota-hit log, block log, activity log, sync runs (read-only audit) |
| Browsers | Anti-detect cloud browsers and dedicated proxies with connectivity & location checks |
| Data plane | Saved searches (create / run), the credit ledger, and stored result rows |
| Platform | Webhooks + delivery logs, so your agent reacts to LinkedIn events in real time |
LinkedIn is the live channel today. Email (Gmail, Outlook, IMAP), messengers (WhatsApp, Telegram, Instagram DMs) and calendars (Google, Microsoft) are on the roadmap on the same typed contract, so an agent built against LinkedIn today will pick up those channels as they land.
Is it safe for my LinkedIn account?
Yes. The stack is built around account safety: gtm-api.com runs each account in its own anti-detect cloud browser with a dedicated residential proxy, warms new accounts up, and enforces health-aware daily limits server-side, before any action fires. GTM API reports 20,000+ LinkedIn accounts at under 1% monthly ban on this stack, self-reported. MirrorProfiles‘ co-founder calls the stack behind it “the safest and most reliable option we’ve tested”.
The safety comes from four things working together: a single dedicated session per account (no shared browser fingerprints), a residential proxy pinned to the account’s location, a warm-up curve on new accounts, and a limit check that runs on every send_* call so an over-eager agent can’t burn an account. Outward actions also require preview → confirm, and every action lands in an activity and quota-hit log you can audit. Compare that to a browser extension running in your own logged-in Chrome, or a scraper hammering pages with your cookie: those are the exact patterns that trigger restrictions.
LinkedIn MCP server vs open-source scrapers
A managed LinkedIn MCP server runs on owned, warmed accounts behind anti-detect sessions, dedicated residential proxies and server-side limits, so it holds up at volume. An open-source MCP server drives a real browser session with your own cookie and no safety layer. That holds up for a weekend demo. Point real outreach volume at it and the missing safety layer becomes the problem. The popular open-source options, like stickerdaniel/linkedin-mcp-server on GitHub (1.9k★), Apify‘s LinkedIn actors, and the servers listed on mcpservers.org and Docker’s MCP catalog, prove the pattern but ship no account safety. Other managed servers take the same “safe managed” angle, most visibly ConnectSafely.ai. What gtm-api.com brings that the rest of the list doesn’t is at-scale numbers it publishes: an under-1% monthly ban-rate across 20,000+ owned accounts, plus a typed MCP + REST contract to build against. And unlike scraper-APIs that were sued and shut down (Proxycurl, 2025), owned accounts and a published ban-rate don’t disappear. Open-source is the right place to experiment, and production outreach belongs on a managed API.
| Dimension | GTM API (managed) | Open-source MCP | Scraper / Apify MCP |
|---|---|---|---|
| Setup | One key, hosted | Self-host + your cookie | Actor + your cookie |
| Safety layer | Anti-detect + proxy + limits | None | None |
| Daily-limit enforcement | Server-side, per account | You build it | No |
| Account model | Owned, warmed, isolated | Your live session | Your live session |
| Coverage | 160+ tools, send + read + enrich | Reads, some sends | Reads / scrape only |
| Ban risk at volume | <1% monthly (20k accts) | High | High |
| Support & uptime | Managed SLA | Community | Best-effort |
Open-source servers currently win the “linkedin mcp” search result but not the production workload. They prove the pattern, then teams move to a managed stack once an account gets restricted. Among managed options, a published ban-rate at scale is the differentiator.
What does it cost?
gtm-api.com starts at $19 per connected account per month and scales down to $5 at volume, with unlimited API calls and no per-action fees. The 7-day free trial needs no card and there’s no minimum. Enrichment and Signals are optional metered add-ons. Billing is per connected account, so the number of messages your agent sends doesn’t change the price.
Full breakdown, including how per-account pricing compares to the per-call metering most data APIs use, is on the LinkedIn API pricing page.
Frequently Asked Questions
Is there a LinkedIn MCP server?
Yes. gtm-api.com is a managed LinkedIn MCP server: a hosted set of Model Context Protocol tools an AI agent calls to search, connect, message and enrich on LinkedIn. There are also open-source LinkedIn MCP servers on GitHub, but they scrape with your cookie and have no safety layer, so they are better for demos than production.
Which AI clients support the GTM API LinkedIn MCP?
Claude (Desktop and API), Cursor, ChatGPT, LangChain and n8n, any MCP-compatible client. For everything else, the same actions are available over REST and webhooks, because GTM API is built from one typed schema that generates MCP, REST and webhooks together.
Do I need to write code to use it?
No. In an MCP client like Claude or Cursor you connect the server once, then prompt in plain English. The agent discovers the LinkedIn tools and runs them. Developers who want to build a product on top can call the same actions over the REST API instead.
Can ChatGPT or an AI agent actually send LinkedIn messages?
Yes. Through the MCP server the agent calls real tools, send_linkedin_message, send_linkedin_connection_request, send_linkedin_inmail, so the message is sent from your connected account, not just drafted. Every send runs a preview-then-confirm step and a server-side daily-limit check first.
Is a LinkedIn MCP server safe for my account?
It depends entirely on the server. GTM API runs each account in its own anti-detect cloud browser with a dedicated residential proxy, warms new accounts up, and enforces health-aware daily limits before any action, which is how it keeps 20,000+ LinkedIn accounts at under 1% monthly ban. Cookie-based open-source servers offer none of that.
Can I connect more than one LinkedIn account?
Yes, that is the design. Connect as many accounts as you like. Each runs in an isolated cloud browser with its own proxy and its own pacing. You pay per connected account per month, and your agent can act across all of them through one key.
Is there a free trial?
Yes. GTM API has a 7-day free trial with no credit card required, and no minimum commitment. Pricing starts at $19 per connected account per month and scales down to $5 at volume, with unlimited API calls.
Is LinkedIn automation against LinkedIn’s terms?
Third-party automation is a grey area and runs against LinkedIn’s User Agreement, so it always carries some risk, and no tool can honestly promise otherwise. That’s exactly why a per-account safety layer matters: gtm-api.com runs each account in an isolated cloud browser on its own residential proxy with server-side limits, which is how it keeps 20,000+ accounts at under 1% monthly ban. This is information, not legal advice.
Sources & Further Reading
- Anthropic / Model Context Protocol, modelcontextprotocol.io (the open standard)
- GTM API, product & live LinkedIn toolsets
- MirrorProfiles, LinkedIn automation guide (independent anti-detect testing)
- Example open-source server, stickerdaniel/linkedin-mcp-server (GitHub) · directories: mcpservers.org, MCP Market
- Related: Safe LinkedIn automation
Give your agent LinkedIn access.
Grab an API key, connect your first LinkedIn account, and point Claude, ChatGPT, or Cursor at it in minutes. 160+ typed tools, one contract, the same stack behind the published ban-rate.
Last updated: July 2026 · Tool names and limits verified against the live GTM API at time of publication