> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/space/mcp-connections.md).

# MCP Connections

The **MCP Connections** page provides an overview of active OAuth connections to the current space. Use it to check who connected an MCP client, to change what a connection may do, and to revoke connections that should no longer have access. In the space menu it is listed as **MCP Connection**.

## Connection list

Each connection shows:

| Field           | Description                                                                                 |
| --------------- | ------------------------------------------------------------------------------------------- |
| Connection Name | The MCP client used to connect, such as ChatGPT/Codex.                                      |
| User            | The user who authorized the connection.                                                     |
| Status          | The current status of the connection.                                                       |
| Scope           | What the connection may use: Management **Full Access** or **Readonly**, and/or **Solver**. |
| Created At      | When the connection was established.                                                        |
| Last Used       | When the connection was last used.                                                          |

## Change the scope of a connection

You can change what an existing connection may do without reconnecting the MCP client.

1. Find the connection in the list.
2. Open the **three-dot menu** at the end of its row.
3. Select **Edit scope**.
4. Choose the Management access level (**No Management access**, **Full Access** or **Readonly**) and whether **Solver** access is enabled, then save.

The new scope applies immediately to every token of that connection. You can select only scopes that both you and the user who authorized the connection are currently allowed to grant. If a current scope is no longer permitted, you can remove it but not select it again.

## Revoke a connection

1. Find the connection in the list.
2. Open the **three-dot menu** at the end of its row.
3. Select **Delete connection** and confirm the action.

Deleting a connection immediately removes that client's access to the space.

## Required permissions

* **View MCP Connections** is required to open the list.
* **Connect MCP Server** is required to change the scope of a connection.
* **Delete MCP Connection** is required to revoke a connection.
* Both **View MCP Connections** and **Delete MCP Connection** are required to manage and revoke connections in the UI.

<figure><img src="https://437457296-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MN4F4-qybg8XDATvios%2Fuploads%2Fyx3Z16Qv9gBhDcgWwwuy%2FStep7MCP.png?alt=media&#x26;token=aba6fdba-ca9b-4389-bf75-2369c5b48a91" alt=""><figcaption></figcaption></figure>

## Create a connection

Connect an MCP-compatible client to the **Authoring MCP Server** to create, manage, test, and execute resources in the selected space. Follow the setup guide: [here](https://docs.decisionrules.io/doc/integrations/sdk-and-libraries/mcp-servers.md#authoring-mcp-server)


---

# 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.decisionrules.io/doc/space/mcp-connections.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.
