← All integrations

TwittrAPI MCP server

42 operations2 webhooks

Read public X (Twitter) data through TwittrAPI (twittrapi.com) and get new tweets of the accounts you watch by signed webhook.

Try TwittrAPI with your agent

Connect TwittrAPI, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in TwittrAPI on my account, then run one read-only example and show me the result.

Runs once, when you ask

TwittrAPI tools and triggers

Tools are what your agent can do in TwittrAPI through Corsair's MCP server. Triggers are the TwittrAPI events a routine can start from.

Monitors

  • Add AccountsWrite

    Watch X accounts for new tweets (up to 100 per request)

    monitors.addAccounts

  • Create WebhookWrite

    Add a webhook for watched-account tweet events

    monitors.createWebhook

  • Delete WebhookDestructive

    Remove an account-monitoring webhook

    monitors.deleteWebhook

  • Get DeliveriesRead-only

    Show latest monitor events with delivery status

    monitors.getDeliveries

  • Get EventsRead-only

    Pull monitor events after an event ID (7-day retention)

    monitors.getEvents

  • Get PlanRead-only

    Get the account-monitoring plan and webhooks

    monitors.getPlan

  • Get WebhookRead-only

    Get one account-monitoring webhook

    monitors.getWebhook

  • List AccountsRead-only

    List watched X accounts and plan usage

    monitors.listAccounts

  • List WebhooksRead-only

    List account-monitoring webhooks, oldest first

    monitors.listWebhooks

  • Remove AccountDestructive

    Stop watching an X account

    monitors.removeAccount

  • Test WebhookWrite

    Send a signed test event to a webhook

    monitors.testWebhook

  • Update AccountWrite

    Change a watched account's reply/retweet/quote filters

    monitors.updateAccount

Connect TwittrAPI to Claude, ChatGPT or Cursor

  1. 1

    Connect TwittrAPI in Corsair

    Add your TwittrAPI API key once in Corsair. Corsair stores the credential encrypted and makes the TwittrAPI API calls for your agent, so it never goes into a prompt or a config file. Connect TwittrAPI

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs TwittrAPI. On a ChatGPT personal plan, connect TwittrAPI here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, TwittrAPI's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/twittrapi, add the TwittrAPI plugin, and connect with an API key. Then call methods like corsair.twittrapi.api.balance.get() from your app. Corsair verifies webhooks, and syncs data per tenant.

Yes. TwittrAPI requires an API key from your TwittrAPI account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit TwittrAPI, GitHub, Notion, Stripe, and the rest. Trigger TwittrAPI from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for read public X (Twitter) data through TwittrAPI (twittrapi.com) and get new tweets of the accounts you watch by signed webhook. Common builds include sync jobs, admin tooling, and agents that call TwittrAPI APIs from your backend. Webhook handlers react to TwittrAPI events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced TwittrAPI records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per TwittrAPI API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/twittrapi in the open repo. When TwittrAPI ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your TwittrAPI data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store TwittrAPI data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put TwittrAPI on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive TwittrAPI operations. You can change a link's mode at hub.corsair.dev/me.