X MCP server: scoped X access for every agent
X MCP connects an agent to X's official remote tool surface for authorized account and publishing workflows. AIPx provides a Pro-only connection with user-context OAuth, then lets you assign the discovered capabilities to each agent without copying provider credentials into every client.
What your agent can do with X
The table labels capabilities rather than inventing exact tool names: search, profiles or timelines, bookmarks, publishing and account activity. The authenticated upstream catalog was not available as a complete inventory for this snapshot. Inspect the actual discovered names, descriptions and vendor permissions before enabling an operation.
| Tool | What it does | Access | Mode |
|---|---|---|---|
| Post/user search (capability) | Search posts and users | read | Allow |
| Profile/timeline lookup (capability) | Read authorized account data | read | Allow |
| Bookmark reads (capability) | Read bookmarks | read | Allow |
| Publish/manage posts or Articles (capability) | External publishing | write | Confirm |
| Bookmark/follow/like mutations (capability) | Change account activity | write | Confirm |
Source labels describe the checked connection. Live discovery and provider access determine availability; account-specific agent names may be normalized. Modes in this table are recommendations, not a change to upstream permissions.
Capability snapshot: 14 October 2026 · provider source
Separate research from publishing. A research agent can gather authorized post and profile context without being able to publish, like or follow. A publishing assistant should show the exact target account and final text before any externally visible action.
X account access depends on the provider’s API permissions, entitlements and quotas. AIPx Pro enables this gateway connector; it does not include a separate X developer entitlement or guarantee every endpoint for every account. A missing capability needs a vendor access check, not an invented tool identifier.
The official remote endpoint is api.x.com/mcp. Direct setup can use the official xurl bridge with developer-app OAuth, or app-only bearer access for supported read-only endpoints. Those credential paths are distinct from AIPx’s user-context connection.
X MCP server: official remote, xurl and AIPx
| Route | Credential path | Main fit |
|---|---|---|
| Official remote X MCP | Supported X authentication | Direct use of the vendor surface |
| Official xurl bridge | Developer-app OAuth or supported app-only reads | CLI-oriented provider access under your control |
| X through AIPx | User-context OAuth with a Pro connector | Shared account access with agent-specific tools |
The official X MCP documentation defines supported access, and the xurl repository describes the official bridge. These are related provider routes, not evidence of three independent equivalent servers.
Direct access can be simpler for one X-only client. AIPx adds another service processing account requests and requires its $3/month Pro plan. Its benefit is reusing the authorized connection with different agent policies; X API billing and quotas remain separate.
Connect X to Claude, Claude Code, Cursor or Codex
Enable the X connector on AIPx Pro and complete user-context OAuth. Inspect the live tool catalog and your X API entitlements before assigning a publishing workflow.
- Open the AIPx dashboard, choose X under Integrations and complete its connection form or authorization.
- Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
- Copy the agent’s complete URL. The examples below use
AGENT_ID; replace it with the actual value from your dashboard.
An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting X; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.
Connect Claude to X
In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when X is the only service you need.
X MCP in Claude Code
claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_IDAuthorize with /mcp, then inspect the authenticated X tool catalog. Begin with account identity or supported reads, keeping publishing hidden. Claude Code MCP setup explains endpoint configuration.
X MCP in Cursor
Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:
{
"mcpServers": {
"aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
}
}Sign in from Cursor and verify the discovered X capability names instead of pasting old identifiers. Keep publishing unavailable during research. The Cursor MCP guide covers client configuration.
X MCP in Codex
codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp listCodex uses the HTTP endpoint and browser OAuth; it does not need a copy of the X credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.
Where ChatGPT custom MCP is enabled, add the X endpoint from an AIPx Pro agent. Check provider entitlement and keep external publishing behind review. ChatGPT MCP setup explains account and workspace eligibility.
Scope X research and publishing per agent
For a researcher, allow only the needed search and account reads and hide every publish, follow, like or bookmark mutation. For a publishing assistant, add specific operations on Confirm after inspecting their descriptions. Avoid granting a broad account surface for a narrow content task.
Confirm is an execution hint whose handling depends on the client. Keep approvals enabled; if posting must be impossible, use Hide. MCP permissions describes the enforced callable-tool boundary.
Exa can supply broader web evidence, and Notion can hold the approved source brief. Yandex Direct is a separate advertising connection with independent spending and campaign controls.
X publishing, API billing and discovery limits
Do not promise a capability solely because a provider catalog description mentions posts or Articles. Check the authenticated tool list and current account entitlement. Tool names can change, and different authentication paths can expose different operations.
External publishing is difficult to take back completely once other users have seen it. Keep the final text and destination account visible before client approval. Do not treat a draft or a search finding as authorization to publish. AIPx does not bypass X API billing or limits.
Browse all MCP integrations to choose another connection for this agent.
The X gateway connector requires AIPx Pro at $3/month; check AIPx pricing for gateway plans and keep provider or client charges separate.
What to ask your agent
Name the X account and a bounded task. Ask for source identifiers and a proposed result before approving a change.
FAQ
Can I connect X to Claude?
Yes. Connect X in AIPx, create an MCP agent and add its copied URL as a Claude custom connector when your account and workspace permit. Choose tools before using the connection.
How do I add X MCP to Claude Code?
Run claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID with your actual agent endpoint, then use /mcp to authorize and inspect tools. See Claude Code MCP setup.
Is the X integration free?
No. The X connector requires AIPx Pro at $3/month. Provider subscriptions, API charges and the AI client's own connector access are separate. See AIPx pricing.
Can I connect two X accounts?
Yes. Add separately authorized X connections and choose each account's tools independently for the agent. One endpoint can include both; it does not merge accounts or synchronize provider data.
Can my agent change X data?
Yes, when the discovered catalog and your X permissions allow it. Publishing and activity changes should be Confirm or Hide. This page uses capability labels because exact authenticated tool identifiers were not verified.
When should I use the official X connection?
Use a direct vendor connection when one service and one client meet your needs and you prefer fewer services handling data. For an API-only service, that can mean using the official API or a compatible server you maintain. AIPx adds shared connections and agent-specific rules.