Connecting
Wire up an MCP client to the remote XQL server.
Endpoint
https://api.xcreener.com/mcpA single POST endpoint implementing the MCP Streamable HTTP transport, in stateless mode: every request is served by a fresh server instance, with no session affinity between requests. There's no local process to run and no session to manage; you only need an MCP client that can speak Streamable HTTP to a remote URL.
Every request requires the same Authorization: Bearer <your-api-key> header used by the HTTP API: generate a key from your account dashboard if you don't have one yet.
Claude Code
claude mcp add --transport http xcreener https://api.xcreener.com/mcp \
--header "Authorization: Bearer <your-api-key>"Other MCP Clients
Client support for remote HTTP MCP servers (and for attaching custom headers) varies. If your client only supports local/stdio servers, a stdio-to-HTTP bridge such as mcp-remote lets you configure it the same way you'd configure any local MCP server:
{
"mcpServers": {
"xcreener": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.xcreener.com/mcp",
"--header",
"Authorization: Bearer <your-api-key>"
]
}
}
}Check your specific client's documentation for its exact remote-server / custom-header configuration syntax.
A missing or unrecognized key is rejected before any MCP request
An MCP request (including initialize and tools/list) is rejected with 401 at the same gate the REST endpoints use, before any protocol handling runs, if the key is missing or doesn't match any stored key. If your client can't connect or list tools, double check the header is being sent exactly as Authorization: Bearer <key>.
A recognized key from a non-Essential account can still connect and call xql_validate/xql_explain: the same subscription split as the REST API applies here. Calling xql_run without an eligible subscription returns a tool-level error (isError: true) rather than an HTTP status, since MCP tool calls don't carry their own response codes.