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

# Use the Console over MCP

> Connect an MCP client such as a desktop assistant or an IDE to the Ravi Console, and read and change your projects, Pages and Bases as yourself.

At the end of this page an MCP client is connected to your organization's Console. It can list your projects and pages, read pages and Bases views, and add or change rows, always as you and only after you agree to each change.

You need a Console login (see [Log in to the Console](/console/login)).

## What the Console mode is

`mcp.ravi.so` serves two MCP servers on the same bridge URL. The plain one exposes tools from your local Ravi daemon. The **Console mode** exposes the Console's own operations: the same ones the [text chat](/console/pages#text-chat) of a page uses. Each person who connects signs in with their own Console account, and every tool runs as that person, with their memberships and project access. The client cannot do anything that person could not do in the Console.

## Connect a client

1. Create a bridge for a project, if you do not have one:

   ```bash theme={null}
   ravi bridges create --project website --name "Console" --json
   ```

   It prints an MCP URL like `https://mcp.ravi.so/<token>/mcp`. Treat the URL as a secret.
2. Point your MCP client at the same URL ending in `/console/mcp` instead of `/mcp`:

   ```json theme={null}
   { "mcpServers": { "ravi-console": { "url": "https://mcp.ravi.so/<token>/console/mcp" } } }
   ```
3. The client opens the Console to sign you in. By default it asks for read access (`mcp.console.tools.read`). The first time you ask for a change, the client asks you again for write access (`mcp.console.tools.write`).

`ravi bridges list` shows your bridges, and `ravi bridges revoke <id> --execute` turns one off together with every client token issued for it.

## Tools

The tools are the Console operations, named after the operation id with `_` instead of `.` (for example `ravi_bases_views_query`). Tools that work inside a project take a `project` argument, a slug or id; list them with the projects tool.

| You can | Kind |
| - | - |
| list projects, Pages sites and published pages | read |
| read a page's text | read |
| read a project's Pages theme | read |
| describe and query a Bases view, read a row, read chart data | read |
| add a row to a Base, change a row | write |

Reads run at once. There is a limit of 120 calls per minute for each person.

## Changes take two steps

A write tool never changes anything on its first call:

1. The client calls the tool. The answer is a preview of the change and a `confirmationToken`, and nothing has changed yet.
2. The client shows you the preview and asks whether to go ahead.
3. Only after you agree, it calls the same tool again with the same arguments plus the `confirmationToken`. The token is valid for 5 minutes and only for those arguments.

A client should never confirm for you. If it does, revoke its bridge.

## What is not available

Publishing pages, changing visibility or passwords, inviting people, sharing pages and deleting anything are not tools here. Use the Console or the `ravi pages` and `ravi invites` commands for those, where they keep their own confirmation.


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