List replies to an X post

List replies to an X post

Returns the direct replies to one X post, each with its author's profile, engagement counts and media, plus a cursor for the next page.

Note: 1 credit per reply returned. id takes a post ID or URL-encoded post URL. Direct replies only: to search a thread, search posts with q=conversation_id:{id}. Reply visibility depends on X, so a missing row does not prove someone did not reply.

Set up

Use the first option your agent supports.

MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

{ "mcpServers": { "xquik": { "url": "https://xquik.com/mcp?codemode=false" } } }

Call the MCP tool getTweetReplies.

Server URL: https://xquik.com/mcp?codemode=false

Note: Native mode: one tool per API operation, named by its OpenAPI operationId. The plain https://xquik.com/mcp is Code Mode, with only docs, search, execute and whoami. Tools list before sign-in; the first tool call starts the OAuth sign-in.

CLI (official)

Install the command, then confirm it runs.

go install github.com/Xquik-dev/x-twitter-scraper-cli/cmd/x-twitter-scraper@latest
x-twitter-scraper --version

Run x-twitter-scraper x:tweets get-replies.

Set $X_TWITTER_SCRAPER_API_KEY in your environment first (get a key: https://dashboard.xquik.com/en/api-keys).

Note: Needs Go, with $(go env GOPATH)/bin on PATH. The variable holds the same xq_ key the REST API takes.

API (official)

• Base URL: https://xquik.com/api/v1
• Endpoint: GET /x/tweets/{id}/replies
• Auth: send the header x-api-key: $XQUIK_API_KEY
• Get a key: https://dashboard.xquik.com/en/api-keys
• Docs: https://docs.xquik.com/api-reference/overview

Note: Public reads need no X account; posting, DMs and private reads need one connected in the dashboard. Calls spend credits and a 402 means the balance is too low. A key always has the read scope; monitors and writes need their scopes added on the key.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

Rules

• Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
• Never print API keys.