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
Copy file name to clipboardExpand all lines: docs/docs/integrating-with-flagsmith/mcp-server.md
+11-3Lines changed: 11 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,9 +27,17 @@ Head to our installation page and pick your client:
27
27
28
28
We support Cursor, Claude Code, Claude Desktop, Windsurf, Gemini CLI, Codex CLI, and any other client that supports MCP servers.
29
29
30
-
### Configuration
30
+
### Authentication
31
31
32
-
You'll need an **Organisation API Key** from Flagsmith:
32
+
The MCP Server supports two authentication methods. You can use either one — both work side by side.
33
+
34
+
#### OAuth (Recommended)
35
+
36
+
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.
37
+
38
+
#### Organisation API Key
39
+
40
+
Alternatively, you can authenticate using an Organisation API Key:
33
41
34
42
1. Go to **Organisation Settings** in your Flagsmith dashboard
35
43
2. Generate a new API Key
@@ -48,7 +56,7 @@ Running your own Flagsmith instance? Point the MCP Server at your API by adding
0 commit comments