Social media · https://api.x.com
set up treg — https://treg.to/llms.txt
claude mcp add --transport http treg https://treg.to/mcp
Settings → Connectors → add https://treg.to/mcp as a custom connector.
Add https://treg.to/mcp as a remote MCP connector in its tool settings.
Settings → Connectors → Add custom connector → https://treg.to/mcp.
Point it at https://treg.to/mcp (HTTP transport).
curl -fsSL https://treg.to/install.sh | sh
LangChain, CrewAI or any code: /call/<tool-id> + X-Treg-Token: <token>. No SDK.
Using treg, get a user's public profile. Show me the price first.
treg call x.x.user.posts --query id=44196397 --query max_results=5 --query tweet.fields=id,text,created_at,public_metrics
Connect once; treg.to keeps the credential server-side and injects it per call. No key on any machine.
The provider's own rate, $0.000 markup. How billing works.
Calls through treg's OAuth app are metered under this server's billing policy.
Calls through treg's OAuth app are metered under this server's billing policy.
Another provider is a different word in the prompt, not a new integration.
The same token calls AnyAPI, Bright Data, Just One API and 3,284 other tools.
x.x.user.postsx.x.user.profilex.x.user.profile.by_usernamex.x.activity-streamx.x.add-chat-group-membersx.x.add-conversation-keysx.x.add-lists-memberx.x.add-user-public-keyReliability badges come from live traffic through treg.to. Live-verified means a successful provider check; it does not verify every request variant.
Every provider that does this job, side by side: price per billing unit, measured success rate and speed.
Every provider that does this job, side by side: price per billing unit, measured success rate and speed.
Yes. Connect your X (Twitter) account through OAuth. Calls through treg's OAuth app are metered under this server's billing policy.
Run: claude mcp add --transport http treg https://treg.to/mcp. One MCP server carries X (Twitter) and the rest of the catalog.
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).
No. treg.to 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.