Docs

Pull, check and publish

Three ways an agent meets a spec: the line on its page, the MCP server, and the page where a spec is published by hand.

Pull a spec

  1. Open the spec from the catalog and set anything under "What can I customize?".
  2. Copy the line. It reads like Build the spec at https://spekkr.com/juno/waitlist/start.md. The address is that spec's start note.
  3. Paste it to an agent that can open a web address. The note tells the agent to fetch the files, record your choices and build. Nothing is installed, and no account is needed.

The same thing with the MCP server connected is the pull_spec tool. choices holds what you changed; anything left out keeps the spec's default.

Check a spec

check_spec reads a spekkr.json you are writing and names every problem at once. Nothing is saved. The page about publishing runs the same check as you write, and does not keep the listing.

A spec that is ready to publish also has to name your username, send every file the manifest lists, and keep screenshots to png, jpg, gif, webp or avif. The limits are on Pricing.

Publish a spec

With an agent connected, from the spec's folder: Publish this spec on Spekkr. The agent checks the manifest with check_spec, then publishes with publish_spec. The first time, a page opens in your browser: sign in with the code sent to your email address, pick a username, and allow the agent to publish as you.

Or with no agent, on the publish page: drop the folder, write what needs writing, and press Publish. The files stay on your computer until you publish.

A small text file goes inside the call. An image, a document or any other large file is announced with its size, then sent with HTTP PUT to an address the tool gives, and publish_spec is called again. A published version never changes. To update a spec, raise version, add a changelog entry and publish again. unpublish_spec takes one of yours down.

MCP tools

The server is at https://spekkr.com/mcp. It uses the Streamable HTTP transport. Searching and pulling need no sign-in. A tool that acts for a person asks the agent to sign in first.

In a browser that has WebMCP, the pages offer the same tools to an agent in that browser. Nothing is connected first. Before a page publishes or takes a spec down, it asks you.

Connect an agent

Add the MCP address once. The same agent can then search, pull and publish.

Claude Code

Run this in a terminal:

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

Codex

Run this in a terminal:

codex mcp add spekkr --url https://spekkr.com/mcp

Cursor

Add this to ~/.cursor/mcp.json:

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

VS Code

Run this in a terminal:

code --add-mcp '{"name":"spekkr","type":"http","url":"https://spekkr.com/mcp"}'

Other agents

Add this address in your agent's MCP settings as a remote server. It uses the Streamable HTTP transport and needs no key.

https://spekkr.com/mcp