# Other MCP clients

> Connect any client that speaks MCP over HTTP, with browser sign-in or a token.

Any coding agent or tool that supports remote MCP servers can connect to Stableship.

## The server

```
https://api.stableship.ai/mcp
```

It speaks MCP over streamable HTTP. No local bridge is needed.

## Sign in through the browser

Stableship supports OAuth sign-in with dynamic client registration, which most MCP clients use on their own: add the server URL, and the client opens app.stableship.ai for you to sign in, pick the workspace and approve. You can disconnect it any time: **Settings**, then **Connections**, then **Connected apps**.

## Or use a token

In Stableship open **Settings**, then **Connections**, open **API tokens and connected apps**, and choose **Create token**. Pick what it may do:

- **Read findings and rules** (`read`): list apps, releases, findings, fix briefs and rules.
- **Start checks and verify fixes** (`run`): also start checks, verify fixes, add product notes and propose rule changes. An agent that fixes findings needs read and run.
- **Run Stableship** (`manage`): also act for you from the agent, such as triaging findings or changing policies. Anything that lowers protection still asks a person first. See [Run Stableship from your agent](/docs/guides/run-from-your-agent).

Copy the token: it starts with `sst_` and is shown once. Send it as a header on every request:

```text
Authorization: Bearer sst_your_token
```

Keep it in your shell profile or your tool's secret settings, never in the repository.

## Project instructions

Ask your agent to call `get_setup` for a short block to put in your project instructions, and `get_repo_files` for the Stableship section of `AGENTS.md` and the `.gate` rule files. Your agent commits them; Stableship never writes to your repository.