Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 22, 04:30 UTC
docs: add changelog for MCP API key default enforcement for new orgs
Starting March 5, 2026, new organizations will have require_mcp_api_key enabled by default. Links back to the Jan 8 opt-in announcement. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Composio committed
Mar 4, 2026 at 00:04 UTC
8129c54459abfb5d33420a252fcdc71edeb94ded
1 file changed
+43
docs/content/changelog/03-04-26-mcp-api-key-default-new-orgs.mdx
new
+43
@@ -0,0 +1,43 @@
1
+---
2
+title: "MCP API Key Enforcement Now Default for New Organizations"
3
+description: "Organizations created on or after March 5, 2026 will have require_mcp_api_key enabled by default"
4
+date: "2026-03-04"
5
+---
6
+
7
+As announced in our [Optional API Key Enforcement for MCP Servers](/docs/changelog/2026/01/08) changelog, **MCP API key enforcement is now enabled by default for all newly created organizations**.
8
+
9
+### What's Changed
10
+
11
+Starting **March 5, 2026**, every new organization created on Composio will automatically have `require_mcp_api_key` set to `true` for all new projects. This means MCP server requests must include a valid API key in the `x-api-key` header.
12
+
13
+| Setting | Previous Default | New Default (orgs created March 5+) |
14
+|---------|-----------------|--------------------------------------|
15
+| `require_mcp_api_key` | `false` | `true` |
16
+
17
+### For New Organizations
18
+
19
+- All new projects require API key authentication for MCP server requests out of the box
20
+- Requests without a valid `x-api-key` header receive `401 Unauthorized`
21
+- You can opt out by explicitly setting `require_mcp_api_key: false` in your project configuration
22
+
23
+### For Existing Organizations
24
+
25
+Nothing changes for existing organizations. If your organization was created before March 5, 2026:
26
+
27
+- Your current `require_mcp_api_key` setting remains unchanged
28
+- You can opt in at any time through your [project settings](https://platform.composio.dev) or via the API
29
+
30
+### Opting Out (New Organizations)
31
+
32
+If you need to disable API key enforcement for a new project, you can set it explicitly during project creation or update the setting afterward:
33
+
34
+```bash
35
+curl -X PATCH "https://backend.composio.dev/api/v3/org/project/config" \
36
+ -H "Content-Type: application/json" \
37
+ -H "x-api-key: ak_your_api_key" \
38
+ -d '{"require_mcp_api_key": false}'
39
+```
40
+
41
+<Callout type="info">
42
+We strongly recommend keeping MCP API key enforcement enabled to prevent unauthorized access to your MCP servers. See the [original announcement](/docs/changelog/2026/01/08) for setup details and usage examples.
43
+</Callout>