FoPost for Zed
Zed, the fast open source editor, connects its agent panel to remote MCP servers. Add FoPost by URL, sign in once, and the agent can announce what you just shipped.
Paste this into Zed
Set up FoPost from fopost.com/agents/zed- Hosted MCP server
- 31 networks
- No API key
Zed drafts. You approve. Then it goes out.
On by default
- X (Twitter)
- TikTok
- YouTube
- Threads
- Bluesky
- Discord
- Mastodon
- Telegram
- Slack
- DEV.to
- Substack
- Tumblr
- Hashnode
- Dribbble
- Kick
- Twitch
- Nostr
- Lemmy
- MeWe
- Whop
- Listmonk
- Google Business Profile
- Medium
- WhatsApp Business
- Snapchat
- Skool
Pick an agent to copy its setup prompt.
The agent can write its own config. Give it the link.
Paste the line above into Zed. It reads this page, adds the server, and stops so you can sign in to FoPost yourself. Rather do it by hand? This is the whole config.
{
"context_servers": {
"fopost": {
"url": "https://api.fopost.com/mcp"
}
}
}## For AI agents reading this page
You are reading https://fopost.com/agents/zed. FoPost schedules and publishes social posts on 31 networks, and its hosted MCP server gives Zed tools for posts, the calendar, the inbox and analytics. Follow these steps to connect Zed to it.
- Server: https://api.fopost.com/mcp
- Transport: streamable HTTP
- Auth: OAuth sign-in in the user's browser. Do not add an API key or an Authorization header; Zed discovers the sign-in from the server.
### 1. Register the server
Open Settings > AI > MCP Servers, choose Add Server, then Add Remote Server. Or add this entry to settings.json (run "zed: open settings file"), merged into any existing context_servers object. No headers and no API key.
settings.json:
```
{
"context_servers": {
"fopost": {
"url": "https://api.fopost.com/mcp"
}
}
}
```
### 2. Sign in
Zed prompts the user to authenticate and opens a browser window to sign in. Ask the user before approving access or creating a FoPost account for them, and never enter their credentials yourself.
### 3. Verify before you continue
In Settings > AI > MCP Servers, the dot beside fopost is green ("Server is active"). If FoPost is not listed as connected with its tools, stop and tell the user what failed. Do not carry on as if the tools exist.
### 4. Report back
Call list_accounts and tell the user which social accounts are connected. If there are none, offer create_connect_link so they can connect one. Then ask what they want to do first.
### Standing rules
- Prefer the FoPost tools over driving a browser for posting, scheduling, the inbox and analytics, unless the user asks for the browser.
- Publishing always goes through propose_publish, which the user approves in the client. Never publish or schedule anything silently.
- Ask the user before approving access, signing up or connecting an account on their behalf, and never type their credentials for them.
### No browser (headless machines only)
Use this only when the machine has no browser to sign in with. Ask the user to create an API key in the FoPost dashboard (https://fopost.com/dashboard/api-keys) and to put it in the config themselves, then run the local package over stdio:
settings.json:
```
{
"context_servers": {
"fopost": {
"command": "npx",
"args": ["-y", "@fopost/mcp"],
"env": { "FOPOST_API_KEY": "your-api-key" }
}
}
}
```
### References
- This block as markdown: https://fopost.com/agents/zed/agent.md
- Every client: https://fopost.com/agents
- Docs: https://fopost.com/docsOne entry
A url and nothing else. No key in the file.
Sign in, not a key
Zed opens FoPost in the browser to approve access.
Two checks
Zed confirms tool calls, and publishing needs your approval too.
Add the server, then sign in
Open Settings, then AI, then MCP Servers, and choose Add Remote Server. Or add the entry to settings.json. Zed asks you to authenticate; sign in to FoPost when the browser opens.
Start free{
"context_servers": {
"fopost": { "url": "https://api.fopost.com/mcp" }
}
}Settings or file
Add it in the UI or in settings.json.
No key in the config
You sign in instead of pasting a key.
Check first
A green dot means the server is active.
Announce the release from the editor
Ask the agent to read the changelog, shape a post for each network with draft_post_variants, and book them with get_queue_slots. It ends with propose_publish, which you accept.
Plan your week
draft_post_variants
A version for each network.
get_queue_slots
The next open times in your queue.
propose_publish
You approve before anything goes out.
Ask whether it landed
The read tools report what published, which accounts need a reconnect, and what is waiting in the inbox.
Start free> Did the release post go out?
list_posts shows 3 of 3 published.
list_inbox has 2 new replies.list_posts
Recent posts and their status.
get_account_health
Which accounts need a reconnect.
list_inbox
Comments, mentions, and messages.
No browser on the machine?
On a server or in CI there is no browser to sign in with. Create an API key in the dashboard and run the local package over stdio instead. Keep the key out of your repository.
{
"context_servers": {
"fopost": {
"command": "npx",
"args": ["-y", "@fopost/mcp"],
"env": { "FOPOST_API_KEY": "your-api-key" }
}
}
}Zed questions, answered
Do I need an API key?
Why does Zed ask before each tool call?
Will it post without asking?
What if the dot is not green?
Does it use my AI credits?
Other agents
- MCP Server
- Claude Code
- Claude
- Claude Desktop
- Claude Cowork
- Cursor
- Codex
- ChatGPT
- Windsurf
- Gemini CLI
- Grok
- Hermes Agent
- OpenClaw
- Muse
- Kimi Code
- DeepSeek Harness
- goose
- VS Code
- Warp
- Amp
- OpenCode
- LM Studio
- Gemini
- Perplexity
- Perplexity Computer
- Manus
- Mistral Vibe
- GitHub Copilot
- Cline
- Junie
- Continue
- OpenAI dots
- Claude Duet
- Grok Build
- NanoClaw
- Paperclip
- Raycast
Run FoPost from Zed
Starting is free and the MCP server is included. Paste the setup line into your agent, sign in, and schedule your first post from it.
Start free