Use Spekkr specs in Amp

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

2 minutes to read

Add the server

Amp stores a URL server in amp.mcpServers. That is local configuration even when the URL is on another machine. Add Spekkr from a terminal:

amp mcp add spekkr https://spekkr.com/mcp

Or add the entry to ~/.config/amp/settings.json. A project file is .amp/settings.json. A workspace server waits for approval before it runs. amp mcp approve spekkr approves it. A server in the user file does not ask.

"amp.mcpServers": {
  "spekkr": {
    "url": "https://spekkr.com/mcp"
  }
}

When you start the terminal UI after adding a URL, Amp opens the server's sign-in page. Spekkr does not require a token to search, read or pull. Publishing uses Spekkr's emailed code.

Checked 20 November 2026. Amp'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.