X MCP Server: API Access, Docs Search and Automation Rules
- X API MCP and Docs MCP serve different purposes; reading documentation does not authenticate a social account.
- App-only and user-context access differ. Verify the actual account, scopes and available tools for the required task.
- X expressly prohibits non-API website scripting; a local browser session does not establish an exception.
- Keep content preparation, permitted execution and observed results separate. NoobClaw’s public local-video record proves a creative output only.
X documents two hosted MCP services with different jobs: one accesses the X API and the other searches developer documentation. Connecting an assistant does not supply every account permission, remove API charges or make browser scripting a permitted alternative. This review explains the current distinction and a practical decision framework for evaluating the actual task. It does not rely on a reported endpoint count, an unverified launch date or a promise that local operation protects an account.
Identify the service, authenticated account, requested action and applicable permission. A discovered tool is not evidence of a completed or permitted publication.
The API service and documentation service are different products
The official MCP guide checked on October 11, 2026 identifies api.x.com/mcp for X API tools and docs.x.com/mcp for documentation search. The former describes account and content functions; the latter supplies search_x and get_page_x to find and read developer material. Do not interpret a successful documentation search as an authenticated account connection. Those services can work together, but their outputs establish different things.
An integration decision should begin with a concrete deliverable. A researcher finding the correct media reference may need only documentation access. An operator retrieving permitted account information needs the relevant API path. Preparing text for review can remain a separate creative task. Treat these as different work requirements rather than ranking all MCP connections by the number of tools advertised.
The earlier article emphasized a reported June launch and more than two hundred endpoints. This current evaluation does not verify that date or endpoint total. It uses the present official guide and the exact task a buyer needs. An extensive advertised surface would not establish that a particular account can invoke every operation, nor that every invocation produces a usable result.

- Service: API calls or documentation search. The documentation service does not post to a social account.
- Identity: App-only or specific user context. Confirm the intended account and scopes; a visible tool is not unrestricted access.
- Action: Read, draft or write. Evaluate the exact supported task and applicable platform conditions.
- Evidence: Observed response and result. No browser-scripting exemption or account-protection guarantee.
Authentication establishes context, not a universal permission
The X guide distinguishes app-only Bearer access for eligible read operations from OAuth user-context access through the local xurl bridge for user actions. It says the bridge requires the developer’s own app and that the authorized user is the account active during login. Check those distinctions before assuming the assistant acts as the account you intended. This is a description of official requirements, not a connection tested in this review.
A hypothetical agency researcher and a brand owner may share the same desired summary while needing different data and authority. Write down whose information is requested, which account should supply it and whether a resulting write is necessary. A read-only brief can be completed without turning the exercise into a public-posting experiment. If the required account context cannot be verified, retain that limitation rather than expanding permissions to see what happens.
The practical record should contain the task, intended account, permission scope and observed result. It should not contain exported tokens, private conversations or unnecessary personal information. An assistant-generated plan and a successful login are separate observations. Review the actual requested operation and its output; do not infer that every future task inherits the same suitability.
Platform method and activity rules remain separate checks
X’s current automation rules prohibit non-API automation such as scripting its website. Using an account’s logged-in browser session therefore does not establish a permitted substitute for API access. The same document distinguishes account authorization from express consent to automated actions and imposes action-specific conditions. A software product’s technical ability is not a platform exemption.
The April 2026 Automation Rules require prior written, explicit X approval for AI reply bots and prohibit automated likes. They also state a prohibition on automated hiding of replies. However, the October 1, 2026 changelog and current Grok moderation guide describe automatic hiding of high-confidence violations in replies to the authorized user’s own Posts, with review and undo controls. These official documents conflict on automated hiding; we found no explanation reconciling the rule or establishing an exception. Permission for a specific auto-hide workflow remains unresolved. An API endpoint’s availability does not settle that question, and slower pacing does not erase a method restriction.
For a hypothetical publishing brief, an editor can separate generating a proposed caption from sending it externally. Review the draft first, identify the actual execution route and preserve the relevant permission evidence before any external action. This framework does not predict penalties, guarantee approval or diagnose an existing account restriction. An actual platform notice should be assessed on its own stated reason and available review path.
Evaluate useful output rather than assuming integration removes work
A tool connection can reduce one integration step without eliminating account setup, access costs, editing or verification. Define an acceptance criterion before comparing a custom integration, an official connection and a separate creative tool. For example, a useful research summary should identify its sources and distinguish retrieved information from interpretation. An attractive summary with missing evidence does not satisfy that brief merely because the interface is convenient.
Use an explicit hypothetical handoff: one operator requests a summary of relevant product discussion, an editor checks the supported sources, and a brand owner decides whether a public response is appropriate. Preserve the intermediate outputs and identify what remains unknown. This example illustrates a review design; it is not a measured agency workflow, a benchmark of time saved or proof that a named client supports every step.
Costs should follow the selected service and actual operations. X’s February 6, 2026 changelog describes usage-based access alongside then-existing arrangements. That dated note does not establish an account-specific current invoice or a universal fixed-tier purchase requirement. This review does not quote an authenticated API bill or a price per completed campaign. Compare a dated offer for the required operations and record any untested dependency rather than inventing a break-even figure.
NoobClaw’s relevant evidence concerns creative preparation
NoobClaw publishes this article. Its public caption, hook and spoken-script tools address text preparation, while the documented desktop video workflow addresses a local creative export. Neither output is evidence of an X MCP connection, an approved reply bot or a permitted browser-scripted publication. If the missing job is reviewed creative material, evaluate that output directly. If the missing job is API access, evaluate the actual account and operation.
The product distinction matters when selecting keywords and a landing page. A visitor looking for X MCP authentication is not necessarily looking for a video-production tool. This article should answer that integration question accurately and point to creative tools only where the reader has a separate production need. It should not position a browser profile as an alternative permission system or infer credential isolation from an unperformed security assessment.
Compare one accepted deliverable and the remaining work instead of a universal claim that one architecture is safer or faster. Inspect the text, video or retrieved response at the level required for its intended use. A completed creative export, an authenticated API request and an externally visible post are three different records. Preserve those distinctions when deciding whether any product addresses the bottleneck.
Choose the output you need: post-caption drafts, opening-line drafts or spoken-script drafts. These text tools have a limited anonymous allowance; they do not transcribe or publish a video.
For the related content and workflow decisions, read X Account Warm-Up: No Proven Safe Automation Schedule and X Video Limits: API, Premium Status and Upload Errors. Each review has its own evidence and scope.
An inspectable creative record, with its limits intact
The public NoobClaw record dated October 10, 2026 documents a supplied 441-character English script and a 32.6-second local video export at 1080 × 1920 and 30 frames per second. It identifies generic or off-topic stock material requiring scene review; voice quality and footage rights were not independently approved. That is a concrete record of one production stage. It contains no authenticated X MCP response, external post or comparison of account protection. A team can inspect that file to judge the remaining creative work without treating it as an integration demonstration.
The script-to-video guide and public creative execution record document a local video result, not external-platform publication. Check the current product offer against the supported action you need.

Frequently asked questions
Does Docs MCP let an assistant publish to X?
The official documentation service searches and retrieves developer pages. Account operations belong to the separate API service and require the applicable context and permissions.
Does an official MCP connection remove the need to check consent?
No. The automation rules distinguish account authorization from express consent to automated actions and require action-specific conditions.
Is a local browser session an approved workaround?
X’s rules prohibit non-API website scripting. Local operation alone does not establish an exception or an account-protection guarantee.
Sources
Official material reviewed on October 11, 2026. Document conditions apply to their stated service and scope; the editorial examples are explicitly hypothetical.