X
Xquik MCP Server
Details
- Endpoint
-
https://xquik.com/mcp - Transport
- streamable-http
- Docs
- https://docs.xquik.com/mcp/overview
Authentication
OAuth 2.0 oauth2 detected 2026-07-14
OAuth · resolves from well-known metadata OAuth 2.0 — self-onboarding
Point your MCP client at the server URL and approve access in the browser. The server accepts a Client ID Metadata Document (CIMD), so the client authenticates with its own hosted URL as the client_id — nothing to register.
Authorization: Bearer <credential> Sign in to the Xquik dashboard, open the account page at Dashboard account, and create an API key. The docs say API keys are managed from the dashboard and can also be created via the authenticated API key endpoint once you already have auth. Use the key as x-api-key for REST, or as Authorization: Bearer <key> for MCP clients that only support bearer auth.