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: add March 1, 2026 rollout date for MCP API key enforcement

Anshu Gargf0dbd5e1c813
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 5772b9240..26d049c5a 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
@@ -3,7 +3,7 @@
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.
+**Opt-in today, default soon**: This feature is currently opt-in. Starting **March 1, 2026**, it will be enabled by default for new organizations. We recommend enabling it now to prepare your integrations.
</Note>
## What's New