For spec writers
Publish a spec
If you have specified something well enough for an agent to build it, other people's agents can build it too. Publish it from this page, or have your agent publish it for you.
Publish it from this page
Drop the spec's folder here, or choose it. You see its files, can write the text and the listing, and publish. The files stay on this computer until you press Publish. Spekkr checks the listing, spekkr.json, as you write it, and does not keep it.
With your agent, in three steps
- Write the spec. A folder with a
spekkr.jsonand the files it lists. The example below shows the shape. - Connect your agent to Spekkr. Pick your agent under Connect your agent. It takes one command.
- Tell it to publish. In the spec's folder, say:
Publish this spec on Spekkr.
The first time, a Spekkr page opens in your browser. You sign in with a code sent to your email address, pick a username, and allow the agent to publish as you. The spec is then listed as username/name, with a page of its own and a line anyone can paste to build it.
What a spec is
A folder an AI agent can build from without asking you anything. The specs Spekkr writes hold a manifest and three files:
booking-page/
spekkr.json what it covers, what a person may change, what it needs
spec.md requirements, each with an acceptance test
design.md data model, rules and flows
tasks.md build steps in order, each with a check
shots/home.png a screenshot of a build, shown on the page and on its card
Yours can be laid out differently, and can hold images, documents and recordings as well as text.
The manifest
spekkr.json describes the spec: what it builds, what a person may change and stay on the tested path, which files it holds, and which commands and secrets the build uses. This one is complete:
{
"spekkr": 1,
"id": "your-username/booking-page",
"name": "Booking page",
"summary": "A page where customers book a time slot and pay a deposit.",
"keywords": ["appointments", "scheduling", "calendar"],
"version": "1.0.0",
"author": { "id": "your-username", "name": "Your Name" },
"targets": { "platforms": ["web"], "stack": ["TypeScript"] },
"customize": {
"settings": [{ "key": "business", "label": "Business name", "default": "Acme" }],
"options": [{ "key": "deposits", "label": "Take a deposit", "default": true }],
"swaps": [{
"key": "database", "label": "Database",
"choices": ["postgres", "sqlite"], "default": "postgres"
}]
},
"files": [
{ "path": "spec.md", "about": "Requirements, each with a test." },
{ "path": "design.md", "about": "Data model and flows." },
{ "path": "tasks.md", "about": "Build steps in order." }
],
"needs": { "accounts": ["A payment provider"], "permissions": ["shell", "network"] },
"demo": { "screenshots": ["shots/home.png"] },
"safety": { "commands": ["npm install", "npm test"], "secrets": ["DATABASE_URL"] },
"changelog": [{ "version": "1.0.0", "date": "2026-11-13", "note": "First version." }]
}
You do not have to get it right by hand. Before it publishes, your agent checks the manifest with Spekkr's check_spec tool, which names every problem at once.
Good to know
- A spec need not be for software. Say what it builds with
"kind", in your own words:CAD,circuit design,animation, anything. People filter the catalog by it. Left out, it means software, and only a software spec has to name a platform. - Its page says your account published it.
- A published version never changes. To update a spec, raise
version, add achangelogentry and publish again. Files that did not change are kept without being sent again. - A spec can hold files of any kind. A file can be up to 25 MB and a spec up to 100 MB, in up to 500 files.
- To take a spec down, ask your agent to unpublish it.
- A draft you put together on this page is kept in your browser, on your computer. Its files are sent to Spekkr only when you publish. The listing,
spekkr.json, is sent to be checked as you write it, and Spekkr does not keep it.
Connect your agent
Publishing goes through Spekkr's MCP server. Connect once and the same agent can also search the specs and pull one by name.
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