---
title: "Connect Zed to 1Post over MCP"
url: "https://get1post.com/assistants/zed.md"
canonical_url: "https://get1post.com/assistants/zed"
last_updated: "2026-10-26"
type: "how-to"
summary: "Add the 1Post MCP server to Zed: the exact settings, how to sign in or use a key, and a request and reply to check it works."
related: ["https://get1post.com/assistants.md", "https://get1post.com/docs/mcp.md", "https://get1post.com/docs/mcp-oauth.md", "https://get1post.com/docs/api-authentication.md"]
---

# Connect Zed to 1Post over MCP

Add the 1Post MCP server to Zed: the exact settings, how to sign in or use a key, and a request and reply to check it works.

Connect Zed to 1Post by adding the MCP server at https://api.get1post.com/v1/mcp with your API key, or at https://api.get1post.com/v1/mcp/oauth to sign in. Zed then lists your accounts, schedules posts and reads results with your role. The steps and the exact Zed settings are below; actions that cancel or reply need confirmation.

## Set up Zed

1. Open settings. Open the Zed settings file.
2. Add the server. Add the entry below under context_servers. With an Authorization header Zed uses the key; with none, Zed starts the sign-in flow when you connect to https://api.get1post.com/v1/mcp/oauth.
3. Check the connection. Open the agent panel and ask it to list your 1Post accounts.

## The Zed settings

**settings.json**

```json
{
  "context_servers": {
    "1post": {
      "url": "https://api.get1post.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer op_live_YOUR_KEY"
      }
    }
  }
}
```

Leave the headers out and use the sign-in address to be asked to authenticate instead of storing a key.

## A request and its reply

Once connected, Zed sends tool calls like this one when you ask it to schedule a post. Account ids come from list_accounts.

**Tool call**

```json
{
  "name": "create_post",
  "arguments": {
    "accounts": [
      "ACCOUNT_ID"
    ],
    "text": "Doors open at nine.",
    "schedule_at": "2026-11-02T15:00:00Z"
  }
}
```

**Reply, abridged**

```json
{
  "id": "POST_ID",
  "status": "scheduled",
  "scheduled_at": "2026-11-02T15:00:00.000Z",
  "accounts": [
    {
      "account_id": "ACCOUNT_ID",
      "status": "queued"
    }
  ]
}
```

## What the connection can do

| Tool | What it does | Needs |
| --- | --- | --- |
| list_accounts | Lists connected accounts and their state | Read |
| create_post | Saves, schedules or publishes a post | Write |
| get_post | Reads one post and the result for each account | Read |
| cancel_post | Cancels a post that has not started | Write and confirm: true |

The connection acts with the role of the member who made the key or signed in, so a contributor's posts still go to review. The full tool list is on the [MCP page](https://get1post.com/docs/mcp.md).

## Questions

**How do I sign in instead of using a key?**

Point the entry at https://api.get1post.com/v1/mcp/oauth and leave out the headers. Zed asks you to authenticate.

**What can Zed do once it is connected?**

It can list your accounts, create and update posts, read results and analytics, and cancel or reply when you confirm. It cannot do more than the member behind the key or sign-in.

## Sources

- [Zed documentation: Model Context Protocol](https://zed.dev/docs/ai/mcp), read 2026-10-26

## Related

- [Connect an assistant to 1Post over MCP](https://get1post.com/assistants.md)
- [The MCP server: 1Post docs](https://get1post.com/docs/mcp.md)
- [MCP sign-in with OAuth: 1Post docs](https://get1post.com/docs/mcp-oauth.md)
- [API authentication and keys: 1Post docs](https://get1post.com/docs/api-authentication.md)