# MCP for Zed

> Connect Zed to SiberMate via a custom context server running the SiberMate npm bridge (Zed has no stable remote-URL MCP field yet).

Last updated: 2026-06-15

## Server URLs

- Default remote MCP URL: `https://mcp.sibermate.com/mcp`
- Multi-tenant profile URL: `https://mcp.sibermate.com/profile/{YOUR TENANT DOMAIN}/mcp`
- Example profile URL: `https://mcp.sibermate.com/profile/sibermate.com/mcp`

## Setup Notes

- Open Zed settings.json (or .zed/settings.json) and add SiberMate under context_servers.
- Zed connects over stdio; run the SiberMate npm bridge as the command with your API key in env.
- For a purely remote setup, bridge the URL with npx mcp-remote.

## Authentication

- Recommended remote flow: OAuth discovery from the MCP server URL.
- Bearer fallback: use `Authorization: Bearer <SIBERMATE_API_KEY>` only when the client supports custom headers.
- Local stdio fallback: `npx -y @sibermatedev/mcp` with `SIBERMATE_API_KEY` in the client environment.

## Zed settings.json

```
{
  "context_servers": {
    "sibermate": {
      "source": "custom",
      "enabled": true,
      "command": {
        "path": "npx",
        "args": ["-y", "@sibermatedev/mcp"],
        "env": {
          "SIBERMATE_API_KEY": "..."
        }
      }
    }
  }
}
```

## Safety Checklist

- Use a dedicated tenant API key for MCP setup.
- Keep API keys out of prompts, screenshots, repositories, browser history, and shared docs.
- For profile URLs, the domain in the URL must match the tenant returned by the API key.
- Review generated action plans before sending assignments, reminders, removals, uploads, or deletions.

Related docs:

- https://docs.sibermate.com/mcp
- https://docs.sibermate.com/api-reference.md
- https://api.sibermate.com/v1/openapi.json