> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/devops/mcp-server/connecting-claude-to-the-devops-mcp-server.md).

# Connecting Claude to the DevOps MCP Server

{% hint style="warning" %}

#### Beta

The DevOps MCP server is in beta. Some tools may not work as expected yet, and this documentation may not reflect the latest changes to the server.
{% endhint %}

## ![](https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FG5ZbxX918xOHwbAwAJ4n%2FSummary2-Small-Icon.svg?alt=media\&token=da26a67f-ff7f-47b3-8669-06be960dc2d7) Overview

This article shows you how to connect Claude to the DevOps MCP (Model Context Protocol) server as a custom connector. Once connected, Claude can use the DevOps MCP tools to work with your DevOps data. You sign in with your own Flosum user during setup, so Claude connects to DevOps as that user, not as the user who created the Connected App.

{% hint style="info" %}

#### Before You Start

You need a Flosum user with at least **Read access** to **DevOps**.

A SystemAdministrator must create a Connected App for MCP access. See the following article.

* [Creating a Connected App for MCP Access](https://docs.flosum.com/global-settings/security/connected-apps/creating-a-connected-app-for-mcp-access.md)

The Connected App also needs Claude's callback URLs. If they have not been added yet, a SystemAdministrator adds them in the **Add the Callback URLs** step below.
{% endhint %}

## Connect Claude to DevOps

{% stepper %}
{% step %}

## Log In to Global Settings

Log in to Global Settings. For login instructions, see the following article.

* [Log In To Global Settings](https://docs.flosum.com/global-settings/getting-started/log-in-to-global-settings.md)
  {% endstep %}

{% step %}

## Check the Callback URLs

1. Click **Connected Apps** from the left sidebar menu.
2. Click the Connected App created for MCP access.

   <div align="left"><figure><img src="https://content.gitbook.com/content/RpUu5iMlzMFAudyBvMOl/blobs/IdSlF0CtL2oyxzRyiKKM/Connecting_Claude_to_the_DevOps_MCP_Server-001.png" alt="" width="563"><figcaption></figcaption></figure></div>
3. Under **Authorized URLs**, check that **Callback URLs** lists both:
   1. `https://claude.ai/api/mcp/auth_callback`
   2. `https://claude.com/api/mcp/auth_callback`

      <div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FTHjbdrkCW5MNALmzPBhr%2FConnectingClaudeToTheDevOpsMCPServer-02.png?alt=media&amp;token=0f8afc75-4e5b-4f77-86ad-eed88e4910f9" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}

#### Callback URLs

If both URLs are listed, skip to the **Copy Client ID and Client Secret** step. If they are not listed, a SystemAdministrator must add them by completing the next step.
{% endhint %}
{% endstep %}

{% step %}

## Add the Callback URLs

1. Click **Edit**.

   <div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FzJTY5saMtrOq078XF6Co%2FConnectingClaudeToTheDevOpsMCPServer-03.png?alt=media&amp;token=e2a089c1-06b4-4e9f-971b-4c21a5a6ffea" alt="" width="563"><figcaption></figcaption></figure></div>
2. Click **ADD URL** under **Allowed callback URLs**.

   <div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2F9lMvOtNuARnZhBjwWc1x%2FConnectingClaudeToTheDevOpsMCPServer-04.png?alt=media&amp;token=59799965-6843-4d55-b14f-ad1cac299337" alt="" width="563"><figcaption></figcaption></figure></div>
3. Enter `https://claude.ai/api/mcp/auth_callback`.
4. Click **ADD URL**.
5. Enter `https://claude.com/api/mcp/auth_callback`.
6. Click **Save**.

   <div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FekHJhRUkW9w4tZr9D9gw%2FConnectingClaudeToTheDevOpsMCPServer-05.png?alt=media&amp;token=b973359f-f957-499d-96c6-04a17afb53a6" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
Claude currently uses the `claude.ai` callback URL. Anthropic recommends adding the `claude.com` URL too, so the connection keeps working if the callback URL changes.
{% endhint %}
{% endstep %}

{% step %}

## Copy Client ID and Client Secret

Any user can copy the **Client id** and **Client secret** from the Connected App.

1. Click the **Client id** field to copy this value.
2. Save the copied value.
3. Click the **Client secret** field to copy this value.
4. Save the copied value.

   <div align="left"><figure><img src="https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FhtAaCu4sBTnwHBMoT5LG%2FConnectingClaudeToTheDevOpsMCPServer-06.png?alt=media&amp;token=78bfe41d-c039-433b-873e-d2ca524ce4bc" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

## Add a Custom Connector in Claude

{% hint style="info" %}
The following steps take place in Claude, and some screens and settings may differ in your version of Claude. For more detailed instructions on adding a custom connector in Claude, see the following article.

* [Get started with custom connectors using remote MCP](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp)
  {% endhint %}

1. In Claude, open **Settings**.
2. Click **Connectors**.
3. Click **Add**.
4. Click **Add custom connector**.

   <div align="left"><figure><img src="https://content.gitbook.com/content/RpUu5iMlzMFAudyBvMOl/blobs/NNIXNBkQwdICOygymvFZ/Connecting_Claude_to_the_DevOps_MCP_Server-007.png" alt="" width="563"><figcaption></figcaption></figure></div>
5. Enter a name for the connector. This name is shown in your connectors list.
6. Enter the MCP server URL for your Flosum Cloud Apps tenant's region.

<table><thead><tr><th width="160.3333740234375">Region</th><th>DevOps MCP Server</th></tr></thead><tbody><tr><td>United States</td><td><code class="expression">space.vars.mcp_url_us</code></td></tr><tr><td>Germany</td><td><code class="expression">space.vars.mcp_url_de</code></td></tr><tr><td>Japan</td><td><code class="expression">space.vars.mcp_url_jp</code></td></tr><tr><td>Australia</td><td><code class="expression">space.vars.mcp_url_au</code></td></tr></tbody></table>

7. Click **Continue**.

   <div align="left"><figure><img src="https://content.gitbook.com/content/RpUu5iMlzMFAudyBvMOl/blobs/WHP3sRAKS9xCimEQQIoj/Connecting_Claude_to_the_DevOps_MCP_Server-008.png" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

## Set Up Authentication

{% hint style="info" %}
The **Add custom connector** form detects the **Authentication** and **OAuth client** settings automatically and labels them **Detected**.
{% endhint %}

1. Confirm **Authentication** is set to **Sign in now**.
2. Confirm **OAuth client** is set to **Use your own OAuth client**.
3. Enter the **Client id** you copied from the Connected App.
4. Enter the **Client secret** you copied from the Connected App.
5. Click **Add**.

   <div align="left"><figure><img src="https://content.gitbook.com/content/RpUu5iMlzMFAudyBvMOl/blobs/YI44qH9Ae8jVWcevB6Hp/Connecting_Claude_to_the_DevOps_MCP_Server-009.png" alt="" width="375"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

## Sign In to Flosum

{% hint style="warning" %}
If you are logged in to Flosum Cloud Apps in the same browser, Claude connects with that Flosum user and does not show the sign-in page. To connect with a different user, log out of Flosum Cloud Apps before you click **Connect**. If Claude already connected with the wrong user, click **Disconnect** on the connector, log out of Flosum Cloud Apps, and connect again.
{% endhint %}

1. Click **Connect**.

   <div align="left"><figure><img src="https://content.gitbook.com/content/RpUu5iMlzMFAudyBvMOl/blobs/IWTEUXN1x3ExQBrEQ8iu/Connecting_Claude_to_the_DevOps_MCP_Server-010.png" alt="" width="563"><figcaption></figcaption></figure></div>
2. Enter your Flosum **Email**.
3. Enter your **Tenant**.
4. Enter your **Password**.
5. Click **LOGIN**.

   <div align="left"><figure><img src="https://content.gitbook.com/content/RpUu5iMlzMFAudyBvMOl/blobs/FKcbg5tcc2SlKeWG9eRW/Connecting_Claude_to_the_DevOps_MCP_Server-011.png" alt="" width="375"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

## Review Tool Permissions

After you sign in, the connector page lists the DevOps MCP tools under **Tool permissions**. Choose when Claude is allowed to use each tool, following your organization's access policy. Use the dropdown menu to set every tool at once, or the icons beside each tool to set them one at a time.

<div align="left"><figure><img src="https://content.gitbook.com/content/RpUu5iMlzMFAudyBvMOl/blobs/zlDBUVzudthBQgYLJqbG/Connecting_Claude_to_the_DevOps_MCP_Server-012.png" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="success" %}
The DevOps MCP server is now connected. Start a new conversation in Claude to use the DevOps MCP tools.
{% endhint %}

{% hint style="info" %}
Your connection lasts as long as the Connected App's **Refresh token lifetime**, counted from when you sign in. Using Claude doesn't extend it. When it runs out, Claude asks you to sign in again.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# 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.flosum.com/devops/mcp-server/connecting-claude-to-the-devops-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.
