Skip to main content
Xquik documentation is available as an MCP server at https://docs.xquik.com/mcp. AI tools can search the full docs site and retrieve indexed public pages during conversations. Those pages include API reference, guides, examples, and type definitions. This differs from the Xquik API MCP server at xquik.com/mcp. That server searches tweets, looks up profiles, exports followers, runs draws, and manages monitors. The docs MCP server is read-only and requires no authentication.

Agent route checklist

Read docs first

Use Docs MCP at https://docs.xquik.com/mcp for public docs, API parameters, examples, error codes, SDK guidance, and no-auth page retrieval.

Run account actions

Use API MCP at https://xquik.com/mcp for live X reads, writes, monitors, webhooks, draws, or extraction jobs. Authenticate with an API key or OAuth 2.1. Prefer OAuth when the client supports browser authorization.

Store outside chat

Use REST or generated SDKs when a backend must own retries, cursor storage, file downloads, queues, or batch orchestration.

Hand off results

Store the endpoint path, request parameters, returned IDs, has_more, next_cursor, export route, or webhook replay route before ending the agent run.

Quick connect

Use the contextual menu at the top of any docs page:
  • Copy MCP Server URL. Copies https://docs.xquik.com/mcp to your clipboard.
  • Copy MCP Install Command. Copies the npx add-mcp install command.
  • Connect to Cursor. Installs the docs MCP server in Cursor.
  • Connect to VS Code. Installs the docs MCP server in VS Code.

Search docs through NLWeb

GET or POST https://xquik.com/ask searches public docs through NLWeb 0.55. It needs no authentication. Never send secrets or private data.
Send JSON, form data, or query parameters. Structured 0.54 requests remain compatible. JSON uses conversational_search and lowercase response types. Set prefer.streaming to true for SSE. Streams emit start, result, and complete events.

Search docs through A2A

The public A2A 1.0 agent card lives at https://xquik.com/.well-known/agent-card.json. It advertises the JSON-RPC endpoint at https://xquik.com/a2a. Send a SendMessage request with A2A-Version: 1.0. The agent accepts text questions and returns the same public documentation results as NLWeb. It needs no authentication and cannot run extractions or account actions. The server does not advertise streaming, push notifications, or extended cards.

Setup

Web clients

  1. Open Claude Connectors or Customize > Connectors.
  2. Select Add custom connector.
  3. Enter:
    • Name: Xquik Docs
    • URL: https://docs.xquik.com/mcp
  4. Select Add.
  5. In a chat, select + > Connectors and enable Xquik Docs.

Coding agents

Verify with:

Additional coding agents

Manual Qwen Code configuration still uses httpUrl: "https://docs.xquik.com/mcp" under mcpServers.
See current coding-agent configuration for version-specific changes.

Editor clients

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):

Additional editors

Run cline mcp, add a Streamable HTTP server, and enter https://docs.xquik.com/mcp. In the IDE, use the MCP Remote Servers UI. Cline stores global MCP settings at ~/.cline/data/settings/cline_mcp_settings.json. Project settings use .cline/mcp.json.

Using both MCP servers

Connect both servers:
  1. Docs MCP (docs.xquik.com/mcp). The AI searches documentation to understand API parameters, error codes, and usage patterns.
  2. API MCP (xquik.com/mcp). The AI executes actions such as tweet searches, extractions, and monitor setup.
The AI decides which server to query based on context. A question about how draw filters work goes to the docs server. A request to run a draw goes to the API server. API MCP results use the normalized v1 contract: snake_case fields, date-time fields as Unix seconds, structured errors, has_more, and next_cursor. Docs MCP returns indexed documentation text and never executes account actions.

What gets searched

The docs MCP server indexes all public pages:
  • API reference (every documented operation)
  • Guides (workflows, error handling, rate limits, billing, extraction workflow, trends, webhook testing)
  • Webhook documentation (overview, signature verification)
  • MCP server setup and tools reference
  • OAuth 2.1 documentation
  • Architecture, troubleshooting, and type definitions
  • llms.txt (compact documentation index)