---
title: "Integrations and tool gateway"
description: "Call third-party APIs from a sandbox with no credential inside it."
---

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

# Integrations and tool gateway

An integration lets code in a sandbox call a third-party API, such as GitHub, as your organization. Sutra adds the credential to each request outside the VM. No token, key or secret is placed in the sandbox, so code you run there cannot read or leak it.

## Attach an integration

Pass `integrations` when you create a sandbox, with the provider key of each one. [Supported integrations](https://docs.jgcp.mistrivedev.com/platform/supported-integrations/) lists every provider and its key. Then call the provider's API from inside the sandbox as usual, with no `Authorization` header. Sutra adds the credential on the way out.

Agents and services list integrations in their revision, and every sandbox they run gets them.

## Scopes

The target API derives each integration's scopes from what your organization allows, so you only name the provider. You can still pass `scopes` to ask for less.

:::note[Today]
Today `scopes` is required on each integration, and the provider key is `github-legacy`. The CLI cannot attach an integration yet, so attach integrations from the SDK.

A scope beyond what your organization allows, or a provider you cannot use, fails the create with `FAILED_PRECONDITION` and leaves the sandbox in the state `ERROR`; delete it. To change the integrations of a running sandbox, call `sandboxes.update` with the update mask `integrations` and the full list you want. Apps cannot use integrations.
:::

## Egress

Integrations stay reachable under every [egress policy](https://docs.jgcp.mistrivedev.com/sandboxes/network/), including `DENY_ALL`. You do not need to add a provider's hosts to an allow list.

## Tool gateway

The tool gateway serves your integrations as Model Context Protocol (MCP) tools, so an agent can find and call them with an MCP client. It uses the same workload identity, and credentials stay outside the sandbox.

For a complete walkthrough, see [Call GitHub from a sandbox](https://docs.jgcp.mistrivedev.com/examples/github-integration/). For every provider you can attach, see [Supported integrations](https://docs.jgcp.mistrivedev.com/platform/supported-integrations/).

Source: https://docs.jgcp.mistrivedev.com/platform/integrations/index.mdx
