Migrate from Composio

Composio offers session-based MCP URLs and a 79-tool Twitter toolkit. This guide is for teams that prefer Xquik’s fixed MCP endpoint, Xquik-managed authorization, and broader Xquik operation catalog.

Why Migrate

	Composio	Xquik
MCP endpoint	Generated for a reusable session and user	Fixed at `https://xquik.com/mcp`
MCP authorization	Session URL plus the selected Composio connection flow	OAuth 2.1 login, or a client-specific API-key fallback
Twitter connection	Uses a Composio auth configuration	Uses the Xquik login and consent flow
Developer credentials	Depends on the selected Composio auth configuration	No X developer credentials required
Published toolkit	79 Twitter tools	118 MCP operations through 2 tools
Agent setup	Create a session, read `session.mcp.url`, then configure the client	Add the fixed endpoint, then authorize

Before: Current Composio Session MCP Setup

Install the current SDK

Install composio for Python or @composio/core for TypeScript.

Create a Twitter auth configuration

Select managed or custom authorization according to the current Composio toolkit options available to your organization.

Create a reusable MCP session

Call composio.create(...) with the user ID, Twitter toolkit, auth config, and mcp=True or mcp: true.

Read the session URL

Use session.mcp.url as the user’s MCP endpoint. Reuse the session instead of creating one for every request.

Configure the MCP client

Add session.mcp.url and follow the current Composio session authentication instructions.

Connect the Twitter account

Complete the authorization flow required by the selected auth configuration.

After: Xquik Setup (2 Steps)

Add the MCP server

Add https://xquik.com/mcp to your MCP client:

claude mcp add --transport http xquik https://xquik.com/mcp

codex mcp add xquik --url https://xquik.com/mcp

{
  "mcpServers": {
    "xquik": {
      "url": "https://xquik.com/mcp"
    }
  }
}

Authorize Xquik

Start authentication from the client. Use /mcp in Claude Code or run codex mcp login xquik in Codex. Complete Xquik login and consent in the browser. Let the client use its documented CIMD or DCR registration flow.

Affected Codex releases discard the RFC 9207 iss value before token exchange. Xquik already returns it. If Codex reports Authorization server response missing required issuer: expected https://xquik.com, set XQUIK_API_KEY and use bearer_token_env_var = "XQUIK_API_KEY" as described in Codex OAuth issuer validation error. Track the upstream Codex issue for the fixed release.

Use an API key only for programmatic clients that cannot complete OAuth and document secure header storage. ChatGPT custom apps require OAuth and cannot present custom API keys.

Code Migration

Python (Pydantic AI)

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

composio_client = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
session = composio_client.create(
    user_id=os.environ["USER_ID"],
    toolkits=["twitter"],
    auth_configs={
        "twitter": os.environ["COMPOSIO_TWITTER_AUTH_CONFIG_ID"],
    },
    mcp=True,
)
COMPOSIO_MCP_URL = session.mcp.url

import os

from pydantic_ai import Agent
from pydantic_ai.mcp import MCPToolset

toolset = MCPToolset(
    "https://xquik.com/mcp",
    headers={"x-api-key": os.environ["XQUIK_API_KEY"]},
)

agent = Agent("anthropic:claude-sonnet-4-6", toolsets=[toolset])
# API-key fallback for noninteractive runtimes

TypeScript (Mastra)

import { Composio } from "@composio/core";

const composio = new Composio({ apiKey: process.env.COMPOSIO_API_KEY });
const session = await composio.create(process.env.USER_ID!, {
  toolkits: ["twitter"],
  authConfigs: {
    twitter: process.env.COMPOSIO_TWITTER_AUTH_CONFIG_ID!,
  },
  mcp: true,
});
const mcpUrl = session.mcp.url;

import { MCPClient } from "@mastra/mcp";

const mcp = new MCPClient({
  servers: {
    xquik: {
      url: new URL("https://xquik.com/mcp"),
      requestInit: {
        headers: { Authorization: `Bearer ${process.env.XQUIK_API_KEY}` },
      },
    },
  },
});
// API-key fallback for noninteractive runtimes

Result Handoff

When you replace Composio agent steps, map raw tool responses into stable rows before sending them to Slack, Sheets, queues, databases, or dashboards.

Tweet Search Page

Store request q, each tweet_id, text, author_username, created_at, and url. Keep has_more and next_cursor for page loops.

User Page

Store source id as user_id, plus username, name, followers, verified, and profile_picture. Keep has_more and next_cursor when present.

Trend Page

Store each trend name, rank, query, and description. Keep response count and woeid for regional audit trails.

Monitor Webhook

Store delivery_id for receiver retry de-dupe and stream_event_id when one monitor event should process once across endpoint changes.

Stored Event Replay

Use GET /api/v1/events with after to replay stored monitor events. Store event_id, type, monitor_id, monitor_type, occurred_at, has_more, and next_cursor.

Media Attachments

For tweets or replies, pass public URLs in media and store tweet_id or write_action_id. For DMs, upload first, pass one media_id in media_ids, store message_id, and leave reply_to_message_id unset.

For downstream tables, keep tweet_rows, user_rows, trend_rows, webhook_event_rows, event_replay_rows, and media_write_rows as separate shapes instead of passing the whole MCP result through the workflow.

Framework-Specific Guides

For complete integration guides with your framework:

Getting Started

SDKs

Guides

Webhooks

MCP Server

Agent Plugins

Framework Guides

OAuth

MPP

Resources

Migrate from Composio

Why Migrate

Before: Current Composio Session MCP Setup

After: Xquik Setup (2 Steps)

Code Migration

Python (Pydantic AI)

TypeScript (Mastra)

Result Handoff

Tweet Search Page

User Page

Trend Page

Monitor Webhook

Stored Event Replay

Media Attachments

Framework-Specific Guides

​Why Migrate

​Before: Current Composio Session MCP Setup

​After: Xquik Setup (2 Steps)

​Code Migration

​Python (Pydantic AI)

​TypeScript (Mastra)

​Result Handoff

Tweet Search Page

User Page

Trend Page

Monitor Webhook

Stored Event Replay

Media Attachments

​Framework-Specific Guides

Why Migrate

Before: Current Composio Session MCP Setup

After: Xquik Setup (2 Steps)

Code Migration

Python (Pydantic AI)

TypeScript (Mastra)

Result Handoff

Framework-Specific Guides