Use Spekkr specs in Zed

Connect Zed to Spekkr's MCP server, then search, pull and build a spec.

2 minutes to read

Add the server

In Zed, open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. Or add the server to your settings JSON. The key is context_servers, and the field is url.

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

When a remote server has no Authorization header, Zed asks you to authenticate with the MCP OAuth flow. Spekkr does not require a token to search, read or pull. Publishing, unpublishing and whoami use Spekkr's emailed code, which is separate from that prompt.

Checked 20 November 2026. Zed's MCP docs.

Without connecting

An agent that can open a web address does not need the server. Paste one line. The address is that spec's start note.

Build the spec at https://spekkr.com/juno/waitlist/start.md.

juno/waitlist is a waitlist spec. The note tells the agent to fetch the files, record the choices and build.

Search, then pull

With the server connected, paste this:

Search Spekkr for a waitlist spec, then pull juno/waitlist with database=sqlite.

Spekkr tells the agent to search with search_specs, read get_spec, then call pull_spec with the person's choices. Write the files into a folder and follow BUILD.md.

juno/waitlist lists database as postgres or sqlite. The default is postgres, so the prompt sets sqlite. A choice the spec does not offer is refused. Anything left out keeps the spec's default.

Search, get and pull need no sign-in. Publishing, unpublishing and whoami do: the agent opens a Spekkr page, and Spekkr emails a code. There is no password. Questions: support@spekkr.com.

The other tools, and the limits, are on the docs page. Every agent is listed on the setup index.