> ## Documentation Index
> Fetch the complete documentation index at: https://docs.revilico.bio/llms.txt
> Use this file to discover all available pages before exploring further.

# Other apps and API keys

> Connect any MCP client to the Revilico MCP server over Streamable HTTP, with OAuth sign-in or an API key, and check the connection with MCP Inspector.

The Revilico MCP server works with any client that supports remote MCP servers over **Streamable HTTP**:

```text theme={null}
https://mcp.revilico.bio/mcp
```

## Clients that support OAuth

Most desktop and IDE clients can sign in with OAuth. Add a remote MCP server with the URL above; when the client asks you to sign in, sign in to Revilico and click **Allow**. Revilico supports dynamic client registration, so you don't need a client ID.

## Clients that use an API key

Some clients can't sign in through a browser, such as agents on a server, scripts and CI. Give them an [API key](https://docs.revilico.bio/developers/authentication.md) instead, sent as a header:

```text theme={null}
Authorization: Bearer rvl_live_…
```

The key's [scopes](https://docs.revilico.bio/developers/authentication.md#scopes) decide which tools the client sees. A **Read only** key gives an agent tools to browse and read but not to start runs.

> [!WARNING]
>
> Anyone with the key can act as you and spend your credits. Keep it out of shared config files and repositories, and revoke it when you no longer need it.

### Claude Code

```bash theme={null}
claude mcp add --transport http revilico https://mcp.revilico.bio/mcp \
  --header "Authorization: Bearer $REVILICO_API_KEY"
```

### JSON configuration

Many clients read servers from a JSON file in this shape. Check your client's documentation for the file's location and how it reads environment variables.

```json theme={null}
{
  "mcpServers": {
    "revilico": {
      "url": "https://mcp.revilico.bio/mcp",
      "headers": {
        "Authorization": "Bearer rvl_live_…"
      }
    }
  }
}
```

### Check the connection

The [MCP Inspector](https://modelcontextprotocol.io/docs/tools/inspector) lists the server's tools and lets you call them:

```bash theme={null}
npx @modelcontextprotocol/inspector
```

Choose **Streamable HTTP**, enter the URL, and add the `Authorization` header (or connect with OAuth).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.