# Install the Brollss MCP

> One server address, signed in with your Brollss account. Install the plugin to also get the working rules and the skills.

Web page: https://brollss.com/mcp/install. All MCP pages: https://brollss.com/llms.txt (index) and https://brollss.com/mcp/llms-full.txt (everything in one file).

## Before you start

- A Brollss account. Every plan works.
- A client that speaks MCP over streamable HTTP with OAuth: Claude Code, Cursor, Codex and most recent clients do.
- Install the plugin or add the bare server, not both. Two connections to the same server under two names are two sessions that know nothing of each other.

Server address:

```
https://brollss.com/api/mcp
```

## Claude Code

The plugin brings the server, five skills and the working rules. Add the marketplace, then install the plugin:

```
/plugin marketplace add smfcoder17/brollss-mcp
/plugin install brollss@brollss
```

For the server alone, without the skills:

```
claude mcp add --transport http brollss https://brollss.com/api/mcp
```

Then ask "use Brollss to import this video and make a publishable edit". The server also offers a prompt that starts a full edit of one project:

```
/mcp__brollss__monter_une_video
```

## Claude Desktop

1. Open Settings, then Connectors, and click Add custom connector.
2. Name it Brollss and paste the server address above.
3. Click Connect: the Brollss page opens so you can sign in.

The same steps work on claude.ai. The plugin's skills do not travel with a connector: give Claude [the best practices](https://brollss.com/mcp/best-practices.md) if you want it to follow them.

## Cursor

Open this link with Cursor installed to add the server:

```
cursor://anysphere.cursor-deeplink/mcp/install?name=Brollss&config=eyJ1cmwiOiJodHRwczovL2Jyb2xsc3MuY29tL2FwaS9tY3AifQ==
```

Or add it by hand to `~/.cursor/mcp.json` for every project, or to `.cursor/mcp.json` for one:

```
{
  "mcpServers": {
    "brollss": { "url": "https://brollss.com/api/mcp" }
  }
}
```

The working rules ship as `rules/brollss-workflows.mdc` in the [brollss-mcp repository](https://github.com/smfcoder17/brollss-mcp). Copy the file into `.cursor/rules/` and Cursor loads it with every request.

## Codex

Add the server to `~/.codex/config.toml`, then sign in:

```
[mcp_servers.brollss]
url = "https://brollss.com/api/mcp"
```

```
codex mcp login brollss
```

The plugin, with the skills, installs from a clone of the repository. The repository is itself a Codex marketplace:

```
git clone https://github.com/smfcoder17/brollss-mcp
codex plugin marketplace add /absolute/path/to/brollss-mcp
codex plugin add brollss@brollss
```

Codex keeps its own copy of the plugin. After you pull a new version, install it again.

## Other MCP clients

Any client that adds a remote MCP server by URL, over streamable HTTP, with OAuth sign-in works. Name the server `brollss`, give it the address above and pick OAuth as the authentication. The rules and the skills do not travel with a bare connection: give your agent [the best practices](https://brollss.com/mcp/best-practices.md) and [the workflows](https://brollss.com/mcp/workflows.md) instead.

## Sign in

1. On the first call, your client opens a Brollss page in your browser.
2. Sign in to your Brollss account if you are not signed in already.
3. The page names the client and the address it will send you back to. Allow it, or refuse.
4. Back in your client, the Brollss tools are listed. Ask your agent to call `whoami` to see which account is connected.

From then on the agent acts as you, on the projects your account can open.

## Open source

The plugin (manifests, rule, skills and their checks) is published under the Apache-2.0 license in the [brollss-mcp repository](https://github.com/smfcoder17/brollss-mcp). The server runs inside Brollss.