Gemini CLI
Connect Gemini CLI to heyeveryone.
Prepare channel versions from Gemini CLI and hand them back for review.
Connect with the shared guide
Follow the connection steps below, then choose the workspaces the agent may access. These steps are imported from the maintained agent guide.
Try a draft before a schedule
Example prompt: “Draft a post from these notes for the channels connected to my workspace. Show me the content link and any channel checks. Do not schedule or publish.” Review the result in heyeveryone, then ask Gemini CLI to request a review if needed.
What stays with a person
An agent cannot sign off, create review links, manage tokens or change billing. Schedule requests wait in Updates for confirmation by default. A person confirms publishing by default. A workspace owner can explicitly enable auto-publish for a particular agent in a particular workspace.
Credits and access
Agent access is included in every plan. MCP and API access does not cost credits; actions that run heyeveryone’s own AI do. See the credit cost before you run them. Your agent provider may charge separately.
Connect Gemini CLI
# 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.