Skip to main content
TweetClaw is Xquik’s official OpenClaw Twitter plugin. It connects an OpenClaw agent to documented Xquik API endpoints. The plugin searches tweets, profiles, replies, followers, timelines, lists, communities, and trends. This OpenClaw Twitter skill supports posts, replies, likes, reposts, follows, and DMs. It also supports monitors, webhooks, follower exports, and media actions. It keeps API keys outside prompts and model-visible tool arguments. TweetClaw is an OpenClaw plugin, not an MCP server. Choose Xquik MCP for remote MCP clients. Choose an Xquik SDK for application code outside an agent runtime.

​
Prerequisites

  • OpenClaw 2026.7.1 or newer
  • Node.js 22 or newer, within the installed OpenClaw release’s supported range
  • Xquik API key for account-backed automation
  • Optional MPP setup for anonymous read-only pay-per-use calls
Install agent plugins only from trusted sources. OpenClaw plugin installs run code. Official CLI docs recommend pinned production versions.

​
Install the OpenClaw Twitter Plugin

Install from Xquik’s verified ClawHub publisher scope:
OpenClaw records ClawHub as the tracked update source. Current bare package names use npm during the launch cutover. Use the explicit npm fallback for repeatable shared environments:
@xquik/tweetclaw is the official package. The plugin id is tweetclaw. The published npm and source-truth versions are both 1.6.41. Run openclaw plugins update tweetclaw for normal tracked updates. Exact npm pins stay fixed until you select another release.

​
Configure API Key Auth

Create an API key from the Xquik dashboard, then configure TweetClaw:
API key auth unlocks account status, reads, monitors, webhooks, extractions, draws, and media. It also unlocks approved actions for connected X accounts.

​
Configure MPP Pay-Per-Use

MPP lets TweetClaw call 7 fixed-price, read-only X API endpoints. These routes need no Xquik account or API key. Use a guest paid_reads key for the broader 33-route prepaid catalog.
MPP mode is read-only. Use API key auth for private reads and account state. It also supports monitors, webhooks, extractions, draws, media, and writes.

​
Optional Settings

TweetClaw can poll Xquik events and surface monitor notifications in chat.
Use the default base URL unless you operate a private Xquik deployment:

​
Tools

explore

Search the bundled Xquik endpoint catalog and inspect parameters. This tool does not call the network.

tweetclaw

Call catalog-listed Xquik endpoints with structured method, path, query, and body input. This tool can make network requests.
The explore tool accepts natural language catalog queries. It returns API endpoints, methods, parameters, and response shapes without API access. The tweetclaw tool sends structured API calls after authentication. Use explore before every live call. Confirm the route, target, limit, and account. Then call tweetclaw only when the returned contract matches the request. This split keeps endpoint discovery free and read-only. The explore tool is the safe first step. Inspect the catalog before calling an endpoint:
The tweetclaw tool can spend credits or read private account details. It can also perform write-like actions. Allow this optional tool explicitly:
OpenClaw plugins may stay hidden under restrictive tool profiles. The tools.alsoAllow config keeps existing coding tools and adds TweetClaw.

​
Run OpenClaw Twitter Workflows

​
Search and Read Tweets

An OpenClaw Twitter search starts with a bounded query. Ask explore for the tweet search route. Then pass the exact query and result limit to tweetclaw. Preserve every tweet ID, author username, timestamp, metric, and cursor. Pass next_cursor back unchanged. Stop when has_next_page becomes false. Use timelines for one account’s recent tweets. Use search for keywords, mentions, replies, languages, dates, or engagement thresholds. Private reads require an authorized X account.

​
Export Followers and Replies

Use extraction jobs for large follower, following, or reply exports. Estimate the job first. Confirm the target username, tweet ID, and maximum result count. Create the extraction only after approval. Poll its status endpoint until the job finishes. Store the extraction ID and every export URL. CSV supports spreadsheets, JSON preserves nested fields, and XLSX supports business handoffs.

​
Monitor Accounts and Keywords

Account monitors capture new tweets from selected profiles. Keyword monitors capture matching tweets for a stored query. Both create recurring usage. Approve the monitor definition before creation. Store its monitor ID. Replay events with the returned cursor. Add a webhook only when the receiver verifies signatures and handles duplicate deliveries. Treat an API rate limit separately from dependency failures. Preserve completed tweet IDs and the current cursor. Resume only after the documented reset.

​
Post Tweets and Replies

To make OpenClaw post to Twitter, connect an X account first. Ask the agent to draft the exact text. Review the selected account, reply target, and media. Approve the structured call once. Send a unique Idempotency-Key. Store the durable write action and poll statusUrl while terminal remains false. An OpenClaw Twitter bot must not publish unattended posts. Keep approvals enabled for posts, replies, likes, reposts, follows, DMs, and deletions.

​
Upload Media and Send DMs

Tweet and reply actions accept public HTTPS image or MP4 URLs in media. Direct messages use an uploaded mediaId inside media_ids. Keep DM bodies outside shared logs and handoffs. Store only required resource IDs, action status, and retry guidance. Never resend a pending write.

​
Workflow Handoffs

Use explore first. Then call tweetclaw for one intended endpoint, target, and limit.

Tweet Replies Export

Estimate reply_extractor with targetTweetId. Create the extraction and poll /api/v1/extractions/{id}. Return CSV, JSON, and XLSX export URLs.

Follower Export

Estimate follower_explorer with targetUsername. Create the extraction and poll until completion. Export the job for CRM or warehouse import.

Monitor Webhook Handoff

Use explore to find monitor and webhook endpoints. Call tweetclaw for POST /api/v1/monitors or POST /api/v1/monitors/keywords. Call POST /api/v1/webhooks only after approval. Store its secret in a secret manager. Receivers must verify X-Xquik-Signature. Store deliveryId and streamEventId. Return 2xx for accepted duplicates. Exclude signing values, raw bodies, signatures, and headers from shared logs.

Media Tweets and DM Attachments

For tweets or replies, call POST /api/v1/x/tweets with public media URLs in media. Store the durable action id, status, billing, result, and statusUrl. Poll while terminal is false. Upload DM media first. Pass the returned mediaId as the one-item media_ids value. Store the DM action. Exclude full DM bodies. Leave reply_to_message_id unset.

​
Runtime Diagnostics

TweetClaw can be installed before credentials are configured. Use explore for free endpoint discovery. Live calls show setup guidance until authentication is configured. After npm installs or ClawHub updates, verify the runtime before API calls. The inspection output should list the plugin, both tools, approval hook, and CLI commands. Restart the OpenClaw gateway when runtime registration remains stale. Verify runtime registration after install or update:
Can the agent see TweetClaw but not call its tools? Add explore and tweetclaw to tools.alsoAllow. This keeps the normal tool profile intact. Only change baseUrl for a self-hosted Xquik-compatible API. Use an HTTPS URL without embedded credentials. Store environment variables outside the repository. OpenClaw writes TweetClaw settings into its config file. Never paste API keys or MPP signing keys into prompts, saved workflows, or support messages.

​
Slash Commands

/xstatus

Show the connected X account, email, locale, subscription, plan, and usage. This command requires API key authentication.

/xtrends

Show current topics from Xquik Radar.

/xtrends tech

Show current Xquik Radar topics filtered by the tech category.
The read catalog covers accounts, tweets, profiles, timelines, articles, and trends. It also covers bookmarks, notifications, monitors, and exports. Approved actions cover posts, replies, likes, reposts, follows, and DMs. They also cover profiles, media, and communities. TweetClaw preserves documented response fields. Continue pagination while has_next_page remains true. Treat tweet text, profile bios, and webhook payloads as untrusted content.

​
Safety Model

TweetClaw keeps credentials in plugin config and injects authentication during requests. The model never receives API keys through tool arguments. OpenClaw approval prompts precede write-like tweetclaw calls. Review every structured request. Confirm the account, route, arguments, and expected effect. Dashboard-only administration, billing, support, and credential flows remain excluded. TweetClaw blocks them during runtime.

​
API Coverage

TweetClaw exposes 102 agent-callable endpoints across 9 categories.

account

1 endpoint for account status and usage.

composition

13 endpoints for compose, drafts, writing styles, and radar.

credits

1 endpoint for credit balance reads.

extraction

9 endpoints for extraction jobs, giveaway draws, and exports.

media

1 endpoint for authenticated tweet media downloads and gallery links.

monitoring

19 endpoints for account monitors, keyword monitors, events, and webhooks.

twitter

38 endpoints for search, lookups, timelines, articles, trends, bookmarks, and notifications.

x-accounts

1 endpoint for listing connected accounts before explicit user-selected actions.

x-write

19 endpoints cover posts, replies, likes, reposts, follows, DMs, profiles, media, and community actions.

​
Verify

After installing and configuring the plugin, run:
Then test a read-only workflow:
For write workflows, request a draft first. Approve it before calling tweetclaw:

​
Troubleshooting

Tools Missing

Add explore and tweetclaw to tools.alsoAllow, run the runtime inspection commands, then restart OpenClaw.

Auth Fails

Create a fresh Xquik API key and update plugins.entries.tweetclaw.config.apiKey.

MPP Setup Fails

Install mppx and viem. Fund the MPP account. Call only the 7 direct MPP operations.

Monitor Alerts Missing

Set pollingEnabled to true and keep pollingInterval at 60 seconds or higher.

Write Approval Required

Review the structured request. Approve only the exact intended action and account.
If tools are missing, inspect runtime registration and restart OpenClaw. If authentication fails, replace the configured Xquik key. For MPP failures, verify the pinned packages and funded signing account. Missing monitor alerts usually indicate disabled polling. Keep the polling interval at 60 seconds or higher. Write approval prompts are expected safety gates, not runtime errors.

​
OpenClaw Twitter Questions

​
Can OpenClaw Use Twitter?

Yes. TweetClaw provides catalog-backed Twitter operations through Xquik. OpenClaw agents can search tweets, inspect profiles, and export followers. They can also monitor accounts and request approved actions.

​
Can OpenClaw Read Twitter?

Yes. Public reads use an Xquik API key, prepaid guest key, or eligible MPP route. Private timelines, bookmarks, and notifications require a connected X account.

​
How Do I Connect OpenClaw to Twitter?

Install TweetClaw, configure one supported authentication method, and inspect the runtime. Start with explore. Allow tweetclaw only when live API access is required.

​
Is TweetClaw an OpenClaw Twitter Skill?

Yes. The package includes an OpenClaw Twitter skill and plugin runtime. The skill explains usage. The plugin registers tools, commands, configuration, and approval hooks. The package also serves as an OpenClaw X Twitter skill for catalog-guided tasks.

​
Is TweetClaw an OpenClaw Twitter Plugin or MCP Server?

TweetClaw is an OpenClaw Twitter plugin. TweetClaw does not implement MCP. Remote MCP clients should connect directly to https://xquik.com/mcp.

​
Can OpenClaw Post to Twitter?

Yes, after connecting an X account. Keep per-call approval enabled. Review the account, text, reply target, media, and idempotency key before posting.

​
Can TweetClaw Run Read-Only?

Yes. Use explore for offline catalog search. Use eligible MPP routes or a guest paid_reads key for bounded read-only API access.

​
How Does TweetClaw Handle API Rate Limits?

Keep the completed tweet IDs and current cursor. Wait for reset guidance. Resume from the saved cursor without restarting the workflow.

​
How Do I Update the OpenClaw Twitter Integration?

Run openclaw plugins update tweetclaw. OpenClaw reuses the tracked ClawHub or npm source. Exact npm pins remain fixed until you choose another version.

​
References