Skip to content
← About Glossa

Glossa · Connection

Civil Code commentaries — right inside your AI assistant

Step-by-step: how to connect the Glossa library to Claude, ChatGPT, Claude Code, Codex or Cursor. Claude and ChatGPT connect via OAuth; for other clients, create a personal key in the mizenko.ru cabinet after verifying your email.

Nothing to install: the server runs on mizenko.ru. All you need is a mizenko.ru account — shared with Russian Laws and Supreme Court Practice.

MCP connection

Everything you need to connect

Claude and ChatGPT connect via OAuth through mizenko.ru sign-in; Claude Code, Codex and other clients use a personal key from the cabinet (Authorization: Bearer mzk_…). The library and search run on the server: no source code, books, SQLite, Python or models need to be downloaded.

Connection details

Connection name
glossa
Server URL
https://mizenko.ru/glossa/mcp
Transport
Streamable HTTP
Authentication
Bearer token
HTTP header
Authorization: Bearer YOUR_GLOSSA_TOKEN
Token lifetime
selected in the cabinet

In a Token / API key field, enter only your key. For HTTP headers, use Authorization with the value Bearer, a space, and your key. YOUR_GLOSSA_TOKEN is a placeholder, not a working token. Email and password are only used to sign in on this website.

Get a key for Bearer connections

  1. Sign in to the mizenko.ru cabinet (or register) and create a key in the “Keys” tab.
  2. Copy the token and save it in your personal password manager: it is no longer displayed after you leave the page.
  3. Choose your client instructions below. If using an Add Server form, select a remote HTTP connection and enter the URL and Bearer token.

Your mizenko.ru account is shared across Glossa, Russian Laws and Supreme Court Practice. Keep configurations containing your personal key private and out of shared Git repositories.

Get a key in the mizenko.ru cabinet

Desktop apps and web chats

Get a key in the mizenko.ru cabinet

Choose the interface you actually use. A local app's MCP configuration and a web-chat account connection use different setup flows.

Client compatibility with Glossa authentication
AppCurrent connection
Codex · DesktopToken connection
Claude Code · Desktop Code tabLocal sessions
Claude · Web / Desktop Chat / CoworkOAuth · read and search
ChatGPT · WebOAuth · read and search
Gemini · WebGlossa connection not verified
Google AI Studio / Gemini APIDeveloper integration
Codex · Desktop

Token connection

  1. Open app settings → MCP servers. Manual setup uses Add server and Streamable HTTP. Use glossa as the name and the URL above.
  2. For token authentication, merge the block below into your personal ~/.codex/config.toml (в Windows %USERPROFILE%\.codex\config.toml). Replace YOUR_GLOSSA_TOKEN. Update an existing glossa block and keep other settings.
  3. Select Restart for the server or fully restart the app. In a new local task, enter /mcp and run the verification prompt below.
[mcp_servers.glossa]
url = "https://mizenko.ru/glossa/mcp"
http_headers = { Authorization = "Bearer YOUR_GLOSSA_TOKEN" }
startup_timeout_sec = 30
tool_timeout_sec = 120

Settings are shared with Codex CLI on the same computer. A local connection is not automatically transferred to cloud tasks. Newer releases may call the app ChatGPT Desktop with local Codex.

Claude Code · Desktop Code tab

Local sessions

  1. Open the Code tab in the Claude desktop app and select a local session with a folder on your computer.
  2. Open your personal ~/.claude.json (в Windows %USERPROFILE%\.claude.json). Merge glossa into the top-level mcpServers object using the template below and replace YOUR_GLOSSA_TOKEN. Keep other fields and servers. CLI setup may already have added this block.
  3. Restart the app and start a new local Code session. Ask it to show available Glossa tools and call glossa_list_books.
{
  "mcpServers": {
    "glossa": {
      "type": "http",
      "url": "https://mizenko.ru/glossa/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_GLOSSA_TOKEN"
      }
    }
  }
}

The CLI and local Code tab share ~/.claude.json. Use the next guide for regular Claude chat; SSH sessions need configuration on the selected machine.

Claude · Web / Desktop Chat / Cowork

OAuth · read and search

  1. Open Customize → Connectors → Add custom connector. Enter Glossa and the URL above. Work organizations may require an administrator to add it.
  2. Select Authentication → OAuth. Sign in through mizenko.ru and approve access to Glossa.
  3. Save the connector. In a new chat, use + → Connectors to enable Glossa and run the verification prompt below. The account connection is used by both web and desktop chat.

Claude and ChatGPT connect via OAuth through mizenko.ru sign-in; Claude Code, Codex and other clients use a personal key from the cabinet (Authorization: Bearer mzk_…).

ChatGPT · Web

OAuth · read and search

  1. First create a mizenko.ru account and keep your email and password. Use your existing account if you have one; OAuth does not require issuing a new personal Bearer key.
  2. In ChatGPT settings, open Plugins → Add custom MCP server (Apps → Create in some accounts). Enter Glossa, https://mizenko.ru/glossa/mcp, and Authentication → OAuth. Availability depends on your account and workspace policies.
  3. Glossa supports Dynamic Client Registration: leave OAuth client ID and client secret blank when automatic registration is allowed. Enter your email and password only on mizenko.ru, approve glossa — read and search — and return to ChatGPT.
  4. Enable Glossa in a new chat and ask it to call glossa_library_status and glossa_list_books. Look for tool results; a saved connection alone does not verify library access.

ChatGPT refreshes access in the background using a refresh token while the grant and account access remain valid. Restart an expired request. If client ID/secret are mandatory, do not use your personal key: ask your administrator about DCR availability. Verify the complete flow from your own account after connecting.

Gemini · Web

Glossa connection not verified

  1. In Gemini, open Settings → Connected Apps → Custom apps. Availability depends on region and account; Google's current help requires US access, English, a personal account aged 18+, and Keep Activity enabled.
  2. Google describes adding an MCP URL and Advanced features for servers without Dynamic Client Registration. Its help does not document direct Bearer token entry; Glossa compatibility with this flow is not verified.
  3. If your interface cannot send Authorization: Bearer, the current Glossa connection is not ready through that dialog. Use a supported client above; developers can use the Google API option below.
Google AI Studio / Gemini API

Developer integration

  1. Regular AI Studio chat and Gemini Web are different interfaces. A ready-made Glossa connection in ordinary AI Studio chat has not been verified. Playground → Agents is available for agent development.
  2. For a code integration, Google's Antigravity agent supports remote MCP with headers. Add the object below to the Interactions API tools array and replace YOUR_GLOSSA_TOKEN. This is an API request fragment, not a web-chat settings file.
  3. You need a separate Gemini API key, access to the chosen agent and your own API call. Request glossa_list_books and verify a real tool call. Google API usage may have separate charges; this Glossa flow has not been tested from your account.
{
  "type": "mcp_server",
  "name": "glossa",
  "url": "https://mizenko.ru/glossa/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_GLOSSA_TOKEN"
  },
  "allowed_tools": [
    "glossa_library_status",
    "glossa_list_books",
    "glossa_search",
    "glossa_read_passage"
  ]
}

Checked against official documentation on October 9, 2026. Menu labels and feature availability can differ in your account. Use your Glossa token in connection settings, not assistant messages.

Editors and terminal

Codex · CLI
  1. Open your personal ~/.codex/config.toml. If it does not exist, create it in ~/.codex.
  2. Append the block below and replace YOUR_GLOSSA_TOKEN with your key. Keep existing settings; update an existing glossa block instead of adding a duplicate.
  3. Fully restart Codex. In the CLI, run codex mcp list, then send the verification prompt below to your assistant.
[mcp_servers.glossa]
url = "https://mizenko.ru/glossa/mcp"
http_headers = { Authorization = "Bearer YOUR_GLOSSA_TOKEN" }
startup_timeout_sec = 30
tool_timeout_sec = 120
Cursor
  1. Open your personal ~/.cursor/mcp.json. If it does not exist, create it in ~/.cursor.
  2. Add glossa inside mcpServers and replace YOUR_GLOSSA_TOKEN with your key. For an empty file, use the whole example.
  3. Save and restart Cursor. In Agent mode, allow Glossa tools and send the verification prompt below.
{
  "mcpServers": {
    "glossa": {
      "url": "https://mizenko.ru/glossa/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_GLOSSA_TOKEN"
      }
    }
  }
}
VS Code · Copilot
  1. Open the Command Palette: Cmd+Shift+P on macOS or Ctrl+Shift+P on Windows/Linux. Run MCP: Open User Configuration.
  2. Add glossa to servers and glossa-token to inputs. For an empty file, use the whole example. Keep existing servers and inputs.
  3. Run MCP: List Servers, select glossa and start it. When prompted for Glossa personal token, enter only the key, without Bearer. Then use Copilot chat in Agent mode.
{
  "servers": {
    "glossa": {
      "type": "http",
      "url": "https://mizenko.ru/glossa/mcp",
      "headers": {
        "Authorization": "Bearer ${input:glossa-token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "glossa-token",
      "description": "Glossa personal token",
      "password": true
    }
  ]
}

This configuration is for local VS Code chat with input support. Agent Host sessions do not receive servers requiring interactive token input.

Claude Code · CLI
  1. With Claude Code installed, run the command below in your terminal after replacing YOUR_GLOSSA_TOKEN with your key.
  2. The --scope user option makes the connection available to you across projects. If glossa is already configured, update the existing configuration.
  3. Open Claude Code and run /mcp to check Glossa status. Then send the verification prompt below.
claude mcp add --transport http --scope user glossa https://mizenko.ru/glossa/mcp \
  --header "Authorization: Bearer YOUR_GLOSSA_TOKEN"

The command contains your personal key and may be saved in terminal history. Do not share it.

The templates contain connection settings only, with no active keys. Merge the relevant block into your configuration and keep existing servers.

How to check the connection

Enable Glossa tools in your client and send this prompt to your assistant:

Call glossa_library_status and glossa_list_books.
Show the library status and the available books.

Then ask: “Search Glossa for commentary on Article 10 of the Russian Civil Code, read the matching passages and cite the book and source reference.” The chat should show tool calls and results from the library.

Opening the URL in a browser does not verify MCP: your client establishes the connection. A successful tool call is the actual check.

If the connection fails

401 · Unauthorized
Check the key, the space after Bearer and the full URL. Expired or replaced tokens no longer work; sign in here for a new one and update your settings.
429 · Too Many Requests
The limit is 60 HTTP requests per minute and two at once, including MCP protocol requests. Wait for the Retry-After interval before trying again.
OAuth in ChatGPT
Select OAuth and follow the ChatGPT guide above. Sign in with your existing email and password on mizenko.ru. Restart expired requests from ChatGPT; a personal Bearer key does not belong in client ID/secret fields.
The assistant replies without sources
Check that the server and its tools are enabled. Ask explicitly to use Glossa and look for a tool call in the chat, rather than just a model response.