Sign in Book a demo
Back to Tools
Communication OAuth
Build Your Agent View X Documentation
x logo

X (Twitter) MCP Tools for AI Agents

Let an agent search recent posts, monitor mentions, publish threads, reply to conversations, and manage X Lists for each authorized user.

Available Tools

38 tools available in this integration

X.AddListMember

Add one or more users to an X List owned by the authenticated user.

X.CreateList

Create a new X List owned by the authenticated user.

X.DeleteList

Delete an X List owned by the authenticated user.

X.DeleteTweetById

Delete one of the authenticated user's tweets.

X.GetConversation

Fetch the conversation thread containing ``tweet_id``.

X.GetHomeTimeline

Fetch the authenticated user's reverse-chronological home timeline.

X.GetListMembers

List members of an X List.

X.GetListMembershipsForUser

List the X Lists the target user is a member of.

X.GetListTweets

List recent tweets from members of an X List, newest first.

X.GetMyMentions

Fetch recent @-mentions of the authenticated user, newest first.

X.GetOwnedLists

List the X Lists a user owns.

X.GetQuoteTweets

Fetch public quote tweets of the given tweet.

X.GetRepliesToTweet

Fetch public DIRECT replies to a given tweet (last ~7 days).

X.GetSpacesByCreator

List the live or scheduled X Spaces created by a set of users.

X.GetUserLikedTweets

List tweets a user has liked, newest-liked first.

X.GetUserTweets

Fetch tweets authored by a specific X user, newest first.

X.LikeTweet

Like a tweet as the authenticated user.

X.LookupSingleUserByUsername

Look up a user on X (Twitter) by their username.

X.LookupSpaceById

Look up a single X Space by its id.

X.LookupTweetById

Look up a tweet on X (Twitter) by tweet ID.

X.LookupTweetEngagers

List the users who liked or retweeted a tweet.

X.LookupTweets

Look up tweets by id (single or batched) on X.

X.LookupUsers

Look up X (Twitter) users by handle and/or numeric user id.

X.PinList

Pin an X List to the authenticated user's profile.

X.PostThread

Post a multi-tweet thread as the authenticated user.

X.PostTweet

Post a new tweet as the authenticated user.

X.RemoveListMember

Remove one or more users from an X List owned by the authenticated user.

X.ReplyToTweet

Reply to a tweet on X (Twitter).

X.Retweet

Retweet a tweet as the authenticated user.

X.SearchRecentTweetsByKeywords

Search for recent tweets (last 7 days) on X (Twitter) by required keywords and phrases.

X.SearchRecentTweetsByUsername

Search for recent tweets (last 7 days) on X (Twitter) by username.

X.SearchSpaces

Search live and scheduled X Spaces by title.

X.SearchTweetsByKeywords

Search tweets on X by structured filters across X's recent ~7-day index.

X.UndoRetweet

Undo a previous retweet by the authenticated user.

X.UnlikeTweet

Remove the authenticated user's like from a tweet.

X.UnpinList

Unpin an X List from the authenticated user's profile.

X.UpdateList

Rename a list, edit its description, or toggle its visibility.

X.WhoAmI

Get the authenticated X (Twitter) user's profile.

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find recent complaints about our product and draft replies." Arcade helps it use the right X tools without guessing tweet IDs, user IDs, or conversation relationships.

Up to 100x fewer tokens

X search and lookup results return focused tweet and user records instead of loading whole timelines or every conversation into the model. The agent gets enough context to decide what to inspect next.

Complete the workflow end to end

Search a conversation, inspect replies, identify the relevant users, draft a response, and publish it after approval through one toolkit designed around the complete X task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing X (Twitter)

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For X (Twitter), you can implement some of these policies:

Access when tools are listed for a user
  • Hide X.DeleteList from agents unless the roles your IDP marks as social administrators are active, so an agent cannot remove a shared list without the right authority.
  • Restrict X.DeleteTweetById to agents operating under your content-owner role, so ordinary workflows cannot erase published posts.
  • Deny X.UpdateList to agents outside your social-administrator role, so an agent cannot change a list's name, description, or visibility.
Pre-execution before each tool call
  • Require human approval before X.PostTweet runs, so an agent cannot publish an unreviewed statement from your account.
  • Block X.PostThread when any post contains credentials, access tokens, or customer data, so an agent cannot publish secrets across a thread.
  • Refuse X.ReplyToTweet when the reply includes threats, personal contact details, or unsupported claims about a customer, so the agent cannot create a public incident.
Post-execution after the tool returns
  • Redact X.GetConversation results, stripping phone numbers, email addresses, access tokens, and private customer details from tweet text before it reaches the model.
  • Strip phone numbers, email addresses, and account credentials from X.GetMyMentions results, so an agent can triage mentions without receiving exposed personal data.
  • Deny X.GetHomeTimeline output when the result contains content from accounts on your restricted-user list, so the model cannot inspect posts your organization has blocked from automated review.

How to use X (Twitter) with your agent

Connect X (Twitter) to an MCP client with Arcade's managed per-user OAuth. Follow the setup to give each user’s agent access to that user’s account.

Your questions, answered

An X (Twitter) MCP server exposes X actions as structured tools an AI agent can call through the Model Context Protocol. After a user authorizes their account, the agent can search tweets, inspect conversations, manage lists, and publish permitted content.

X does not provide a first-party MCP server for these actions. Arcade provides the X integration, user-level OAuth, a consistent MCP and tools interface, approval and redaction policies, and scope controls across clients and agents.

Arcade agents can search recent tweets, inspect conversations, mentions, replies, quote tweets, users, Spaces, timelines, and list activity. They can also post tweets and threads, reply, retweet, like, delete the user's tweets, and create or manage lists.

Arcade requests the X OAuth scopes required by the actions you enable, such as tweet.read, users.read, tweet.write, like.read, like.write, list.read, list.write, space.read, and offline.access. Grant only the scopes needed for your workflow.

Yes. Each user authorizes their own X account through OAuth. Actions run under that user's authorization, so the agent can access and change only the account and permissions they approved.

Yes. Contextual Access policies can require human approval before consequential X actions such as posting, replying, retweeting, deleting a tweet, or changing a list. The call proceeds only after the policy's conditions are satisfied.

Arcade proxies X API calls and does not persist your content as part of normal tool execution. OAuth credentials are brokered and stored encrypted at rest, and the model never receives them.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the user's X authorization remains valid. If access is revoked, rotated, or can no longer be refreshed, calls stop until the user reconnects their X account.

X API rate limits, endpoint limits, and plan-level quotas still apply to calls made through Arcade. The applicable limits depend on the X API access tier and the endpoint used.

Ready to actually ship your agent?

Connect your agent to X (Twitter) with managed OAuth, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the X (Twitter) Quickstart