diff --git a/docs/docs/integrating-with-flagsmith/mcp-server.md b/docs/docs/integrating-with-flagsmith/mcp-server.md
index 06f113987975..9839165a5b08 100644
--- a/docs/docs/integrating-with-flagsmith/mcp-server.md
+++ b/docs/docs/integrating-with-flagsmith/mcp-server.md
@@ -31,13 +31,29 @@ We support Cursor, Claude Code, Claude Desktop, Windsurf, Gemini CLI, Codex CLI,
 
 The MCP Server supports two authentication methods. You can use either one — both work side by side.
 
-#### OAuth (Recommended for SaaS users)
+#### 1. OAuth (Recommended for SaaS users)
 
-OAuth lets you authenticate directly in your browser — no API keys to manage. When you first connect, your MCP client will open a browser window where you log in to Flagsmith and authorise access.
+OAuth lets you authenticate directly in your browser — no API keys to manage. Simply add the MCP server to your client and it will redirect you to the Flagsmith OAuth flow where you can log in and authorise access.
+
+For **Claude Code**:
+
+```bash
+claude mcp add --transport http "flagsmith" \
+    "https://app.getgram.ai/mcp/flagsmith-mcp"
+```
+
+For **Codex CLI**:
+
+```json
+[mcp_servers.flagsmith]
+url = "https://app.getgram.ai/mcp/flagsmith-mcp"
+```
+
+For other clients, visit the **[installation page](https://app.getgram.ai/mcp/flagsmith-mcp/install)** for client-specific instructions.
 
 > OAuth is currently available for SaaS users only. Self-hosted and private cloud customers should use an Organisation API Key or contact our team.
 
-#### Organisation API Key
+#### 2. Organisation API Key
 
 Alternatively, you can authenticate using an Organisation API Key: