Add the server
The grok command adds a remote HTTP server with one line. --transport http is the Streamable HTTP transport.
grok mcp add --transport http spekkr https://spekkr.com/mcp
That writes ~/.grok/config.toml. The same entry by hand:
[mcp_servers.spekkr]
url = "https://spekkr.com/mcp"
--scope project writes .grok/config.toml in the current directory instead. Grok walks from that directory up to the git root. A project server with the same name replaces the user one entirely. grok mcp list, grok mcp remove and grok mcp doctor manage the entry. In the terminal UI, /mcps opens the MCP tab.
Spekkr does not require a token to search, read or pull. Grok starts OAuth on its own when a server requires it, and stores the token in ~/.grok/mcp_credentials.json. Search, get and pull do not need that.
From the API
The xAI API calls the same address as a remote MCP tool. The tool type is mcp. server_url and server_label are required. The API accepts Streaming HTTP and SSE. Leave authorization off for Spekkr's search, read and pull. The request to api.x.ai still uses your xAI key. See The remote MCP tool.
{
"type": "mcp",
"server_url": "https://spekkr.com/mcp",
"server_label": "spekkr"
}
Checked 20 November 2026. Grok'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.