# External MCP Servers

Connect third-party MCP servers and import their tools for use in runbooks and the Assistant

[Model Context Protocol](https://modelcontextprotocol.io) servers expose tools, such as API calls, database queries, and file operations, over a standard protocol. Risotto acts as an **MCP client**. It connects to an external MCP server, discovers the tools that server provides, and makes the ones you choose available to the Risotto agent.

An imported tool works like any other Risotto tool. The agent can call it when it handles a request. You can reference it in runbooks next to Risotto's native tools. It has the same per-tool settings, logging, and approval controls. The agent can act on any system an MCP server fronts, without a custom integration.

> **Note:** This page covers Risotto connecting **out** to other MCP servers as a client.
> If you want an MCP client like Claude Desktop or Cursor to call **into**
> Risotto, see the [Risotto MCP Server](https://www.tryrisotto.com/docs/integrations/mcp-server) page.

## Requirements

- The server URL must start with `https://`.
- The server must speak MCP over **Streamable HTTP**.
- The server must use one of these authentication modes: **OAuth 2.1**, **Bearer token**, **Custom headers**, or **None**.
- Each URL can be connected once per organization.
- You need the **Org Admin** or **Org Manager** role.

## Connect a server

You can connect a server from the dashboard or from a chat with the [Assistant](https://www.tryrisotto.com/docs/dashboard/assistant). Both ways manage the same connections.

### From the dashboard

1. **Start a new MCP server**

   Go to **Settings** > **Integrations**. Click **New custom integration**, then **MCP server**. Each server you add gets its own card in the **Custom** group.

2. **Configure the server**

   Enter a **Name** and the **Server URL**. Choose the **Authentication** the server requires.

   - **OAuth 2.1**: Risotto sends you to the server's authorization page when you connect.
   - **Bearer token**: Select a credential from the [Credential Vault](https://www.tryrisotto.com/docs/dashboard/settings/credential-vault). Risotto sends the token on every request.
   - **Custom headers**: Enter each header name and select a vault credential for its value. Risotto sends the headers on every request. You cannot use the names `Authorization`, `Host`, `Content-Length`, or `Mcp-Session-Id`.
   - **None**: Use this for servers that need no authentication.

3. **Test the connection (optional)**

   For **Bearer token**, **Custom headers**, and **None**, click **Test connection**. Risotto reports how many tools it can discover.

4. **Connect**

   Click **Connect & discover tools**. Risotto connects to the server and calls its `tools/list` method to discover the tools it provides.

5. **Import tools**

   Open the server from the **MCP servers** tab. Select each tool you want the agent to use. Click **Apply changes** to import them.

Imported tools are enabled and appear in the runbook editor next to Risotto's native tools.

#### Use a pre-registered OAuth client

Risotto registers itself with an OAuth 2.1 server automatically through Dynamic Client Registration. If the server does not support that, or your organization needs a confidential client, add a client yourself.

1. Choose **OAuth 2.1** in the **Authentication** field.
2. Expand **Use a pre-registered client**.
3. Copy the **Redirect URI** and register it as an allowed redirect with your provider.
4. Enter the **Client ID** and the **Client secret**.
5. Click **Connect & discover tools**.

### From the Assistant

Ask the Assistant to connect a server. How the connection proceeds depends on the authentication mode.

- **None**: Risotto creates the connection and discovers the tool catalog in one step.
- **Bearer token**: Risotto creates the connection without a token. The Assistant then shows a **secure credential card** in the chat. You enter the token in the card. The token goes straight to a secure endpoint and never passes through the conversation. Risotto checks it against a live call to the server before it saves it. Then a refresh discovers the tool catalog.
- **OAuth 2.1**: Risotto runs the full authorization-code flow, with endpoint discovery, Dynamic Client Registration, and PKCE. The Assistant shows an **Authorize** card. Click it to open the server's consent page in a new browser tab. The conversation continues when you finish.
- **Custom headers**: Risotto creates the connection without headers. Save the headers on the server's page in the dashboard. Then ask the Assistant to refresh the server.

The Assistant cannot use a pre-registered OAuth client. If the server does not support Dynamic Client Registration, connect it from the dashboard instead.

> **Note:** The chat never displays, echoes, or returns credentials, for any
> authentication mode. Connection listings show the authentication mode, never
> the secret.

## The tool catalog

Each connected server has a committed catalog. The catalog lists the remote tools Risotto discovered, with each tool's name, description, and parameters.

To discover tools again, open the server and select **Refresh available tools**, or ask the Assistant to refresh it. If nothing changed, nothing happens. If the remote tools changed, Risotto stages the change for your review instead of applying it. The server shows the **Needs review** status. Tools carry the badges **New**, **Updated**, or **Removed upstream**. Review the changes in the dashboard, then click **Apply changes**.

## Test a tool

You can call a remote tool on the live server before you import it.

- In the dashboard, open the server, select a tool, and use its **Test** tab.
- In the Assistant, ask it to test the tool. An approval card shows the tool name and the arguments before each call.

> **Warning:** Test calls are real calls. A remote tool can make destructive changes on the
> external system.

## Import tools

Importing turns a remote tool into a Risotto tool that runbooks and the Assistant can call.

- Risotto enables each imported tool on import.
- Each imported tool requires approval by default. To change this, open the tool and clear **Require approval before calling**.
- To rename a tool in the runbook editor, enter a **Display name (optional)**. The default is the remote tool's name. The name can have up to 100 characters.
- Risotto imports only tools in the committed catalog. A tool that exists only in unreviewed changes waits until you apply those changes in the dashboard.
- In the dashboard, **Apply changes** also removes tools you cleared and applies staged catalog changes.
- In the Assistant, importing only adds tools or updates their name and approval setting. It never removes a tool.

Risotto treats every external MCP tool as a tool that makes changes. A [script tool](https://www.tryrisotto.com/docs/integrations/tools/script-tools) that calls one always shows the approval card.

## Manage a connection

Open the server from the **MCP servers** tab, then use the actions menu.

- **Re-authorize**, **Update token**, or **Update headers** replaces the credentials. The menu item depends on the authentication mode. The current credentials stay active until Risotto verifies the new ones.
- **Disconnect server** removes the connection and its imported tools.

You cannot change the name or URL of a connection. To change the URL, disconnect the server and connect it again.

A connection shows one of these statuses: **Connected**, **Needs review**, or **Needs reauth**. With **Needs reauth**, runbooks that use the server's tools fail until you re-authorize or add credentials.

Risotto blocks a disconnect, or an **Apply changes** that removes tools, when an active runbook uses those tools. Remove the tools from each runbook first. Script tools that call the tools block the change too.

MCP connections apply to your whole organization. Every runbook can use the tools you import.

## Use an MCP server as a knowledge source

Risotto answers questions from the [indexes](https://www.tryrisotto.com/docs/concepts/indexing) you connect under **Knowledge**. An MCP server is not an index. Risotto does not crawl or embed its content. To let the agent answer from a knowledge system that has an MCP server, route the questions through a runbook:

1. Connect the server and import its search or lookup tools.
2. Create a [runbook](https://www.tryrisotto.com/docs/dashboard/runbooks). Set its **Match condition** to **Department request** so it applies to every ticket in a department. Or set it to **Request match** with a description of the questions the server can answer.
3. In the runbook instructions, reference the imported tool with `#`. Tell the agent when to call it and how to use the result.

The Assistant can do all three steps from a chat.

## Related

- [Risotto MCP Server](https://www.tryrisotto.com/docs/integrations/mcp-server): connect Claude Desktop, Cursor, and other MCP clients to Risotto
- [Runbooks](https://www.tryrisotto.com/docs/dashboard/runbooks): where imported tools get put to work
- [Knowledge indexing](https://www.tryrisotto.com/docs/concepts/indexing): the sources Risotto indexes
- [Credential Vault](https://www.tryrisotto.com/docs/dashboard/settings/credential-vault): where bearer tokens and header values are stored

Source: https://www.tryrisotto.com/docs/integrations/tools/external-mcp-servers
