Add the server
Kiro reads .kiro/settings/mcp.json for the workspace and ~/.kiro/settings/mcp.json for every workspace. The workspace file wins when both name the same server. The command palette opens either file: Kiro: Open workspace MCP config (JSON), or Kiro: Open user MCP config (JSON). The Kiro panel has an Open MCP Config icon. A remote server is a url. HTTPS is required, except for localhost.
{
"mcpServers": {
"spekkr": {
"url": "https://spekkr.com/mcp"
}
}
}
Save the file and Kiro reconnects. Spekkr needs no headers for search, read or pull. Enable MCP support in Settings if the servers do not load: search for MCP and turn the setting on.
Checked 20 November 2026. Kiro'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.