Xquik MCP Server

Search Xquik's public docs to answer questions about its X (Twitter) API, MCP setup, SDKs, errors and limits. Queries reach only the read-only docs server. Free.

Execute JavaScript against Xquik's X (Twitter) API at https://xquik.com/docs. Reads cost 1 credit per result, 2 per analyzed post & 5 per article. 1,000 credits cost $0.12-$0.15. Writes cost 10 credits & posts from 30. Empty & failed reads are free. search returns endpoints, parameters & response schemas. The sandbox declares `interface XquikRequest { path: string; method?: "GET" | "POST" | "PUT" | "PATCH" | "DELETE"; query?: Record<string, string | number | boolean | undefined>; body?: unknown } declare const xquik: { result: unknown; request<T = unknown>(options: XquikRequest): Promise<T> }`. request() returns the body as the API sends it, as the response schema from search describes it. code is an async arrow function. Fields use snake_case, & camelCase reads work too. A missing field reads as undefined & warns with the available keys. An absent field may need a request parameter. Output holds up to 24,000 characters, so large arrays fit after projection. A call may send requests for 54 seconds. Paged reads return a cursor, so a few pages fit 1 call. Independent reads can run together with Promise.all. A result_id from an earlier answer lets a later call project its saved data through xquik.result. Authentication & idempotency headers are injected, so code holds no credentials. The sandbox has no filesystem or general network access. A failed request throws an Error naming its method, path, HTTP status & request ID, then the API's error body. Example ```js async () => xquik.request({ path: "<path from search>" }) ```

Search the current credential's Xquik OpenAPI catalog for X (Twitter) operations. The sandbox has no network access. spec is global and the async function's first argument. spec.paths maps paths to HTTP methods and operation objects. Fields include operationId, summary, description, readOnly, tags, parameters, requestBody, and responses. The catalog resolves inputs inline. Each response schema describes the body as the API sends it and execute's request() returns it. Response $refs point to reusable schemas in spec.components.schemas. An answer can hold operation descriptions, parameters & response schemas with their paths. Fields remain queryable independently. Answers hold up to 24,000 characters of JSON. Free. Examples ```js // Every tag async (spec) => [...new Set(Object.values(spec.paths).flatMap(Object.values).flatMap((op) => op.tags ?? []))] // Operations tagged Users async (spec) => Object.entries(spec.paths).flatMap(([path, methods]) => Object.entries(methods).filter(([, op]) => op.tags?.includes("Users")).map(([method, op]) => ({ method, path, summary: op.summary }))) // 1 operation's parameters async (spec) => Object.values(spec.paths).flatMap(Object.values).find((op) => op.operationId === "searchTweets")?.parameters ```

Return the Xquik account this connection is authenticated as. Takes no arguments. The id stays the same across token refresh, reconnection & permission changes. Free.