X Use
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X_USE_APP | No | Registered app name in xurl. Recommended. | |
| X_USE_USER | No | Existing OAuth2 username in xurl. Recommended. | |
| X_USE_XURL_BIN | No | Path to xurl; defaults to `xurl` on `PATH`. | |
| X_USE_TIMEOUT_MS | No | Per-command timeout, 1–120 seconds. | |
| X_USE_SKILLS_ROOT | No | Override the installer's Skill root. | |
| X_USE_INSTALL_ROOT | No | Override the installer's application-data directory. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Read-only X API v2 access through the user's existing official xurl OAuth2 authentication. No write tools are exposed. Never infer permission to post, reply, DM, follow, like, bookmark, delete, or upload media. All tool results are JSON. Errors use unauthenticated, forbidden, rate_limited, not_found, invalid_request, or unknown.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| x_postA | Read one public/visible X post by URL or numeric ID. Returns upstream data, includes, and structured pagination/error envelopes. Read-only. |
| x_userA | Look up an X user by @username, username, or numeric user ID. Read-only. |
| x_user_postsB | Read posts authored by an X user. The username is resolved to a user ID first when needed. Read-only. |
| x_searchA | Search X posts. scope=recent covers the last 7 days; scope=all requests full-archive search and may be forbidden by account entitlement. Read-only. |
| x_threadA | Resolve a post's conversation_id and read posts in that conversation. Recent scope only covers the last 7 days; full scope may be forbidden. Read-only. |
| x_mediaA | Read media metadata by media key. The direct endpoint may be forbidden when the developer App is not enrolled in a Project; the error is returned without fabricating data. Read-only. |
| x_statusA | Check xurl version and safe auth metadata, verify OAuth2 user access, and read the developer credit balance. Does not print tokens or write to X. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| x-use | Usage, authentication, error, and write-permission rules for the X Use MCP. |
| x-api-investigation | Versioned source-backed capability, authentication, pricing, rate-limit, and architecture findings. |
TDQS
Scored across 7 tools
Each tool maps to a fairly distinct target: search, single post, user lookup, user timeline, media, thread, and status. The only mild overlaps are x_post vs x_thread (both return posts) and x_search vs x_user_posts (both return post collections), but the descriptions make the boundaries clear.
All tools use a consistent 'x_' prefix with snake_case, keeping them visually grouped and predictable. The only wrinkle is that x_post is a noun-style name that could be misread as a write action, though 'Read-only' in the description resolves it.
Seven tools is a tight, well-scoped set for an X read client, with no redundant entries. Every tool covers a distinct resource path (search, post, user, timeline, media, thread, diagnostics).
Read coverage is solid across posts, users, timelines, threads, and media, plus an auth/credit diagnostic. However, the surface is entirely read-only with no write operations (post, reply, like, repost, follow), and common reads like followers/following lists or engagement metrics are absent, which will limit many agent workflows.