# No integration for it? Ask the Assistant to build one.

Your stack has the tool nobody else integrates with. Tell the Risotto Assistant what you need from it, and it builds the connection: tools from the vendor's API docs, a script for any public API, or a link to your MCP server. Then use it in the Assistant, in runbooks and in automations.

[Book a demo](/demo)

## Turn a vendor's API docs into tools

Send the Risotto Assistant a link to the vendor's API docs. It finds the published spec, checks it with you, and picks out the endpoints you asked for. You paste the API key into a secure card, where you also confirm the host, and it goes straight into Risotto's credential vault. Each read must pass a test before it goes live. Tools that change data arrive switched off, for you to review.

Okta, Jamf, Zendesk and a dozen more start from a ready-made template. [Integrations](/integrations)

The Assistant builds Snipe-IT tools from its published API spec, and tests the read before it goes live. Example data.

## Any public API, the same steps every time

When one job takes several calls in a fixed order, ask the Risotto Assistant for a script tool. It writes the TypeScript and draws it as a flow chart. The tool calls only the HTTPS hosts its code declares, and only reads from them unless you allow writes. API keys never appear in the code, and a test run that changes something waits for your approval.

[Script tools](/product/script-tools)

The Assistant writes a script tool for a badge system with no integration, then tests it step by step. Example data.

## Plug in the MCP servers you already run

Give the Risotto Assistant your MCP server's URL. It connects with OAuth or a bearer token you paste into a secure card, lists the server's tools and imports the ones you pick. Imported tools ask before they run until you change that. When a refresh finds a changed tool list, Risotto marks the server Needs review, and your tools keep the list you accepted until you apply the change.

[MCP server and API](/product/mcp)

The Assistant connects an internal MCP server and imports four of its five tools. Example data.

## Which one should you build?

| | Custom API tool | Script tool | MCP server |
|---|---|---|---|
| Start from | The vendor's API docs, a spec or a curl command | A description of the job | The server's URL |
| Best for | Single calls the AI agent chooses between, such as "find a laptop by serial" | A fixed sequence of calls, such as "suspend their badge, then note it on the ticket" | Tools a vendor or your team already serves over MCP |
| Who decides each step | The AI agent | The code | The AI agent |
| Keys | Credential vault, from a secure card | Credential vault, filled in as each request leaves | OAuth sign-in or a bearer token |

## Build it once. Use it everywhere.

In Risotto, a custom tool works like a built-in one. Add it to a runbook and the AI agent uses it on requests in Slack and Teams. Add it to an automation and it runs when Rippling, Okta or a webhook reports a change. Attach a script tool to an access rule, and it grants access after approval and removes it when access ends, for an app with no Okta group. Ask the Assistant and it uses the tool right in the conversation.

[Runbooks](/product/runbooks) · [Automations](/product/automations) · [Access requests](/product/access-requests) · [Assistant](/product/assistant)

Snipe-IT's custom tools in the Assistant, a runbook and an automation. Example data.

## Your tools, with Risotto's approvals

Risotto applies the same approvals and logs to the tools you build as to its own.

- **Keys stay in the vault.** You paste each key into a secure card, and it goes straight into Risotto's credential vault. Nobody reads it back, the Assistant included.
- **Only the hosts you name.** A script tool calls only the hosts its code declares. Every other request is refused before it leaves.
- **Approval is on by default.** New custom tools ask before they run. Custom API tools that change data start switched off until you review them.
- **Changed MCP tools wait for you.** When a server's tool list changes, nothing new runs until you accept it.

[Security and trust](/security)

## Frequently asked questions

### Can Risotto connect to a system it has no integration for?

Yes. Risotto can use any system with a public API or a remote MCP server. Ask the Risotto Assistant to build custom API tools from the vendor's docs, write a script tool that calls the API, or connect the MCP server.

### How do I add a custom API integration to Risotto?

Send the Risotto Assistant a link to the vendor's API docs. It finds the published spec, builds the tools you need, collects the key in a secure card and tests each read before it goes live. In the dashboard, you can also add a source from a spec file or URL, or a curl command. [Integrations](/integrations)

### Should I use a custom API tool, a script tool or an MCP server?

Use a custom API tool for single calls the AI agent chooses between, such as finding a laptop by serial number. Use a script tool when one job needs several calls in a fixed order. Connect an MCP server when the vendor or your team already runs one. All three work in Risotto's runbooks, automations and Assistant.

### Can Risotto use our own MCP servers?

Yes. Give the Risotto Assistant your remote MCP server's URL, sign in with OAuth or add a bearer token, and pick which tools to import. Imported tools ask for approval before they run until you change that. [MCP server and API](/product/mcp)

### Where can I use a custom tool in Risotto?

In runbooks the AI agent follows in Slack and Teams, in automations triggered by events, in script tools and in the Risotto Assistant. A script tool can also grant and remove access on an access rule. [Access requests](/product/access-requests)

## Connect the system nobody else integrates with

[Book a demo](/demo)

Source: https://www.tryrisotto.com/product/custom-integrations
