xbird — Twitter/X for AI Agents

Agent skills that give AI agents 247 Twitter/X tools — reading, searching, posting, engagement, media upload — across 3 integration protocols.

No Twitter developer account, no API keys, no OAuth.

Skills

Which skill to use?

Running in Claude Code / Cursor / Windsurf?
  → xbird (MCP)

Building a backend service or autonomous agent?
  → xbird-rest-api (x402 micropayments, USDC on Base)

Operating on Virtuals Protocol marketplace?
  → xbird-acp (E2E encrypted credentials, ECDH + AES-256-GCM)

Quick Install

Claude Code Plugin

/plugin install checkra1neth/xbird-skill

Agent Skill (works with 35+ agents)

npx skills add checkra1neth/xbird-skill

MCP Server Only

Bun (recommended) — auto-detects browser cookies:

claude mcp add xbird -- bunx @checkra1n/xbird

Node.js — requires one-time login:

claude mcp add xbird -- npx @checkra1n/xbird
npx @checkra1n/xbird login  # paste auth_token + ct0 from x.com DevTools

A payment wallet is generated automatically on first run.

CLI

# Save Twitter credentials locally
npx @checkra1n/xbird login

How It Works

MCP (Local)

AI Agent (Claude Code / Cursor / Windsurf)
  |  MCP stdio
@checkra1n/xbird (local process)
  |-- Auto-detect Twitter cookies from browser
  |-- Pay x402 --> xbird server (payment only)
  '-- Execute --> Twitter API (your residential IP)

The xbird server only verifies payments. All Twitter API calls happen locally from your machine.

REST API (Stateless)

Your Backend / Agent
  |-- npx @checkra1n/xbird login  -->  generates stateless token locally
  |-- GET /api/search + token     -->  xbird server
  |<-- 402 Payment Required       <--  (challenge)
  |-- x-payment header (signed)   -->  (auto via @x402/fetch)
  |<-- 200 { data, cursor }       <--  (result)

Fully stateless server — no database, no stored credentials. The token is self-contained (xbird_sk_<key>.<ciphertext>.<iv>), decrypted per-request then discarded.

ACP (Virtuals Protocol)

Buyer Agent
  |-- ECDH key exchange  -->  xbird TEE (attestation)
  |-- Encrypted credentials + job  -->  Virtuals relay (claw-api)
  |-- Job lifecycle: REQUEST → NEGOTIATION → TRANSACTION → COMPLETED
  |<-- Deliverable with results

End-to-end encrypted credentials (ECDH P-256 + AES-256-GCM). The Virtuals relay transports only opaque ciphertext.

Pricing

Resource catalog billing (~2× cheaper than X API pay-per-use per unit):

Comparison with X API

Example session (9 calls, count=20 on search/lists):

Both bill per resource unit — xbird unit rates are ~2× lower.

Security

Skill Structure

Each skill follows Anthropic's best practices — concise SKILL.md (<500 words) with heavy reference in separate files.

skills/
├── xbird/                   # MCP (local tools)
│   ├── SKILL.md             # Setup + workflows + common mistakes
│   └── tools.md             # 247 MCP tools reference
├── xbird-rest-api/          # REST API + x402 micropayments
│   ├── SKILL.md             # Setup + auth + example + common mistakes
│   ├── endpoints.md         # Full endpoint tables with pricing
│   └── x402-flow.md         # Payment flow + stateless token
└── xbird-acp/               # ACP (Virtuals marketplace)
    ├── SKILL.md             # Setup + example + common mistakes
    ├── encryption-flow.md   # ECDH P-256 + AES-256-GCM details
    └── polling.md           # Job lifecycle + polling strategies

Compatibility

Distribution

License

MIT