Skip to main content
The Revilico MCP server works with any client that supports remote MCP servers over Streamable HTTP:

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 instead, sent as a header:
The key’s scopes decide which tools the client sees. A Read only key gives an agent tools to browse and read but not to start runs.
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

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.

Check the connection

The MCP Inspector lists the server’s tools and lets you call them:
Choose Streamable HTTP, enter the URL, and add the Authorization header (or connect with OAuth).