Add the server
OpenCode adds a remote server, which is Streamable HTTP, with one command. That writes the project config. --global writes it for every project. opencode mcp list shows what is connected.
opencode mcp add spekkr --url https://spekkr.com/mcp
opencode mcp add spekkr --url https://spekkr.com/mcp --global
The current config puts the server under mcp.servers. type is remote, and url is an absolute URL. The file is opencode.json or opencode.jsonc.
{
"mcp": {
"servers": {
"spekkr": {
"type": "remote",
"url": "https://spekkr.com/mcp"
}
}
}
}
OAuth is on by default. If the list says the server needs authentication, /mcps starts sign-in. Spekkr does not require a token to search, read or pull. Publishing uses Spekkr's emailed code, which is a separate step.
Checked 20 November 2026. OpenCode'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.