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
| 1 | --- |
| 2 | title: "Enhanced MCP URL Security Requirements" |
| 3 | description: "MCP URLs now require user_id or connected_account_id for better isolation" |
| 4 | date: "2025-11-05" |
| 5 | --- |
| 6 | |
| 7 | We're introducing improved security requirements for Model Context Protocol (MCP) URLs to ensure better isolation between user connections and prevent unauthorized access. |
| 8 | |
| 9 | ### What's Changing? |
| 10 | |
| 11 | Starting today, **all new Composio projects** must include at least one of the following parameters in their MCP URLs: |
| 12 | - `user_id` - Identifies the specific user |
| 13 | - `connected_account_id` - Identifies the specific connected account |
| 14 | |
| 15 | ### Why This Matters |
| 16 | |
| 17 | This change ensures that: |
| 18 | - **User Isolation**: Each user's connections remain completely separate from others |
| 19 | - **Enhanced Security**: Prevents potential cross-user data access scenarios |
| 20 | - **Better Multi-Tenancy**: Enables safer multi-tenant application architectures |
| 21 | - **Explicit Access Control**: Forces developers to explicitly specify which user or account context they're operating in |
| 22 | |
| 23 | ### Impact on Existing Projects |
| 24 | |
| 25 | **For existing projects**: We understand the importance of backward compatibility. While we've sent email notifications to project owners about upgrading their MCP URLs, your existing integrations will continue to work until **January 15th, 2026**. |
| 26 | |
| 27 | **Important**: After January 15th, 2026, MCP URLs without `user_id` or `connected_account_id` query parameters will no longer be supported. Please ensure you update your MCP URLs before this date to avoid service disruption. |
| 28 | |
| 29 | **Note**: If your MCP URLs already include either `user_id` or `connected_account_id` query parameters, no action is required—you can safely ignore this notice. |
| 30 | |
| 31 | ### Implementation Example |
| 32 | |
| 33 | **Before:** |
| 34 | ``` |
| 35 | https://dashboard.composio.dev/v3/mcp/{id} |
| 36 | ``` |
| 37 | |
| 38 | **After (with user_id):** |
| 39 | ``` |
| 40 | https://dashboard.composio.dev/v3/mcp/{id}?user_id=user_123 |
| 41 | ``` |
| 42 | |
| 43 | **After (with connected_account_id):** |
| 44 | ``` |
| 45 | https://dashboard.composio.dev/v3/mcp/{id}?connected_account_id=ca_xyz |
| 46 | ``` |
| 47 | |
| 48 | ### Migration Guide |
| 49 | |
| 50 | If you're using an existing project and want to adopt this security enhancement: |
| 51 | |
| 52 | 1. Review your current MCP URL configuration |
| 53 | 2. Add either `user_id` or `connected_account_id` parameter to your URLs |
| 54 | 3. Update your application code to pass the appropriate identifier |
| 55 | 4. Test the updated URLs in your development environment |
| 56 | |
| 57 | For more details on choosing the right user identifiers for your application, see our [session documentation](/docs/how-composio-works). |
| 58 | |
| 59 | ### Questions? |
| 60 | |
| 61 | 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](#). |