@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 38 lines 1.93 KB
Raw
1 ---
2 title: "Required API Key Authentication for MCP URLs"
3 description: "API key authentication becomes mandatory for MCP URLs starting December 15th, 2025"
4 date: "2025-11-13"
5 ---
6
7 We're strengthening the security of Model Context Protocol (MCP) URLs by making API key authentication mandatory for all requests.
8
9 ### What's Changing?
10
11 Starting **December 15th, 2025**, **all new Composio projects** must include the `x-api-key` header when making requests to MCP URLs. This header authenticates your application and ensures secure communication with the Composio platform.
12
13 ### Why This Matters
14
15 This change provides:
16 - **Enhanced Authentication**: Ensures only authorized applications can access MCP endpoints
17 - **Industry Best Practices**: Aligns with standard API security patterns
18
19 ### Impact on Existing Projects
20
21 **For existing projects**: We value backward compatibility and understand the need for a smooth transition. Your existing MCP URLs will continue to work without the `x-api-key` header until **April 15th, 2026**.
22
23 **Important**: After April 15th, 2026, all MCP URL requests without the `x-api-key` header will be rejected. Please ensure you update your applications before this date to avoid service disruption.
24
25 **Note**: If you're already passing the `x-api-key` header in your MCP requests, no action is required—you're all set!
26
27 ### Migration Guide
28
29 To adopt this security enhancement in your existing projects:
30
31 1. **Locate Your API Key**: Find your API key in the Composio dashboard under Project Settings
32 2. **Update Your Code**: Add the `x-api-key` header to all MCP URL requests
33 3. **Test Thoroughly**: Verify the updated requests work in your development environment
34 4. **Deploy**: Roll out the changes to your production environment
35
36 ### Questions?
37
38 If you have any questions about this security enhancement or need assistance with migration, please reach out to our support team or check our [MCP documentation](https://docs.composio.dev/docs/mcp).