Skip to content

Get started

Ways to connect

Four ways in, from pasting a URL to running a command line. All four reach the same tools, with the same permissions.

Which one to use

  • Your app can add a connector or a remote MCP server: use the URL and sign in. Most apps can.
  • Nobody is there to click Allow, as with a script, a server or a scheduled job: use an API key.
  • Your app only starts MCP servers on your machine: run the CLI's stdio bridge.
  • Your agent works in a terminal and uses skills: install the CLI and the Agent Skill.

1. Connector URL and sign in

Your app talks to SPREVA over MCP's Streamable HTTP and signs you in with OAuth. There is no key to copy or keep safe: you choose the workspace on SPREVA's own page, and you can disconnect the app at any time.

URL
https://app.spreva.ai/api/mcp
  1. 1

    Paste the URL where your app adds a connector or an MCP server.

  2. 2

    Your app opens SPREVA. Sign in, choose the workspace and click Allow.

  3. 3

    What agents may do on their own is up to you in SPREVA, under Agents, where you can also disconnect each app.

Recommended. It works in Claude, ChatGPT, Cursor, Claude Code, Codex, Gemini CLI, Kimi CLI and most apps that add MCP servers by URL.

2. API key in a header

For automation that runs without a person, and for apps that cannot sign in with OAuth. Create a key in SPREVA under Developer, then API keys, and send it as a Bearer token:

Header
Authorization: Bearer spreva_sk_...

Most apps take it in their JSON configuration.

JSON
{
  "mcpServers": {
    "spreva": {
      "type": "http",
      "url": "https://app.spreva.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer spreva_sk_..."
      }
    }
  }
}
A key belongs to one workspace, and anyone who has it can act there. Keep it out of shared files and repositories, and revoke it when you no longer need it.

3. The CLI's stdio bridge

Some apps only start MCP servers on your own machine, over stdio. spreva mcp is such a server: it runs locally, reads your API key from SPREVA_API_KEY and passes every call on to SPREVA.

JSON
{
  "mcpServers": {
    "spreva": {
      "command": "npx",
      "args": [
        "-y",
        "@spreva/cli",
        "mcp"
      ],
      "env": {
        "SPREVA_API_KEY": "spreva_sk_..."
      }
    }
  }
}

It needs Node.js 20 or later. The tools, answers and permissions are the same as through the URL.

4. The CLI and the Agent Skill

Agents that work in a terminal, such as OpenClaw, Hermes Agent, Claude Code and Codex, can use SPREVA as a command line. The Agent Skill tells them when to reach for it and how.

  1. 1

    Install the CLI:

    Terminal
    npm i -g @spreva/cli
  2. 2

    Give it your API key:

    Terminal
    export SPREVA_API_KEY=spreva_sk_...
  3. 3

    Install the skill for your agent. The targets are claude, codex, openclaw, hermes and agents, for any other agent that supports skills:

    Terminal
    spreva skill install --target claude
  4. 4

    Check that everything is in place:

    Terminal
    spreva doctor

More in CLI and Agent Skill.