Claude and LinkedIn
Prepare LinkedIn posts with Claude.
A person confirms before anything posts by default. A workspace owner can explicitly enable auto-publish for this agent in this workspace.
Check channel access first
Company pages are waiting for LinkedIn to approve our Community Management API access, which LinkedIn reviews by hand. Personal profiles work now; posts for pages go to the post kit until then.
Connect your agent
Custom connectors run from Anthropic's cloud, so they only work with a server that is reachable on the internet (not localhost). Plans: Free (one custom connector), Pro, Max, Team and Enterprise.
Pro, Max or Free:
- Open Customize > Connectors (claude.ai/customize/connectors). Older guides and some Desktop builds call it Settings > Connectors.
- Choose Add custom connector (+).
- Paste
https://heyeveryone.ai/mcp. - Leave Advanced settings alone. Claude picks the right client registration for heyeveryone on its own ("Use Claude's published identity").
- Click Add, then Connect. heyeveryone opens: sign in, tick the workspaces Claude may use, and click Connect.
- In a chat, turn the connector on from the tools menu. Try the Plan my week or What needs me prompt.
Team or Enterprise:
- An Owner adds the connector once for the organization: Organization settings > Connectors > Add > Custom > Web, then paste the URL.
- Each member then clicks Connect under Customize > Connectors. Everyone signs in with their own heyeveryone account.
Good to know:
- The OAuth callback Claude uses is
https://claude.ai/api/mcp/auth_callback. - A personal access token only works through the Request headers beta, which few organizations have: header
Authorization, valueBearer hey_pat_.... It can't be combined with OAuth. To change it, remove and re-add the connector. - Claude Desktop uses the same connectors for remote servers. Anthropic's docs describe no way to put a remote URL in
claude_desktop_config.json. - The community bridge `mcp-remote` works but isn't needed:"command": "npx", "args": ["mcp-remote", "https://heyeveryone.ai/mcp"].
Sources: support.claude.com: custom connectors, claude.com: remote MCP connectors, claude.com: connector authentication, modelcontextprotocol.io: connect to remote servers.
Draft, review, then confirm
- Connect your channel in heyeveryone and grant the agent access to its workspace.
- Ask: “Draft a LinkedIn post from these notes. Check the channel rules and show me the content link. Do not schedule or publish.”
- Open the draft and inspect it. Ask the agent to request a review; a person creates the review link or reviews it personally.
- Review the current text and approve it if sign-off is required. Confirm the channels and time before publishing.
Access and credits
Agent access is included in every plan. MCP and API calls do not cost credits; actions that run heyeveryone’s own AI do, with cost shown first. Your agent provider may charge separately.
Full Claude guide