mcp.composio.dev) was decommissioned in March 2026, and managed Twitter credentials were removed in February 2026. This guide shows how to replace Composio’s Twitter MCP integration with Xquik.
Why Migrate
| Composio | Xquik | |
|---|---|---|
| Accounts needed | 3 (X Developer, Composio, AI tool) | 1 |
| Credentials | 6 (API Key, API Secret, Bearer Token, OAuth Client ID, OAuth Client Secret, Composio API Key) | 1 (API key) |
| Setup steps | 14 | 3 |
| OAuth dance | Yes (browser redirect on first use) | No |
| X Developer Portal | Required (create app, configure callbacks) | Not required |
| Dashboard config | Required (create auth config, toggle custom creds) | Not required |
| Setup code | ~20 lines + CLI commands | 0 lines (just config) |
| Twitter tools | 79 | 122 endpoints + 23 extraction tools |
Before: Composio Setup (14 Steps)
Configure OAuth callback
Set OAuth 2.0 callback URL to
https://backend.composio.dev/api/v1/auth-apps/add.Configure custom auth in Composio dashboard
Navigate to dashboard, create auth config for Twitter, toggle custom credentials, enter all 5 X credentials.
Write MCP URL generation script
Write ~20 lines of Python to create a Composio session and extract the MCP URL.
After: Xquik Setup (3 Steps)
Get an API key
Sign up at xquik.com, subscribe, and generate an API key from the dashboard.