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

# Replicas MCP connector

> Give the Sazabi agent tools to create and steer Replicas cloud coding-agent workspaces, chats, environments, and automations.

[All Replicas integration capabilities](https://docs.sazabi.com/catalogs/integrations/replicas)

## About

This is an MCP connector that gives the Sazabi agent tools from Replicas' hosted MCP server at `https://api.replicas.dev/v1/mcp`. Replicas runs coding agents in cloud workspaces called replicas. Replicas' MCP server authenticates with an API key; it does not offer OAuth. Sazabi stores your Replicas API key securely and sends it as the `Authorization: Bearer` token to Replicas' MCP endpoint. The tools mirror the Replicas API with the key's permissions: an organization key acts as the Replicas bot, and a personal key acts as you. Write operations are governed by the per-connection read-only toggle.

**What the agent can do:**

* Create, wake, sleep, archive, and delete replicas, and wait for them to finish (`create_replica`, `list_replicas`, `wait_for_replica`)
* Send messages to coding agents and read chat history (`send_replica_message`, `read_replica_history`)
* Review and merge the pull requests replicas open (`get_pull_requests`, `merge_pull_request`)
* Manage repositories, environments, automations, and learnings

## Prerequisites

* A Replicas account with at least one coding agent configured
* A Replicas API key: an organization key from [Settings → API Keys](https://app.replicas.dev/dashboard/settings?tab=api-keys) (admins) or a personal key from [Personal → API Keys](https://app.replicas.dev/dashboard/account/api-keys)

## Set up in the dashboard

Configure connectors in the dashboard under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 1**

### Open the connector

Find Replicas in [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Step 2**

### Add your key

Create an API key in Replicas. An organization key acts as the Replicas bot; a personal key acts as you, including your personal environments and automations. Paste it into Sazabi. Sazabi stores it securely and sends it as the `Authorization: Bearer` token to Replicas' MCP endpoint (`https://api.replicas.dev/v1/mcp`).

## Set up with the CLI

Replicas authenticates with a Replicas API key. With the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) installed and authenticated (see [`sazabi mcp-connectors` reference](https://docs.sazabi.com/reference/cli/mcp-connectors)), connect it in one command, passing the credential as a header:

```bash theme={"system"}
sazabi mcp-connectors connect replicas --header "Authorization=Bearer <api-key>"
```

The CLI connects to the MCP server at once and prints the connection with the tools it discovered; a credential the server rejects is reported, and the connection is left needing attention. Use `NAME=@<file>` to read a value from a file, or `--header-file <file.json>` for a JSON object of header names and values. To rotate the stored credentials later, use `sazabi mcp-connectors update-credentials <connection-id>`; find the connection ID with `sazabi mcp-connectors list`.

## Verify

Open the connector's connection page under [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors) and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to list your Replicas environments and confirm it returns them. If no tools appear, confirm the key is correct.

## Troubleshooting

**No tools discovered**: Confirm the API key is valid and has not been revoked. Re-enter it from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Connection shows needs attention**: The key may have been revoked; create a new one in Replicas and update the connector's credentials from [**Settings > MCP connectors**](https://app.sazabi.com/settings/mcp-connectors).

**Creating a replica fails**: Replicas needs at least one coding agent configured in **Organization → Coding Agents** before it can create workspaces.

## Further reading

> [card] [Agent tools](https://docs.sazabi.com/ask/agent-tools.md)
>
> How the agent uses connector tools.

> [card] [MCP connectors](https://docs.sazabi.com/catalogs/integrations.md#mcp-connectors)
>
> Browse the connector catalog.


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