Any MCP client
Connect any MCP client to Unitley with the server URL and an access token in the Authorization header. Covers transport, errors and limits.
If your agent is not covered by its own guide, it can still use Unitley as long as it speaks MCP over HTTP and can send a fixed Authorization header. This page has everything such a client needs.
The two things to enter
Server URL
https://console.unitley.com/api/mcp
Header, on every request, with a token from the Connect page in place of the placeholder:
Authorization: Bearer YOUR_UNITLEY_TOKENThe scheme name Bearer is not case-sensitive, but there must be a space between it and the token. A Unitley token starts with unt_.
A client that can only start local servers, over stdio, can reach Unitley through the mcp-remote bridge, the way the Claude Desktop guide does.
Transport
- Streamable HTTP. Send JSON-RPC messages with
POSTto the server URL, withContent-Type: application/json. - Stateless. Unitley keeps no session between requests. A client on a 2025 version of the protocol that opens a
GETstream or sendsDELETEto end a session gets a 405, because there is nothing to stream or end. - No subscriptions. Unitley publishes no change events. A
subscriptions/listenrequest is answered as an unknown method: HTTP 200 with JSON-RPC error-32601. The tool list does not change during a connection, solistChangedis false. - Requests up to 256 KB. A larger body gets a 413. A body that is not valid JSON gets a 400 with JSON-RPC error
-32700. - Up to 60 seconds per request. The slowest tool, player props, can take most of a minute when Unitley has to fetch fresh props. Give your client a tool-call timeout of at least 60 seconds.
- Desktop and server clients only. A client that sends no
Originheader, which covers desktop apps, terminals and servers, is accepted. A browser calling from another website is refused.
The server
The server introduces itself as unitley, version 0.1.0. It offers:
- Tools: 20 of them. See Every tool.
- Resources: Unitley's knowledge notes, as Markdown. See Resources.
- Prompts: ready-made starting points. See Prompts.
- Instructions: the rules every agent receives when it connects. See The MCP server.
Every token sees the full tool list, including log_bet, settle_bet and save_recommendation. With a read-only token, calling one of those returns an insufficient_scope error rather than hiding the tool.
Errors and limits
A tool that fails still returns a normal tools/call result, with isError set to true. The message is in the text content, and structuredContent.error holds the code, message, any issues with the arguments, and retryAfterSeconds when you should wait.
Problems before a tool runs come back as HTTP errors:
| Status | When |
|---|---|
| 401 | The header is missing or malformed, or the token is unknown, revoked or expired. The body is an OAuth error, {"error":"invalid_token","error_description":"…"}, not a JSON-RPC error, and a WWW-Authenticate: Bearer challenge repeats the description. |
| 403 | The request came from a browser on another website, or to the wrong host. |
| 413 | The body is over 256 KB. |
| 429 | Too many requests from your address, over 300 a minute. Wait for the Retry-After seconds. |
| 503 | Unitley could not serve the request. Try again in a moment. |
Tool calls also count against a budget per token and per account, 60 a minute and 120 a minute. Going over returns a rate_limited tool error with retryAfterSeconds. See Rate limits and Troubleshooting.
Not an MCP client
If your agent or script cannot speak MCP at all, call the same tools over the REST API.