X (Twitter): connect your own account

Set up

Set up X (Twitter) in Claude Code, Codex or any agent

1Give this to your agent

in your agent's chat

set up olywork — https://olywork.com/llms.txt

2Or add the MCP server yourself

claude code

claude mcp add --transport http olywork https://olywork.com/mcp

ChatGPT

Settings → Connectors → add https://olywork.com/mcp as a custom connector.

Grok bot

Add https://olywork.com/mcp as a remote MCP connector in its tool settings.

Claude Desktop

Settings → Connectors → Add custom connector → https://olywork.com/mcp.

Cursor, Codex, any MCP client

Point it at https://olywork.com/mcp (HTTP transport).

CLI

curl -fsSL https://olywork.com/install.sh | sh

Plain HTTP

LangChain, CrewAI or any code: /call/<tool-id> + X-Olywork-Token: <token>. No SDK.

Why olywork.com

Why call X (Twitter) through olywork.com

Your account, held safely

Connect once; olywork.com keeps the credential server-side and injects it per call. No key on any machine.

Price before the call

The provider's own rate, $0.000 markup. How billing works.

Account billing

Calls through your own connection are not metered by olywork.

Your account connection

Connect your account with the provider's supported authentication method.

Switch by changing a word

Another provider is a different word in the prompt, not a new integration.

One key, the whole catalog

The same token calls AnyAPI, Bright Data, Just One API and 3,156 other tools.

The shelf

All 173 X (Twitter) tools

X (Twitter) · 173 tools

Recent tweets of a user by user id — engagement metrics · OAuth connection · live-verified · $0.005/result
List the recent posts of an X user (your own or any public account) x.x.user.posts
X bills the app owner $0.005 per post returned — pass max_results (5-100, default 10) deliberately; a default-sized page costs ~$0.05
Your connected X account profile — handle, followers · OAuth connection · live-verified · $0.01/result
Get the profile of the connected X account (handle, name, follower counts) x.x.user.profile
one user resource at the User read rate. NOT the $0.001 owned read: that needs the caller to own the developer app, and on a registry connect the app is olywork's
X user profile by username — followers, bio, verified · OAuth connection · live-verified · $0.01/result
Get any public X user's profile by handle x.x.user.profile.by_username
X bills the app owner $0.010 per user resource returned; the batch route (/2/users/by?usernames=a,b,c) is priced per user too, so batching saves rate-limit windows, not money
Stream activity events in real time · OAuth connection · account management · $0.005/result
Activity Stream x.x.activity-stream
X publishes no rate for this route's resource, so olywork meters it at $0.005 per resource — the same figure the proxy falls back to
Add members to a group chat conversation · OAuth connection · $0.015/call
Add members to a Chat group conversation x.x.add-chat-group-members
X's rate card, dm create: $0.015 per request; which row applies is a judgement call, and this takes the dearer reading
Add encryption keys to a chat conversation · OAuth connection · helper · $0.015/call
Add Conversation Keys x.x.add-conversation-keys
X's rate card, dm create: $0.015 per request; which row applies is a judgement call, and this takes the dearer reading
Add a member to a List · OAuth connection · $0.005/call
Add Lists Member x.x.add-lists-member
X's rate card, list manage: $0.005 per request
Add an encryption public key · OAuth connection · helper · $0.015/call
Add public key x.x.add-user-public-key
X publishes no rate for this route's resource, so olywork meters it at $0.015 per request — the same figure the proxy falls back to
See all 173 X (Twitter) tools on the catalog →

Reliability badges come from live traffic through olywork.com. Live-verified means a successful provider check; it does not verify every request variant.

Questions

Before you start

Do I need a X (Twitter) account?

Yes. This is an own-account connection: you sign in to X (Twitter) once and your agent uses that connection through your olywork.com token. Calls on it are never metered.

How do I add X (Twitter) to Claude Code?

Run: claude mcp add --transport http olywork https://olywork.com/mcp. One MCP server carries X (Twitter) and the rest of the catalog.

Which frameworks does it work with?

Anything that speaks MCP (Claude Code, Claude Desktop, ChatGPT, Codex, Cursor, Grok) and anything that can make an HTTP request (LangChain, CrewAI, LlamaIndex, plain code).

Is this the official X (Twitter) MCP server?

No. olywork.com serves X (Twitter)'s real API through its own metered proxy: the request is the provider's own, the credential is injected server-side, and the answer is relayed verbatim. The official X (Twitter) channels are linked above.