Replit

Replit connects to the Stableship MCP server, so its Agent can read what Stableship found, fix it and ask Stableship to verify the fix. Replit reads replit.md from your repository.

Connect

1. Click Add to Replit.
2. Click Test & save, then approve.

The Add to Replit button in Stableship's setup and in Settings, then Connections, does step 1 for you, or use this link: Add to Replit.

Approving opens app.stableship.ai: sign in, pick the workspace and approve. No token to copy. You can disconnect it any time in Stableship: Settings, then Connections, then Connected apps.

Use a token instead

First make a token: in Stableship open Settings, then Connections, open API tokens and connected apps, and choose Create token with Read findings and rules and Start checks and verify fixes. Copy it: it starts with sst_ and is shown once. Use it where these steps say sst_your_token.

1. In Replit: MCP Servers, + Add MCP server. Display name: Stableship. MCP Server URL:

   https://api.stableship.ai/mcp

2. Under Advanced settings add the header Authorization with this value, then Test & save:

   Bearer sst_your_token

Keep the token out of your repository.

Check it works

Back in Replit, Test & save shows it connected. Then ask Replit to list your Stableship projects: it calls list_projects and names your app.

If it does not connect:

• In MCP Servers, open Stableship and Test & save again.
• Or use a token instead.

Before you publish

Replit publishes when you click publish, so Stableship checks each change that reaches GitHub before you do. When a change breaks one of your rules, Stableship says "don't publish yet". If you already published it, publish the last good version again, or copy the revert from the release page and give it to Replit's Agent.

Keep the rules in your repository

Ask Replit's Agent to call get_repo_files and add the Stableship section it returns to replit.md: the rules, and how to use the tools. Stableship never writes to your repository itself.