> ## 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.

# Use Revilico from AI apps with the MCP server

> Let AI apps such as Claude, ChatGPT and Claude Code run Revilico engines for you

Revilico runs a remote [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server. Add it to an AI app and the app can browse engines, upload molecules, start runs, follow them and read their results, all from a conversation.

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

## Connect an app

> **[Claude](https://docs.revilico.bio/developers/mcp/claude.md)**
>
> Claude on the web and desktop, and Claude Code.

> **[ChatGPT](https://docs.revilico.bio/developers/mcp/chatgpt.md)**
>
> ChatGPT on the web.

> **[Other apps](https://docs.revilico.bio/developers/mcp/api-key.md)**
>
> Any MCP client, with OAuth or an API key.

The web app shows the same steps: open your account, click **Developer**, go to the **Connected apps** tab and click **Connect an app**.

## How signing in works

You don't need an API key. When you add the server, the app opens Revilico in your browser:

1. Sign in to Revilico as usual.
2. Review the app's request. Revilico shows the app's name, and marks it **Unverified** if it isn't an app Revilico recognizes. Only allow an unverified app if you just added it yourself.
3. Under **Allow it to**, untick anything you don't want the app to do, then click **Allow**.

The app then acts as you, with only the permissions you allowed. It sees what you see in the web app, and runs it starts use your organization's credits and appear in your Command Center. You stay signed in until you disconnect the app or it goes unused for 30 days.

## Disconnect an app

Open your account, click **Developer** and go to the **Connected apps** tab. It lists every app you have connected, with its permissions and when it was connected and last used. Click **Disconnect** next to an app and confirm to sign it out immediately.

## What the app can do

The server offers 25 tools, grouped like the REST API. An app only sees the tools for the permissions you allowed. See the [tools reference](https://docs.revilico.bio/developers/mcp/tools.md) for each tool and its arguments.

| Area | Tools |
| - | - |
| Engines | `list_engines`, `get_engine`, `validate_parameters` |
| Files | `upload_file_content`, `create_upload`, `get_file` |
| Runs | `create_run`, `get_run`, `get_run_inputs`, `list_runs`, `cancel_run` |
| Results and outputs | `get_results`, `get_result_detail`, `list_run_files`, `read_run_file`, `list_outputs`, `get_output` |
| Projects | `list_projects`, `get_project`, `list_project_runs`, `create_project`, `add_run_to_project`, `remove_run_from_project` |
| Account | `get_credit_balance`, `get_usage` |

A typical session goes: `list_engines` → `get_engine` to read the parameters → `upload_file_content` for an input file → `create_run` → `get_run` until it finishes → `get_results`.

## Things to try

* "Which Revilico engines can I use?"
* "Compute the oxidation and reduction potentials of phenothiazine with RevRedox."
* "Find the low-energy conformers of these five SMILES with RevConformer and summarize them."
* "Show the results of my last run and explain what the numbers mean."
* "How many credits have my runs used this month?"

> [!WARNING]
>
> Runs take minutes to hours and spend your credits. The server asks apps to confirm parameters with you before starting a run, but check what the app proposes before you agree, especially for large batches.

## Long-running runs

Runs don't finish within one chat reply. Ask the app to check on a run later ("Is my RevRedox run done?"), or come back to the conversation; the run keeps going on Revilico either way. You can also follow it in the web app's Command Center.


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