Workspace
crm.read
- Verify which workspace the connection can use
LinkedIn MCP server
OutreachGenie's hosted MCP server lets Claude, ChatGPT, Claude Code, and Codex work with your LinkedIn prospect lists, outreach flows, and campaign drafts. You approve each change. The Chrome companion runs LinkedIn-side steps in your own browser.
Free, including MCP access. LinkedIn limits still apply. See pricing.
Server URL
https://api.outreachgenie.ai/mcpBefore you connect
Claude works with the prospects, lists, notes, flows, and campaigns saved in OutreachGenie. It does not browse LinkedIn, search LinkedIn, or read your LinkedIn messages.
During sign-in you approve separate scopes for reading the CRM, changing it, preparing campaigns, and activating them. Leave activation out if you want Claude to prepare work but never start it.
Invitations, messages, and visits run through the Chrome companion in your signed-in browser, at the pace your workspace limits allow. Keep that browser open while a campaign runs.
21 tools
crm.read
crm.read · crm.write
crm.read · crm.write
crm.read · crm.write
campaigns.write · campaigns.activate
content.read · content.write
Claude and ChatGPT
In ChatGPT, add the same server URL as a connector where your plan allows custom connectors.
Claude Code and Codex
Create a key under Settings, then API keys in OutreachGenie, keep it in an environment variable, and add the server once:
claude mcp add --transport http linkedin-crm \
https://api.outreachgenie.ai/mcp \
--header "Authorization: Bearer $LINKEDIN_CRM_API_KEY"Do not commit the key. Full steps are in the Claude Code guide and the Codex guide.
First prompts
“Verify my OutreachGenie workspace and tell me which tools you can use.”
“Create a list called Conference leads, import these LinkedIn profile URLs, and tell me which records were created or already existed.”
“Look up this LinkedIn profile URL and summarize what we already know before I write to them.”
“Use the Partner outreach flow with the Partner leads list. Summarize the launch plan and wait for my approval before creating the campaign.”
A useful pattern: ask for a summary of the list, flow, and first message, check it yourself, and only then ask Claude to create or activate the campaign.
Account risk stays visible
LinkedIn says third-party software and browser extensions that scrape, modify, or automate activity on its website are not allowed. Asking Claude to prepare the work does not change that. Keep batches small enough to review, and stop if the account shows a warning, verification prompt, or restriction.
Read LinkedIn's automated activity policyLinkedIn MCP questions
No. OutreachGenie is independent and is not affiliated with or endorsed by LinkedIn. The MCP server connects an AI client to your OutreachGenie workspace, not to a LinkedIn API.
No. The tools work with records in your OutreachGenie workspace: prospects, lists, notes, flows, campaigns, and content drafts. LinkedIn-side steps such as invitations and messages run later through the Chrome companion in your signed-in browser.
Only if you grant the campaign activation scope during sign-in. Even then, ask Claude to summarize the list, flow, and messages first and approve activation yourself. Reading data and preparing a draft use separate, narrower scopes.
No. MCP access is part of the free OutreachGenie workspace. There is no separate API or MCP plan. LinkedIn's limits and account restrictions still apply to anything the companion runs.
Claude and ChatGPT connect through OAuth: you sign in, choose a workspace, and approve the requested scopes. Claude Code and Codex can also connect with a workspace API key. Any client that supports remote Streamable HTTP MCP servers can use the same endpoint.
Many open-source LinkedIn MCP servers sign in to LinkedIn with your own session and read pages on demand. That gives an agent raw profile access but no lists, flows, or campaign history to work from, and it carries the same LinkedIn policy risk. OutreachGenie gives the agent a workspace with that state, with approval points before changes.