# How to connect X public data to OpenClaw (paste one key, 28 tools) > Connect X public data to OpenClaw with ClawLink: paste your X public data key once and 28 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/x-data The usual route to X public data access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical X public data setup: install one ClawHub skill, connect X public data in the browser, and OpenClaw can call real X public data actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to X public data. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect X public data** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect x-data # connect X public data (browser OAuth) npx -y @useclawlink/cli actions x-data # list available actions npx -y @useclawlink/cli run x-data --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect X public data in the [ClawLink dashboard](https://claw-link.dev/dashboard) — enter your X public data account details once. Verify the connection by asking OpenClaw: > Use X public data to xdata user profile and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once X public data is connected in the dashboard, that agent calls the same 28 X public data tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## X public data MCP for OpenClaw Looking for a X public data MCP server for OpenClaw? ClawLink connects X public data to OpenClaw and exposes 28 X public data tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes X public data integration](https://claw-link.dev/hermes/x-data) works the same way. ## What the OpenClaw X public data integration can do 28 X public data tools are ready for OpenClaw once the account is connected. ### All 28 X public data tools for OpenClaw | Tool | What it does | |---|---| | **User profile** `xdata_user_profile` | Public profile by handle | | **User posts** `xdata_user_posts` | An account's recent posts | | **Post detail** `xdata_post_detail` | One post with thread context | | **Post replies** `xdata_post_replies` | Replies to a post | | **Search** `xdata_search` | Search posts, people or media | | **Trending** `xdata_trending` | Trending topics by country | | **User media** `xdata_user_media` | An account's photo and video posts | | **User replies** `xdata_user_replies` | Replies an account wrote | | **User followers** `xdata_user_followers` | An account's followers | | **User following** `xdata_user_following` | Accounts it follows | | **User about** `xdata_user_about` | About this account facts | | **User affiliates** `xdata_user_affiliates` | An organization's affiliates | | **Users by IDS** `xdata_users_by_ids` | Profiles for several user ids | | **User live status** `xdata_user_live_status` | Is the account live now | | **Check follow** `xdata_check_follow` | Does A follow B | | **Check repost** `xdata_check_repost` | Did an account repost a post | | **Post replies latest** `xdata_post_replies_latest` | Newest replies to a post | | **Post reposters** `xdata_post_reposters` | Who reposted a post | | **Post transcript** `xdata_post_transcript` | Transcript of a video post | | **Thread** `xdata_thread` | A whole thread from one post | | **Article** `xdata_article` | Full text of an X Article | | **Search communities** `xdata_search_communities` | Search Communities | | **Community** `xdata_community` | One Community | | **Community members** `xdata_community_members` | A Community's members | | **Community posts** `xdata_community_posts` | Posts in a Community | | **List posts** `xdata_list_posts` | Posts from a List | | **List members** `xdata_list_members` | Accounts on a List | | **List followers** `xdata_list_followers` | A List's followers | ## Example prompts **Xdata User Profile** > Use X public data to xdata user profile and walk me through the result in plain English. **Xdata User Posts** > Use X public data to xdata user posts and walk me through the result in plain English. **Xdata Post Detail** > Use X public data to xdata post detail and walk me through the result in plain English. **Xdata Post Replies** > Use X public data to xdata post replies and walk me through the result in plain English. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual integration wiring plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want X public data working from chat. | | Manual | ClawLink | |---|---|---| | **Setup flow** | Collect and store the right X public data credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link X public data without custom integration screens. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for X public data. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right X public data actions to the runtime in a format your agent can reliably use. | 28 tools for X public data are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes X public data to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect X public data in the browser, and the 28 tools above work from chat. There is no SDK and no config file, and the X public data key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the X public data skill but can't call the tools The ClawHub skill teaches OpenClaw about X public data, but the calls run through the ClawLink plugin and your connected account. Make sure X public data is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect X public data from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling X public data tools X public data tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every X public data call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### X public data returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### The setup form accepts credentials but calls still fail Re-enter the credentials carefully and verify the account-level permissions for X public data. Basic and token-based integrations tend to fail on formatting mistakes or limited account roles. ### Is there a OpenClaw X public data integration? Yes. ClawLink is the fastest way to connect OpenClaw to X public data: link your X public data account once in the browser and OpenClaw can call the X public data API through 28 ready-made tools — no custom code or token handling. ### How do I add X public data to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink X public data skill from ClawHub, then you click Connect in the dashboard to authorize X public data. OpenClaw calls the tools from the next message — no config files, and the X public data key you paste is stored server-side instead of in your environment. ### How long does it take to connect X public data to OpenClaw? About two minutes. Sign in, click Connect next to X public data in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring X public data up myself? The alternative to ClawLink is usually manual integration wiring plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want X public data working from chat. ### OpenClaw installed the X public data skill but can't call the tools The ClawHub skill teaches OpenClaw about X public data, but the calls run through the ClawLink plugin and your connected account. Make sure X public data is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Stack Exchange](https://claw-link.dev/openclaw/stack-exchange) — Search and browse questions, answers, and developer knowledge - [Connect TikTok public data](https://claw-link.dev/openclaw/tiktok-data) — Read any public TikTok profile, video, comments, hashtag or search. Read-only and not your account: nothing to connect, paid per call from credit - [X (Twitter) tools](https://claw-link.dev/openclaw/twitter) — Post tweets, manage lists, search content, and analyze engagement