Supported capabilities
MCP connector Core integration- MCP connector: Replicas — Give the Sazabi agent tools to create and steer Replicas cloud coding-agent workspaces, chats, environments, and automations.
- Core integration: Replicas — Connect Replicas so Sazabi can hand issue fixes to it and follow the result in the issue thread.
Core integration
About
Connecting Replicas lets Sazabi hand an issue’s fix to Replicas. You choose Fix on an issue, Replicas works in your repository and opens a pull request, and Sazabi follows its progress in the issue thread. Replicas is a coding agent integration: one of the agents listed under Settings > Integrations that Fix can hand off to.Prerequisites
- A Replicas organization API key.
- Organization admin access in Sazabi.
- Repository access for Replicas: Replicas works only in repositories its GitHub integration can reach. Install GitHub at app.replicas.dev > Integrations, then add each repository to a Replicas environment under Environments.
Set up in the dashboard
1
Get your credentials
Create a Replicas organization API key from Replicas settings. The Replicas organization ID field is optional.2
Open the Replicas integration
In the dashboard, go to Settings > Integrations and open Replicas.3
Connect with the key
Choose Connect and paste the key. Sazabi checks it with Replicas before saving the connection.4
Check repository access
The connection page’s Repositories section shows which repositories Fix can hand to Replicas. Default coding agent is set per project, so it appears only when you open the connection from a project’s settings: open the project, go to its Integrations settings, select Replicas, and choose Use this account. Fix then hands off to it without asking. For Replicas, the connection page also lets you pick a Default environment for fixes.Set up with the CLI
You can also connect Replicas with the Sazabi CLI (installed and authenticated; see CLI reference). Replicas is an API-key provider, so pass its key as theapiKey credential. Read the key from an environment variable rather than pasting it inline:
sazabi integrations list to confirm the connection, or sazabi integrations providers --json to see each provider’s credential fields.
Fix issues
Open an issue in the project inbox, choose Fix, and pick Replicas. Confirm the repository, and the base branch if asked, then choose Fix with Replicas. Replicas works in the repository and opens a pull request; its progress, questions, and pull request appear in the issue thread. From the CLI, hand the fix off and follow the attempt withsazabi agent-dispatches (see CLI reference):
sazabi agent-dispatches reply answers a question from the agent, and sazabi agent-dispatches cancel stops the attempt.
Verify
Choose Fix on an open test issue and hand it to Replicas. Confirm the attempt appears in the issue thread within a minute, and thatsazabi agent-dispatches list --issue-id "$ISSUE_ID" lists it with Replicas as the agent.
Troubleshooting
Replicas did not accept this key - The key is wrong, revoked, or from the wrong account. Create a new one and reconnect. Replicas can’t reach any repositories yet - Replicas works only in repositories its GitHub integration can reach. Install GitHub at app.replicas.dev > Integrations, then add each repository to a Replicas environment under Environments. Fix doesn’t offer Replicas - Confirm the connection shows connected under Settings > Integrations, and that the issue’s project has a repository Replicas can reach.Further reading
Issues
Open, investigate, and resolve issues.
Integrations
Browse the core integrations.
Replicas MCP connector
Give the Sazabi agent Replicas tools over MCP.