Use Spekkr specs in Gemini CLI

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

2 minutes to read

Add the server

Gemini CLI adds a Streamable HTTP server with --transport http. Without that flag the command starts a local process.

gemini mcp add --transport http spekkr https://spekkr.com/mcp

The default scope is the project, which writes .gemini/settings.json. -s user writes ~/.gemini/settings.json and applies to every project.

gemini mcp add --transport http spekkr https://spekkr.com/mcp -s user

The HTTP streaming field is httpUrl. A url field is the older SSE transport.

{
  "mcpServers": {
    "spekkr": {
      "httpUrl": "https://spekkr.com/mcp"
    }
  }
}

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