Last cheat update: 20-Nov-26 01:00 CS2 compatibility confirmed

AI assistant integration

Connect an AI assistant to Hexui with MCP

Use a compatible AI assistant to manage Counter-Strike 2 cloud profiles, explore access options or work with public CS2 developer offsets. You choose account permissions, and purchases finish through normal website checkout.

Connect your assistant

Public developer offsets: https://hexui.com/mcp/offsets/ — no login or subscription required.

Account and settings tools: https://hexui.com/mcp/ — sign in and approve account permissions.

  1. Open the custom MCP server or connector settings in an assistant that supports remote Streamable HTTP servers and OAuth.
  2. Add the endpoint for the tools you want as the server URL.
  3. For account tools, follow the sign-in link to Hexui. Check the application name and callback domain, then select the permissions you want to grant. The public developer endpoint skips this step.
  4. Return to your assistant. Ask for the published offset status, setting definitions or your existing profiles.

Support for custom MCP connections depends on your assistant and account plan. This page documents the Hexui service; it does not claim that every AI application supports custom servers.

Public CS2 offsets for developers

The public endpoint reads the same validated publication as the CS2 offsets browser and JSON API. It exposes schema fields, signature offsets, buttons and interfaces without access to customer accounts.

  • get_offset_status: inspect the publication build, manifest, timestamp, available modules and symbol counts.
  • search_offsets: find fields or symbols and return their exact paths, decimal values and hexadecimal display. Results are paginated, up to 50 per page.
  • get_offset_values: read up to 50 exact paths from one snapshot. Supply the expected build to detect a publication change. Missing symbols fail the whole request.
  • get_offset_export: get an existing module or category JSON URL, its response grouping and API limits.

For example: “Find published health fields and show their exact paths and build number,” or “Give me the JSON export URL for client.dll.” The same four developer tools are also available through the authorized customer endpoint.

Schema values are class-relative byte offsets. Buttons and interfaces use module-relative addresses. Signature entries can represent RVAs or member offsets; use each symbol according to its meaning. The publication build identifies the returned snapshot and does not guarantee that a newer game update is already covered.

MCP calls retain the website’s request limits. Direct JSON exports and generated API links retain their existing limits and expiry. Create persistent custom selections using the offsets browser. MCP does not extract binaries, change the updater or publish data.

Public developer tool schemas · GitHub mirror

What your assistant can do

  • Explore access: list standard prices, see the free-weekend schedule and prepare a link for an access length available in the shop.
  • Understand settings: read the current setting names, choices, numeric ranges and weapon identifiers used by the settings editor.
  • Manage your profiles: read owned profiles, create a profile, patch a settings section, select an active profile or import a published community configuration when your membership permits it.
  • Check access: read whether your account currently has cheat access and whether free-weekend editing restrictions apply.

Your permissions and membership still apply

Reading account status, reading cloud profiles, changing profiles and preparing purchases are separate permissions. Settings changes require current cheat access. Free users retain their one-profile limit, editing is locked outside their claimed weekend, and community imports require Premium. The assistant cannot access another member’s private profiles.

A cloud save changes the stored profile. Apply it to a running module using the normal client or Live apply flow. MCP does not operate the game, download or install software, or bypass account restrictions.

Purchases stay in your browser

The purchase tool prepares a link to Hexui’s existing shop. Open it while signed in to the intended account, review the current price and terms, and complete payment yourself. Regional eligibility and the final total are determined in that checkout. MCP does not charge a card, start renewal, accept terms or report an unpaid order as successful.

Example requests

  • “List my cloud profiles and explain the settings I can change.”
  • “Show the differences between my current profiles before changing anything.”
  • “Create a private cloud profile using the default settings.”
  • “Show my access status and prepare the checkout link for an available subscription length.”

Disconnect at any time

Open Account → AI connections to revoke an assistant. Its tokens stop working immediately. Changing your password or connected sign-in identity also invalidates existing AI authorization. Access tokens last one hour; refresh tokens rotate and remain subject to revocation and account checks.

Technical connection details

The server supports MCP protocol versions 2025-03-26, 2025-06-18 and 2025-11-25 over Streamable HTTP, using stateless JSON replies. It supports OAuth authorization-code grants, S256 PKCE, dynamic public-client registration, protected-resource metadata, rotating refresh tokens and token revocation. An HTTP GET to the MCP endpoint returns 405 because unsolicited SSE streams are not offered.

Tool schemas and service metadata · Public access catalog · Machine-readable site overview

Profile revisions prevent stale edits. Write operations require an operation key: repeat the same key and arguments when retrying. An interrupted operation is marked for inspection rather than being executed again automatically.