> 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/connecting-an-mcp-server.md).

# Connecting an MCP server

Every GLBNXT MCP server connects the same way: through the **GLBNXT login** (OAuth 2.1). Each user signs in once with their GLBNXT account; the server's tools are then available in every chat, and usage is recorded per user.

### What you need from GLBNXT

Ask GLBNXT support for access to the server and say which client you use. GLBNXT provides:

* a **client ID**, always;
* a **client secret**, for clients 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 it in your request.

GLBNXT Workspace instances that GLBNXT runs for you are already connected: users only switch the server on in a chat and sign in.

### Steps per application

Each server's Connect page lists the chat applications it works with and how each one connects; for DICTUM: [Connect](https://docs.glbnxt.com/platform/mcp-servers/dictum/connect). Step-by-step instructions per application are in the server's client dashboard.

The general tutorials [Connecting an MCP server to Open WebUI](https://docs.glbnxt.com/tutorials/guides/openwebui/mcp-openwebui) and [Connecting an MCP server to LibreChat](https://docs.glbnxt.com/tutorials/guides/librechat/mcp-librechat) explain the clients' MCP settings in more depth.


---

# 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/connecting-an-mcp-server.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.
