| Where | Works with Relm | What you do |
|---|---|---|
| grok.com in your browser | Yes | Add a custom connector and sign in |
| Grok command-line tool | Yes | Run one command with your API key |
| xAI API | Yes | Pass Relm as a remote MCP tool with a key |
On grok.com you sign in with your Relm account. The command-line tool and the API use a Relm API key. See Create an API key.
In the browser: grok.com
- Go to grok.com/connectors.
- Select New Connector, then Custom.
- Enter the URL
https://api.relm.ai/mcp/. - Grok opens Relm's sign-in page: sign in, choose the workspace Grok may use, and approve access.
Grok then lists Relm's tools and can use them in your conversations. It can do what a Read & write key can, in the workspace you chose; runs that spend credits still ask you to confirm. On Grok Business and Enterprise, a team admin may first need to add Relm as a connector in the xAI console before members can connect it. xAI's guide: Connectors.
In the terminal: Grok command-line tool
Put your key in an environment variable, then add Relm:
export RELM_API_KEY=relm_sk_...
grok mcp add --transport http relm https://api.relm.ai/mcp/ --header "Authorization: Bearer ${RELM_API_KEY}"
You can also leave out the header and sign in with Relm the first time Grok uses it. xAI's guide: MCP servers.
From your own code: xAI API
Pass Relm as a remote MCP tool and send your key in headers:
{
"type": "mcp",
"server_url": "https://api.relm.ai/mcp/",
"server_label": "relm",
"headers": { "Authorization": "Bearer relm_sk_..." }
}
xAI's servers call Relm directly, so the key must be valid when the request runs. xAI's guide: Remote MCP tools.