You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* docs: fix outdated Codex MCP setup instructions
- Replace broken config.toml + 'codex mcp login' primary path with
'codex mcp add sourcebot --url <URL>' which matches Settings → MCP
- Add tip near Getting Started pointing users to Settings → MCP for
easiest setup (one-click install cards)
- Update Codex docs link to current official location
- Fix API key path to use CLI flag instead of manual config.toml editing
Co-authored-by: Michael Sukkarieh <msukkari@users.noreply.github.com>
* docs: remove anonymous access mentions from MCP docs
Co-authored-by: Michael Sukkarieh <msukkari@users.noreply.github.com>
* docs: consolidate example notes and restore anonymous access mention
- Remove redundant sentence from Fastest setup tip
- Combine public deployment note with anonymous access into single Note
- Restore anonymous access mention in Authorization section
Co-authored-by: Michael Sukkarieh <msukkari@users.noreply.github.com>
---------
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Michael Sukkarieh <msukkari@users.noreply.github.com>
Copy file name to clipboardExpand all lines: docs/docs/features/mcp-server.mdx
+20-19Lines changed: 20 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,12 +23,14 @@ Sourcebot MCP uses a [Streamable HTTP](https://modelcontextprotocol.io/specifica
23
23
24
24
You can read more about the options in the [authorization](#authorization) section.
25
25
26
-
<Note>
27
-
If [anonymous access](https://docs.sourcebot.dev/docs/configuration/auth/access-settings#anonymous-access) is enabled on your Sourcebot instance, no OAuth token or API key is required. You can connect directly to the MCP endpoint without any authorization.
28
-
</Note>
26
+
<Tip>
27
+
**Fastest setup:** Open **Settings → MCP** in your Sourcebot deployment to copy the Server URL and use one-click install cards for supported clients.
28
+
</Tip>
29
29
30
30
<Note>
31
-
The examples below add the MCP server and connect it to Sourcebot's public deployment at [app.sourcebot.dev](https://app.sourcebot.dev). Replace the URL with your own Sourcebot deployment as needed.
31
+
Note the following about these examples:
32
+
- The examples add the MCP server and connect it to Sourcebot's public deployment at [app.sourcebot.dev](https://app.sourcebot.dev). Replace the URL with your own Sourcebot deployment as needed.
33
+
- If [anonymous access](/docs/configuration/auth/access-settings#anonymous-access) is enabled on your Sourcebot instance, no OAuth token or API key is required. You can connect directly to the MCP endpoint without any authorization.
32
34
</Note>
33
35
34
36
<AccordionGroup>
@@ -145,30 +147,29 @@ You can read more about the options in the [authorization](#authorization) secti
Replace `https://app.sourcebot.dev` with wherever your Sourcebot instance is hosted. Codex will automatically detect OAuth support and prompt you to authorize in your browser when you first connect.
163
+
164
+
<Tip>
165
+
Open **Settings → MCP** in your Sourcebot deployment and click **Copy command** on the Codex card for a ready-to-run command with the correct Server URL.
Replace `https://app.sourcebot.dev` with wherever your Sourcebot instance is hosted, then set your API key as an environment variable:
@@ -276,7 +277,7 @@ You can read more about the options in the [authorization](#authorization) secti
276
277
277
278
## Authorization
278
279
279
-
The Sourcebot MCP server supports two authorization methods, OAuth and API keys. If [anonymous access](/docs/configuration/auth/access-settings#anonymous-access) is enabled on your instance, no authorization is required.
280
+
The Sourcebot MCP server supports two authorization methods: OAuth and API keys. If [anonymous access](/docs/configuration/auth/access-settings#anonymous-access) is enabled on your instance, no authorization is required.
280
281
281
282
Regardless of which method you use, all MCP requests are scoped to the associated Sourcebot user and inherit the [user's role and permissions](/docs/configuration/auth/roles-and-permissions). When [permission syncing](/docs/features/permission-syncing) is configured, this includes repository permissions - the MCP server will only surface results from repositories the user has access to.
0 commit comments