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, 15:45 UTC
Address review comments: add non-breaking note, remove help section
Anshu Garg committed
Jan 5, 2026 at 12:40 UTC
f7861a1d7bde0f06fb75cb7d2ce28e3146800666
1 file changed
+4
-8
fern/pages/src/changelog/12-29-25-mcp-api-key-enforcement.md
+4
-8
@@ -2,6 +2,10 @@
2
3
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.
4
5
+<Note>
6
+**Non-breaking change**: This is fully opt-in. Your existing MCP integrations continue to work without any modifications.
7
+</Note>
8
+
9
## What's New
10
11
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
152
"require_mcp_api_key": true | false
153
}
154
```
151
-
152
-## Need Help?
153
-
154
-If you have questions about implementing API key enforcement for your MCP servers:
155
-- Join our [Discord community](https://discord.gg/composio)
156
-- Check our [MCP documentation](/docs/mcp/quickstart)
157
-- Contact support at support@composio.dev
158
-