Approved team context, without uploading your working tree.

Choose the hosted or local path

• Use the hosted connector for approved rules, approved skills, and review memory already synced to a Brief workspace.
• Use the local runbrief connector when the agent needs to scan source, resolve the active worktree, recommend tests, or review an uncommitted diff.
• The hosted team_context tool never returns raw repository source or uncommitted diffs.

Connect from Claude, ChatGPT, Codex, or Cursor

1. Sign in to Brief and confirm you belong to the workspace whose approved context you need.
2. Directory submissions for Claude, ChatGPT/Codex, and Cursor are in progress. Today, add https://www.runbrief.ai/mcp as a custom remote MCP connector in a client that supports Streamable HTTP and OAuth.
3. Complete Brief's OAuth consent. The requesting client receives identity access only; Brief checks current workspace membership again for every context request.
4. Ask for the approved context for a repository. If you belong to several Brief workspaces, name or select the workspace instead of letting the agent guess.

Availability by client

• Claude: add Brief as a custom remote connector now. The Connectors Directory submission is being prepared.
• ChatGPT and Codex:the same hosted MCP server is packaged for OpenAI's shared Plugins Directory. Native Codex discovery, OAuth, and a production tool call are verified.
• Cursor: add the hosted MCP URL directly today, or use the local connector for working-tree access. A Cursor Marketplace plugin is being prepared.
• A directory submission is not a claim of approval. This page will identify marketplace availability only after the relevant publisher approves and publishes Brief.

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.

The tool cannot change a workspace, approve guidance, edit a repository, inspect local files, or review a live working-tree diff. Use local Brief for those repo-attached jobs.

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.