VS Code
Connect VS Code to heyeveryone.
Use your editor’s agent to prepare content in the workspace your team reviews.
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 VS Code 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 VS Code
Run MCP: Add Server, or edit .vscode/mcp.json:
{
"inputs": [
{ "type": "promptString", "id": "hey-token", "description": "heyeveryone token", "password": true }
],
"servers": {
"heyeveryone": {
"type": "http",
"url": "https://heyeveryone.ai/mcp",
"headers": { "Authorization": "Bearer ${input:hey-token}" }
}
}
}Leave out headers and inputs to sign in with OAuth. VS Code identifies itself with its client metadata document, so there's nothing to register.
Source: VS Code MCP configuration.