Skip to main content
Any MCP client that supports HTTP transport can connect to xysq with a bearer token. Takes about two minutes.
1

Generate your API key

Open the generic connect guide in app.xysq.ai (Connect → Generic HTTP) and generate a key. The full value is shown exactly once; copy it right away. Use your personal key here, not an agent key: /mcp rejects agent keys, which belong to the SDK.
2

Copy your MCP config

xysq supports both streamable-http (v2, recommended) and legacy SSE. Use whichever your client supports:
Legacy SSE clients connect to https://api.xysq.ai/sse instead, same bearer header.Most modern MCP clients accept this shape directly. If yours uses a different field naming, the values stay the same; just remap url, headers.Authorization, and the transport name.
3

Test the connection

Before wiring xysq into your client, sanity-check the connection from the command line:
A 401 means the key was not accepted (wrong value, revoked, or an agent key). Anything else, including a transport complaint about a bare GET, means the host is reachable and your key got through; a network error means you can’t reach the host at all.Once that works, paste your config into the client and start the connection.
4

Verify the connection

Trigger any xysq tool call from your client. The in-app guide watches for the first call and marks the connection verified.
If your client doesn’t surface tool calls explicitly, try asking for context. Most MCP-aware clients invoke pull_context when asked to remember or look up something.