Connect an agent

Let your agent set itself up

Paste this line into an agent that can run commands. It reads the public setup guide, runs the setup and asks you to approve access in your browser.

Set up https://app.relvo.si/SKILL.md

Claude Code and Codex

On macOS or Linux with Node.js 22 or later, one command connects every installed Claude Code and Codex client, installs Relvo’s workflow skills and saves your login.

npx --yes @relvo/cli setup \
  --api-url https://api.relvo.si \
  --console-url https://app.relvo.si

1. Keep it running while you open the link it prints, compare the code, choose a project and approve.
2. Every permission is selected by default, including execution, which spends your team’s balance. Untick any you do not want before approving.
3. Add --client claude, --client codex or --client terminal (CLI only) to set up one client.
4. Run the same command again to resume an interrupted setup.

Restart the agent, then check the connection:

npx --yes @relvo/cli doctor

Remote MCP with sign-in

Clients that support remote MCP connect to https://app.relvo.si/mcp and sign in through your browser. No API key or local install is needed. In Claude (web and desktop) and ChatGPT, add the URL as a custom connector. Command-line agents register the URL and sign in:

claude mcp add --transport http --scope user relvo https://app.relvo.si/mcp
codex mcp add relvo --url https://app.relvo.si/mcp
codex mcp login relvo

On the consent screen you choose the project, the scopes and which connections, custom tools and skills the client may use. A sign-in lasts 90 days.

Other MCP clients

Clients without browser sign-in send a project API key in a header. Create a key in API keys ↗ and replace YOUR_RELVO_API_KEY.

{
  "mcpServers": {
    "relvo": {
      "url": "https://app.relvo.si/mcp",
      "headers": { "Authorization": "Bearer YOUR_RELVO_API_KEY" }
    }
  }
}

To list specific catalog tools as their own MCP tools, add ?tools= with up to 20 names, for example https://app.relvo.si/mcp?tools=web_search,serp_lookup. The client’s access follows the permissions attached to its credentials.

Discover, then inspect

Ask the client to read your Relvo project and search the available tools without running a paid one. Choose an action, inspect its input schema and provide the required fields.

Describe the intended outcome clearly. For actions that change external data, review the target and inputs before approving a run.

Follow your first request

Keep the returned execution ID. If the tool is still working, follow its progress until a result or error is available.

See Running tools for result handling, MCP server & CLI for the server’s tools, and Troubleshooting if the client cannot discover or call a tool.