@devries-cameron20 / composio Mirror · read-only
Fork 0

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 21, 03:37 UTC

next
mdx 41 lines 1.91 KB
Raw
1 ---
2 title: "MCP API Key Authentication Enabled by Default for New Orgs"
3 description: "Organizations created on or after March 5, 2026 will have require_mcp_api_key enabled by default"
4 date: "2026-03-04"
5 ---
6
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 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 |---------|-----------------|--------------------------------------|
15 | `require_mcp_api_key` | `false` | `true` |
16
17 ### For New Organizations
18
19 - You can opt out by setting `require_mcp_api_key: false` in your project configuration
20
21 ### For Existing Organizations
22
23 Nothing changes for existing organizations. If your organization was created before March 5, 2026:
24
25 - Your current `require_mcp_api_key` setting remains unchanged
26 - You can opt in at any time through your [project settings](https://dashboard.composio.dev?utm_source=docs&utm_medium=content&utm_campaign=changelog-03-04-26-mcp-api-key-default-new-orgs) or via the API
27
28 ### Opting Out (New Organizations)
29
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 \
34 -H "Content-Type: application/json" \
35 -H "x-api-key: YOUR_API_KEY" \
36 -d '{"require_mcp_api_key": false}'
37 ```
38
39 <Callout type="info">
40 We strongly recommend keeping MCP API key enforcement enabled to prevent unauthorized access to your MCP servers. See the [original announcement](/docs/changelog/2026/01/08) for setup details and usage examples.
41 </Callout>