Blog·
Connecting Claude, ChatGPT, and Cursor to a LinkedIn MCP
Claude, ChatGPT, and Cursor are named on some rows and absent on others. Linked API does not list those chat clients on the pages reviewed.
The client is not the action
A client can call only the tools the server documents. Connecting Cursor to a public-data MCP does not give Cursor an inbox. Connecting Claude to Composio does not give Claude Sales Navigator. Pick the server for the action, then check that your client is on that server’s agent list. A missing name means this comparison does not record it. It is not proof the vendor rejects the client.
One URL on Cesar
Cesar publishes a remote hosted MCP with one connector URL for eight agents: Claude, ChatGPT, Cursor, Claude Code, Codex, Gemini, Grok, and n8n. You enable it on Pro or Business and paste that URL into the client. The server reads chats through the Cesar browser extension.
The tools behind the URL are inbox read, drafts you send, labels, reminders, archive, connection notes, invites, snippets, people search, and paced Sales Navigator search. The Basic plan does not include the server.
Who each row names
The other rows name overlapping clients, and a few gaps matter.
- LinkMCP: Claude, ChatGPT, Cursor, Windsurf, Codex, plus n8n, Make, and Zapier.
- Linked API: an MCP server, agent skills, a CLI, a REST API, and a Node.js SDK. Named chat clients are not listed on the pages reviewed.
- ConnectSafely: Claude, ChatGPT, Cursor, HubSpot, and n8n. The homepage API section also names Zapier.
- Manifold MCP: Claude, ChatGPT, Cursor, Codex, and other MCP clients.
- Apify: Claude, Cursor, and other MCP-compatible clients.
- Composio: Claude, ChatGPT, and other supported AI agents. Cursor is not named.
- Zapier MCP: ChatGPT, Claude, and MCP-compatible clients. Cursor is not named.
- Bright Data: MCP-compatible agents, LangChain, and LlamaIndex.
- stickerdaniel/linkedin-mcp-server: MCP-compatible clients, including local AI development environments.
What to paste
Hosted products expect their own connector. Cesar’s is one URL for the eight named clients. The comparison records the client names and the tool surface. It does not reprint each vendor’s click-path.
After the client connects, the first check is the tool list the agent can see. If inbox tools are missing, the server is in the public-data or official-API group, or it is ConnectSafely, which does not document an inbox reader. If send is missing on Cesar, that is the documented boundary: the draft is the tool, and you send the message.
Figures and capabilities are from the linkedinmcp.ai comparison, updated November 2026. Confirm current capabilities on each vendor site before buying.
Related notes
- How to choose a LinkedIn MCP by the action the agent should takeMessaging, public research, and official publishing sit on different products. Start from the action, then from who sends, then from the price the vendor page prints.
- Self-hosting a LinkedIn MCPstickerdaniel/linkedin-mcp-server is the self-hosted option in this comparison. It covers inbox retrieval, messaging, and people search on infrastructure you run.