> For the complete documentation index, see [llms.txt](https://docs.glbnxt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glbnxt.com/platform/mcp-servers/dictum/connect.md).

# Connect

DICTUM is one MCP server at `https://dictum.glbnxt.tech/mcp`. Any assistant or chat application that supports remote MCP servers can use it. Every connection uses the **GLBNXT login** (OAuth 2.1): there are no shared passwords or API keys to hand around.

### How a connection works

1. **Your application gets DICTUM's address.** An admin (or, in some applications, each user) adds `https://dictum.glbnxt.tech/mcp` as an MCP server, together with the client ID that GLBNXT provides.
2. **A user signs in once.** The first time DICTUM is used, the application opens the GLBNXT login. The user signs in with their own GLBNXT account.
3. **DICTUM's tools are available.** From then on the application calls DICTUM on that user's behalf, in every chat. The session renews itself; a user signs in again only when it has been revoked or has expired.

Every call is made as the signed-in user, so usage is recorded per person and access can be withdrawn per person or per application.

### What you need from GLBNXT

Ask GLBNXT support for access to DICTUM and say which application you use. GLBNXT provides:

* a **client ID**, always;
* a **client secret**, for applications that run on a server (Open WebUI, LibreChat);
* for your own Open WebUI or LibreChat instance: the registration of your instance's callback URL, so include that URL in your request.

Which people in your organisation may sign in is managed by GLBNXT in your organisation's GLBNXT account. Step-by-step instructions for each application are in the **DICTUM client dashboard**.

### Supported chat applications

| Application                                            | How it connects                                           | Set up by                                              | From GLBNXT                                           |
| ------------------------------------------------------ | --------------------------------------------------------- | ------------------------------------------------------ | ----------------------------------------------------- |
| GLBNXT Workspace (Open WebUI, LibreChat run by GLBNXT) | Already connected                                         | GLBNXT                                                 | nothing; users switch DICTUM on in a chat and sign in |
| Claude.ai and Claude Desktop                           | Custom connector, "Use your own OAuth client"             | organisation owner, or each user on an individual plan | client ID                                             |
| Open WebUI (your own instance)                         | MCP connection, OAuth 2.1 (Static)                        | instance admin                                         | client ID, client secret                              |
| LibreChat (your own instance)                          | MCP server in `librechat.yaml` with an `oauth` block      | instance admin                                         | client ID, client secret                              |
| Claude Code                                            | `claude mcp add` with `--client-id` and `--callback-port` | each user                                              | client ID, callback port                              |

### Other MCP clients

Any other client works if it supports remote MCP servers over Streamable HTTP with OAuth 2.1 and a pre-registered client (the GLBNXT login does not offer automatic client registration). The settings it needs:

| Setting                        | Value                                   |
| ------------------------------ | --------------------------------------- |
| Server URL                     | `https://dictum.glbnxt.tech/mcp`        |
| Transport                      | Streamable HTTP                         |
| Authentication                 | OAuth 2.1, authorization code with PKCE |
| Authorization server           | `https://login.platform.glbnxt.com`     |
| Client ID (and secret, if any) | from GLBNXT                             |
| Scopes                         | `openid profile email offline_access`   |

Most clients find the authorization server by themselves from DICTUM's first answer. When you request access, tell GLBNXT the redirect URL your client uses.

### Good to know

* **Switch DICTUM on per chat** in applications that offer it (Open WebUI): the first sign-in needs the user's browser, so do not make DICTUM a default tool of a model.
* **Prompts:** DICTUM offers four ready-made prompts next to its tools in applications that show MCP prompts: `legal_memo`, `case_overview`, `statute_on_date` and `legislative_history`.
* **Research method:** for answers with verbatim quotes, paragraph numbers and checked authority, add the [suggested skill](https://docs.glbnxt.com/platform/mcp-servers/dictum/tools/skill) to your assistant.
* **Access refused after signing in:** your GLBNXT account is not yet allowed to use DICTUM; ask GLBNXT support.
* **Two-step sign-in for DICTUM accounts:** signing in to the DICTUM client dashboard, or to an application with a DICTUM account, asks for a second step after the password: a code from an authenticator app (Microsoft Authenticator, Google Authenticator) or a security key. The first sign-in walks you through setting it up. People who sign in through their own organisation's sign-in (single sign-on) are not asked; their organisation's sign-in covers it. Lost your phone or key? Mail <support@glbnxt.com> and the second step is reset, so you can set it up again.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.glbnxt.com/platform/mcp-servers/dictum/connect.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
