Skip to content

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: improve changelog title wording and use cURL snippet

Sushmitha Mallesh186a42519d73
diff --git a/docs/content/changelog/03-04-26-mcp-api-key-default-new-orgs.mdx b/docs/content/changelog/03-04-26-mcp-api-key-default-new-orgs.mdx
index 89142a356..56ea45e4e 100644
--- a/docs/content/changelog/03-04-26-mcp-api-key-default-new-orgs.mdx
+++ b/docs/content/changelog/03-04-26-mcp-api-key-default-new-orgs.mdx
@@ -1,5 +1,5 @@
---
-title: "MCP API Key Enforcement Now Default for New Organizations"
+title: "MCP API Key Authentication Enabled by Default for New Orgs"
description: "Organizations created on or after March 5, 2026 will have require_mcp_api_key enabled by default"
date: "2026-03-04"
---
@@ -31,11 +31,11 @@ Nothing changes for existing organizations. If your organization was created bef
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:
-```http
-PATCH /api/v3/org/project/config
-Content-Type: application/json
-
-{"require_mcp_api_key": false}
+```bash
+curl -X PATCH https://backend.composio.dev/api/v3/org/project/config \
+ -H "Content-Type: application/json" \
+ -H "x-api-key: YOUR_API_KEY" \
+ -d '{"require_mcp_api_key": false}'
```
<Callout type="info">