# Zed MCP: Add PostEverywhere as a Context Server

**Source:** https://posteverywhere.ai/connectors/zed

---

# Add PostEverywhere to Zed as a context server

Yes, with one wrinkle: Zed nests the block under context_servers rather than mcpServers.

Zed supports the Model Context Protocol, but it names the setting differently from every other client. The block goes under context_servers, not mcpServers, and it lives in your normal Zed settings file rather than a dedicated MCP config.

That one key is the whole difference. Copy a config from a Claude or Windsurf guide unchanged and Zed will silently ignore it, which is the most common reason people think the server is broken when it was never registered.

Everything else about the setup is standard, which is precisely why the one difference catches people. The fields, the command and the environment variable are identical to every other client; only the section name changes.

[Start your 7 day trial](https://app.posteverywhere.ai/signup)[All connectors →](https://posteverywhere.ai/connectors)Card required · $0 charged today · cancel any time

## How to connect PostEverywhere to Zed

One key name is the only thing that differs from every other MCP client, and it is the thing that catches people.

Before you start

- Zed installed, and comfort editing settings.json by hand.
- Node on your PATH for the npx-launched server.
- A PostEverywhere API key and at least one authorised social account.
~/.config/zed/settings.jsonjson`{
  "context_servers": {
    "posteverywhere": {
      "command": "npx",
      "args": ["-y", "@posteverywhere/mcp"],
      "env": { "POSTEVERYWHERE_API_KEY": "pe_live_YOUR_KEY" }
    }
  }
}`

- 1Get an API key from your PostEverywhere account. The same key works for the REST API and the SDK.

- 2Add the block below to ~/.config/zed/settings.json.

- 3Restart Zed. The 33 tools appear once it reloads its MCP configuration.

**Worth knowing:** If you copied a config from a Claude or Cursor guide, change mcpServers to context_servers. That single word is usually the whole problem.

## What you can ask Zed once it is connected

Zed is a good fit when you want the announcement to happen in the same place as the work, with no browser involved. Each one maps onto a real tool, covering scheduling, [AI captions](https://posteverywhere.ai/ai-content-generator) and [analytics](https://posteverywhere.ai/social-media-analytics). The [AI agents page](https://posteverywhere.ai/agents) has the full surface.

Publish a release note from the editor you wrote it in

Draft a changelog post while the diff is still on screen

Queue a set of updates for the week ahead

Check what is scheduled before you add more

Shift a post that clashes with a launch

Retry a failed post and see the error

The assistant in Zed gains the publishing tools, so a changelog entry can go from written to scheduled without another application being opened.

### What the tools cover

The context server exposes all 33 tools, identical to the hosted connector. Scheduling and cross-posting cover most use, with analytics and account health available when you want to know whether last week landed or why something failed. Nothing is held back from the local path.

### Prompts that work, and what comes back

“Write a changelog post from the diff I am looking at and schedule it for tomorrow.”

The assistant drafts from the change in front of you and queues the post.

“What is scheduled for this week across all accounts?”

It reads back the queue with dates and accounts, so nothing lands twice.

“Rewrite this post to be shorter and reschedule it for Friday.”

It edits the queued item in place rather than creating a second copy.

## Zed MCP troubleshooting

The three things that actually go wrong, and what fixes each one.

The server is silently ignored

The key is wrong. Zed reads context_servers, and a block under mcpServers is skipped without any error at all, which is why this looks like a broken server rather than a typo.

settings.json will not save

Zed validates the whole settings file, so an error anywhere in it blocks the save. Fix the reported line first, then add the server block.

The server starts but has no tools

Check the API key value. An expired or mistyped key lets the process start and then fail every call, which reads as an empty tool list.

## What it will not do

Worth knowing now rather than after you have started a trial.

- A block under mcpServers will be ignored. Zed reads context_servers and gives no error for the wrong key.
- The server runs with Zed. Anything already queued publishes from our side regardless.
- It does not handle replies or direct messages, only publishing and performance.

## When to use Zed rather than another editor

Zed suits someone who wants a fast editor and is happy editing settings by hand. If you already keep your Zed configuration deliberate, this is one more block in a file you know.

Reference material: [Zed's MCP documentation](https://zed.dev/docs/ai/mcp), [The Model Context Protocol spec](https://modelcontextprotocol.io). The full agent surface, including the REST API, is on the [AI agents page](https://posteverywhere.ai/agents).

## Included on every paid plan from $9/mo

The server is open source and free to run. The API key needs a PostEverywhere plan, from $9 a month. One key covers the connector, the [REST API](https://posteverywhere.ai/social-media-api) and the SDK. Not using Zed? [See all connectors](https://posteverywhere.ai/connectors), wire it up from [n8n, Make or Zapier](https://posteverywhere.ai/integrations), or read how the whole [agent setup](https://posteverywhere.ai/agents) fits together.

[Start your 7 day trial](https://app.posteverywhere.ai/signup)

## Zed MCP FAQ

### How do I connect PostEverywhere to Zed?

Get an API key from your PostEverywhere account. The same key works for the REST API and the SDK. Then: Add the block below to ~/.config/zed/settings.json. Then: Restart Zed. The 33 tools appear once it reloads its MCP configuration. There is no plan restriction on this client.

### Can Zed post to social media?

Yes, with one wrinkle: Zed nests the block under context_servers rather than mcpServers. Zed is a good fit when you want the announcement to happen in the same place as the work, with no browser involved.

### Why is my MCP server not appearing in Zed?

Almost always the key name. Zed uses context_servers where every other client uses mcpServers. A config copied unchanged from another guide will be ignored without an error.

### Where does the Zed config live?

In your normal settings file at ~/.config/zed/settings.json, not a separate MCP config. Add context_servers alongside your other settings.

### Is this the hosted server or the local one?

Local. Zed runs the open-source server through npx with an API key. The hosted OAuth connector is for Claude, ChatGPT, Grok and Cursor, and both give you the same 33 tools.

### What does it cost to use Zed this way?

The server is open source and free to run. The API key needs a PostEverywhere plan, from $9 a month. Every plan has a 7-day trial and a card is required to start it.

## Other assistants

[Claude](https://posteverywhere.ai/connectors/claude)[ChatGPT](https://posteverywhere.ai/connectors/chatgpt)[Cursor](https://posteverywhere.ai/connectors/cursor)[Claude Code](https://posteverywhere.ai/connectors/claude-code)[Grok](https://posteverywhere.ai/connectors/grok)[Windsurf](https://posteverywhere.ai/connectors/windsurf)[Cline](https://posteverywhere.ai/connectors/cline)[Codex CLI](https://posteverywhere.ai/connectors/codex-cli)