Gemini CLI and LinkedIn
Prepare LinkedIn posts with Gemini CLI.
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
Limited
Read all LinkedIn formats and limitsCompany 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
# OAuth: then run /mcp auth heyeveryone inside Gemini CLI
gemini mcp add --transport http heyeveryone https://heyeveryone.ai/mcp
# Personal access token
gemini mcp add --transport http --header "Authorization: Bearer hey_pat_..." \
heyeveryone https://heyeveryone.ai/mcp--scope user writes ~/.gemini/settings.json; the default is the project's .gemini/settings.json. By hand:
{
"mcpServers": {
"heyeveryone": {
"httpUrl": "https://heyeveryone.ai/mcp",
"headers": { "Authorization": "Bearer hey_pat_..." }
}
}
}httpUrlmeans Streamable HTTP.urlalone means the old SSE transport, althoughgemini mcp add --transport httpwrites"url"with"type": "http", which also works.- Gemini's docs don't promise
$VARexpansion insideheaders. Paste the token, or use/mcp authinstead.
Source: gemini-cli docs: MCP 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 Gemini CLI guide