Nobl9 MCP server

Reading time: 0 minute(s) (0 words)

Enabling AI agents to manage SLOs can significantly enhance a business's operational efficiency by automating monitoring and configuration tasks. The Nobl9 MCP server connects AI clients directly to the Nobl9 platform, enabling AI agents to interact with your SLOs, monitor reliability metrics, and manage SLO configurations through natural language.

Prerequisites

Before you begin, make sure you have the following:

A Nobl9 account.
An AI client with or without OAuth 2.0 Authorization Code flow support.

How you connect depends on your AI client’s support for OAuth 2.0 Authorization Code flow.

Remote server:
- If your client supports OAuth 2.0, you can configure the Nobl9 remote MCP server directly within the client interface.
sloctl proxy:
- If your client does not support OAuth, you must install and configure sloctl (version 0.21.0 or later).
- sloctl processes requests from your AI client through standard input/output and forwarding them to the Nobl9 API.

Accessing Nobl9 MCP server

The Nobl9 MCP server can be accessed using either a remote endpoint or a local server with sloctl. The remote option allows for seamless integration and management with the provided hosted MCP server. The local option relies on standard sloctl authentication with device credentials (client ID and client secret pair).

Remote access

Nobl9 provides a hosted MCP server that allows you to connect your AI client directly with authorization code generated with your Nobl9 credentials.

Instance	Endpoint	Client ID
EU (app)	`https://app.nobl9.com/api/mcp`	`0oatwilexuu9M053R417`
US (us1)	`https://us1.nobl9.com/api/mcp`	`0oasuxjkqx2piyEQH5d7`

Local access

sloctl version requirement

The MCP server proxy is supported in sloctl versions 0.21.0 or later.

Run the Nobl9 MCP server locally for automation and programmatic access. For this:

Install sloctl (or run go install github.com/nobl9/sloctl@latest).
Run the MCP server with sloctl mcp.

For assistance, run sloctl mcp --help.

Authenticate with sloctl

Because sloctl acts as a proxy, it handles all authentication directly. You do not need to authenticate within your AI client.

To authenticate sloctl, use your user or API access key generated in the Settings section of the Nobl9 web application.

AI client setup

This section provides guidance on setting up AI clients to access the Nobl9 MCP server.

Other AI clients can be configured to work with Nobl9 MCP server provided that they implement either SSE with OAuth authorization or stdio transport.

ChatGPT configuration depends on your license.

Individual license

Prerequisites:

The Developer mode
MCP server address
Client ID

To set up Nobl9 MCP server access in Chat GPT:

Go to Settings in your ChatGPT app.
Open Apps and click Create app.
Fill in the form, providing your Nobl9 MCP server details.

Organization license

Prerequisite:

The Nobl9 MCP server app is configured and published by your organization's admin.

To use ChatGPT as the Nobl9 MCP server client:

Go to your profile > Settings.
Open Apps. Click Explore apps.
Find Nobl9 MCP Server and open it.
Click Connect.
This connects the Nobl9 MCP server for your account within the organization.
Click Start chat to begin asking questions.

To set up Nobl9 MCP server access in VS Code and Copilot:

Create .vscode/mcp.json in your workspace.
In the VS Code editor, click Add Server.
Enter the MCP server URL and server name:

Example Copilot configuration
{
    "servers": {
        "nobl9-server": {
            "url": "https://app.nobl9.com/api/mcp",
            "type": "http"
        }
    }
}

Start the server.
Once the server starts for the first time, VS Code opens the input field where you can enter your client credentials for authentication.
Enter the client ID according to the endpoint you're connecting to. Skip the client secret.
Confirm with Enter.
This opens the browser with either the Nobl9 login form or the confirmation screen displayed after successful authentication.
Once authenticated, add the Nobl9 MCP server as the chat context.
Click Add context in the request field of your VS Code AI chat:

Select Tools in the file list.
Search for Nobl9. Click Nobl9: All Tools to choose it as the request context.

Nobl9 MCP server — Choosing the Nobl9 tools for context

Limitations:
The Google Gemini browser app doesn't support MCP server configuration. To pair Nobl9 MCP server with Gemini use Gemini CLI.
Refresh tokens aren't supported. You will need to re-authenticate manually.
For correct setup, specify a client ID in settings, as the Nobl9 MCP server doesn't support DCR.

Prerequisites:

Installed Gemini CLI.

To setup Nobl9 MCP server access in Gemini CLI:

Add the Nobl9 MCP server to ~/.gemini/settings.json, specifying the Nobl9 MCP server address and client ID:

Example settings for Gemini CLI
{
    "mcpServers": {
        "nobl9-server": {
            "url": "https://app.nobl9.com/api/mcp",
                "oauth": {
                "enabled": true,
                "clientId": "0oatwilexuu9M053R417"
            }
        }
    }
}

Start Gemini at port 7777:

OAUTH_CALLBACK_PORT=7777 gemini

This triggers authentication first. Log in to your account.

Redirect URI port

Gemini CLI uses a random port instead of the specified redirectUri in its requests to the authorization server. A Gemini random port bug causes this.
The OAUTH_CALLBACK_PORT=7777 gemini environment variable suggested in Step 2 is the workaround for this bug.

Check if the Nobl9 MCP server is successfully connected:

/mcp

Success: The Nobl9 MCP server you added is displayed in the Configured MCP servers list and its capabilities.

Nobl9 MCP server and capabilities — The configured Nobl9 MCP server and its capabilities

To re-authenticate, run:

/mcp auth nobl9

Claude Code doesn't support pre-provisioned client ID. It relies strictly on DCR, which makes a remote server connection unavailable.
To address this, Nobl9 ships an MCP server proxy in sloctl that forwards requests to the remote Nobl9 HTTP MCP server.

Prerequisites:

Installed and configured sloctl.
You may need to create an API or user access key to configure the context for sloctl.
Installed Claude Code.

To setup Nobl9 MCP server access in Claude Code:

Add the Nobl9 MCP server:

claude mcp add --transport stdio nobl9 -- sloctl mcp

Check if the Nobl9 MCP server is successfully connected

/mcp

Success: The Nobl9 MCP server you added is displayed in the Local MCPs list with its location and project.

Start Claude:

claude

Codex doesn't support pre-provisioned client ID. It relies strictly on DCR, which makes a remote server connection unavailable.
To address this, Nobl9 ships an MCP server proxy in sloctl that forwards requests to the remote Nobl9 HTTP MCP server.

Prerequisites:

Installed and configured sloctl.
You may need to create an API or user access key to configure the context for sloctl.
Installed Codex CLI.

To setup Nobl9 MCP server access in Codex:

Add the Nobl9 MCP server:

codex mcp add nobl9 -- sloctl mcp

Click to open server configuration for manual setup

Update your Codex config (config.toml) as follows:

Nobl9 MCP server settings for Codex
[mcp_servers.nobl9]
command= "sloctl"
args = ["mcp"]

Check if the Nobl9 MCP server is successfully connected:

/mcp

Success: The Nobl9 MCP server you added is displayed in the MCP Tools list with the enabled status:

Start Codex:

codex

Because OpenCode fails to pass OAuth scope values correctly, remote connection is currently unavailable. To resolve this, connect the client locally using the sloctl proxy.

Prerequisites:

Installed and configured sloctl.
You may need to create an API or user access key to configure the context for sloctl.
Installed OpenCode CLI.

To configure OpenCode as the AI client for the Nobl9 MCP server, do the following:

Add Nobl9 MCP server settings to opencode.json:

opencode.json with the Nobl9 MCP server settings
{
    "mcp": {
        "nobl9" : {
            "type": "local",
            "command": ["sloctl", "mcp"],
        }
    }
}

Run OpenCode:

opencode

Check if the Nobl9 MCP server is successfully connected:

/mcp

Success: The Nobl9 MCP server you added is displayed in the MCPs list. Its status is Enabled.

Practical use examples

Example	Description
SLO discovery & search	Find and explore SLOs across projects using natural language queries. Filter by service, labels, or text search to understand your reliability landscape.
Real-time reliability monitoring	Check error budget state, burn rate, and SLO compliance in real time. Identify services at risk of breaching their objectives.
Configuration management	Retrieve and analyze SLO definitions, review objectives and thresholds, export configurations in JSON or YAML.
Alert and incident response	Access alert policies, review active silences, and understand alerting configurations tied to your SLOs for faster incident resolution.

Read more about Nobl9 MCP server capabilities.

OAuth authentication

cli The Nobl9 MCP server requires authentication using the browser-based OAuth 2.0 Authorization Code Flow.

Client registration

Nobl9 MCP authorization uses the pre-registered client approach. Dynamic Client Registration (DCR) is not supported.

Most AI clients that attempt DCR first are designed to handle its absence. If provided a static configuration, they do not strictly require DCR to authenticate.

Currently, the following available AI clients strictly require the OAuth 2.0 Client Credentials flow with mandatory DCR:

This renders it impossible to configure the remote Nobl9 MCP server. You can still configure these clients by using a local MCP server with sloctl.

Authorization server metadata

Nobl9 provides authorization server metadata discovery in compliance with:

Session management

The Nobl9 authorization server can return refresh tokens to maintain authenticated sessions for extended periods without requiring repeated browser authentication. MCP clients that support refresh tokens will automatically handle token refresh as needed, while other clients may still require you to re-authenticate periodically.

Capabilities

The Nobl9 MCP server supports various operations designed for read-only interaction with your Nobl9 resources

SLO management
- Get the following details about one SLO or SLOs in bulk (up to 50 SLOs per page):
  - Current health metrics, error budget remaining, and reliability for SLOs
  - Complete SLO configuration, including all objectives
- Search SLOs by the following parameters:
  - Keyword, label, and SLO type
  - Responsible users
  - Location—project, service
  - SLO health—error budget remaining, lower and upper reliability bounds
  - Review—status and dates
Resource and object handling
- Retrieve the following definitions:
  - Projects, services, data sources
  - Alerts, alert methods, policies, and silences
  - Budget adjustment definitions, data exports, and reports
User and access control
- Get the details of the following:
  - Nobl9 organizations the authenticated user belongs to, indicating the default
  - Definitions of user groups
  - Role bindings