One local connector. Team context when you need it.

Start with local Brief

• Install the runbrief MCP connector in Claude Code, Codex, Cursor, or another local MCP-capable coding agent.
• It resolves the active worktree, scans source, maps architecture, routes task context, recommends tests, and reviews uncommitted diffs on the developer machine.
• Local mode works without an account. Add a workspace only when the team wants approved shared guidance and proof history.

Add approved team context

1. Create or join the Brief workspace that owns the approved guidance.
2. In a client that supports remote Streamable HTTP MCP with OAuth, add https://www.runbrief.ai/mcp.
3. Complete OAuth consent. Brief checks current workspace membership for every context request.
4. Ask for team context for the repository. Name the workspace when more than one is available.

Choose the right client path

• Claude Code, Codex, and Cursor: use the local connector for repo-attached work. Repository plugin packages launch the same versioned runtime. Once their marketplace listings are live, install the native plugin; the commands below remain supported for consoles and direct MCP setup.
• VS Code and other MCP-capable editors: add a stdio server that runs npx -y runbrief@stable and passes the active workspace directory.
• Terminal and CI: run npx -y runbrief@stable setup directly. Use an exact version for reproducible automation.
• ChatGPT: supported workspace plans can add the hosted endpoint as a custom MCP app through developer mode. An admin may need to enable and publish it for the workspace.
• Marketplace-ready packaging is not the same as an approved public listing. Brief will claim official marketplace availability only after the relevant publisher makes it live.

What the connector can do

Brief exposes one hosted tool: team_context. It is read-only and can return approved rules, skills, and review memories for one workspace and optional repository identity.

It never returns raw repository source or uncommitted diffs and cannot change a workspace, approve guidance, edit files, or review a live working-tree diff.

Troubleshoot a connection

1. If authorization expires, disconnect Brief in the AI client and connect again.
2. If Brief asks for a workspace, provide the intended workspace explicitly; this is a tenant-safety check.
3. If repository context is empty, confirm approved guidance was synced to that Brief workspace and that the repository identity matches.
4. For persistent failures, use the support checklist. Never send access tokens, connector keys, raw source, or session cookies.