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.

Address review comments: add non-breaking note, remove help section

Anshu Gargf7861a1d7bde
diff --git a/fern/pages/src/changelog/12-29-25-mcp-api-key-enforcement.md b/fern/pages/src/changelog/12-29-25-mcp-api-key-enforcement.md
index e7bdf2006..8345acf1c 100644
--- a/fern/pages/src/changelog/12-29-25-mcp-api-key-enforcement.md
+++ b/fern/pages/src/changelog/12-29-25-mcp-api-key-enforcement.md
@@ -2,6 +2,10 @@
We've introduced a new project-level security setting that allows you to require API key authentication for all MCP server requests. This opt-in feature gives you fine-grained control over who can access your MCP endpoints.
+<Note>
+**Non-breaking change**: This is fully opt-in. Your existing MCP integrations continue to work without any modifications.
+</Note>
+
## What's New
A new **"Require API Key for MCP"** toggle is now available in your Project Settings. When enabled, all requests to your MCP servers must include a valid Composio API key in the request headers.
@@ -148,11 +152,3 @@ PATCH /api/v3/org/project/config
"require_mcp_api_key": true | false
}
```
-
-## Need Help?
-
-If you have questions about implementing API key enforcement for your MCP servers:
-- Join our [Discord community](https://discord.gg/composio)
-- Check our [MCP documentation](/docs/mcp/quickstart)
-- Contact support at [email protected]
-