Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs: clean up changelog wording and remove redundancy
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sushmitha Mallesh committed
Mar 4, 2026 at 12:36 UTC
5cc90cf6013e49702fc55b1574dd7844f3dd1e7c
1 file changed
+4
-6
docs/content/changelog/03-04-26-mcp-api-key-default-new-orgs.mdx
+4
-6
@@ -4,11 +4,11 @@ description: "Organizations created on or after March 5, 2026 will have require_
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**.
7
+As announced in our [Optional API Key Enforcement for MCP Servers](/docs/changelog/2026/01/08) entry, **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.
11
+From **March 5, 2026**, all projects in newly created organizations will have `require_mcp_api_key` set to `true` by default. Any MCP server request without a valid `x-api-key` header will be rejected with `401 Unauthorized`.
12
13
| Setting | Previous Default | New Default (orgs created March 5+) |
14
|---------|-----------------|--------------------------------------|
@@ -16,9 +16,7 @@ Starting **March 5, 2026**, every new organization created on Composio will auto
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
19
+- You can opt out by setting `require_mcp_api_key: false` in your project configuration
20
21
### For Existing Organizations
22
@@ -29,7 +27,7 @@ Nothing changes for existing organizations. If your organization was created bef
27
28
### Opting Out (New Organizations)
29
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:
30
+If you need to disable API key enforcement, set `require_mcp_api_key: false` during project creation or update it afterward:
31
32
```bash
33
curl -X PATCH https://backend.composio.dev/api/v3/org/project/config \