Zed

Zed calls MCP servers "context servers", and its agent can use remote ones by address. Hamloy has not been tested in Zed; the steps below were checked against Zed's own docs on 10 October 2026.

What you need

• A Hamloy account and a project. Create a free board if you have none.
• Zed, with its agent turned on.

Connect

In Zed, open Settings › AI › MCP Servers, choose Add Server, then Add Remote Server. Zed writes the server into your settings under context_servers. The entry for Hamloy is:

{
  "context_servers": {
    "hamloy": {
      "url": "https://hamloy.com/mcp"
    }
  }
}

You can also paste it into Zed's settings.json yourself, beside any servers already there.

Leave out headers. Zed's docs say that without an Authorization header Zed asks you to sign in through the standard MCP OAuth flow. Your browser opens on Hamloy and asks whether to let Zed in. Choose Allow. No key is needed.

https://hamloy.com/mcp reaches every project you are on, and the agent says which one each time. For one project only, use its own address from Hamloy's Connect page.

Check that it worked

In Settings › AI › MCP Servers, the dot beside hamloy turns green, with the tooltip "Server is active".

Then ask Zed's agent "What's open in Hamloy?" It calls the list tool:

Pebble · 3 open, 0 done
backlog
  [ ] B-k3f9@1   Streak counter on the habit card
requests
  [ ] R-q4ve@1   Create an Apple developer account
questions
  [ ] Q-7hnc@1   How should a shared streak look?  options: 1) A square card (recommended)  2) A story-sized image

On a new project the reply is Pebble · 0 open, 0 done and (nothing to show). Give the agent real work and it writes the plan into Hamloy, claims the task it starts, and asks you what only you can decide.

With a token instead

If the sign-in doesn't work from your computer, make an API token on Hamloy's Connect page and send it as a header:

{
  "context_servers": {
    "hamloy": {
      "url": "https://hamloy.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

Zed's settings file is yours, not the repo's, so the token stays out of the repo. Don't put it in a project's .zed/settings.json that the repo keeps.

If it doesn't work

• The dot isn't green. Hover over it: the tooltip says what is wrong. Check the address is exactly https://hamloy.com/mcp.
• No sign-in prompt. Take out any headers from the entry; with an Authorization header Zed sends that instead of signing in.
• The browser window says "This link doesn't work." Hamloy doesn't know the app that sent you. Remove the server in Zed, add it again, and sign in again.
• You want to cut the connection. Hamloy's Connect page lists Zed under Connected apps, with Disconnect.

How Hamloy works with every app: Client compatibility.