Nobl9 MCP server

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

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.
MCP stands for Model Context Protocol, it is an open-source standard for connecting AI applications to external systems.

---

note

Before you proceed, make sure you choose the right Nobl9 instance.
If you're not sure, this is the host in the browser URL when you log into Nobl9 web application.
Bear in mind, client ID in this article refers to the pre-registered OAuth client. It is NOT related to your user's access keys.

Choose your Nobl9 instance app.nobl9.comus1.nobl9.com

Setup

Claude Code

1. Add the Nobl9 MCP server:

   claude mcp add --transport=http --client-id=0oatwilexuu9M053R417 --callback-port=6274 nobl9 https://app.nobl9.com/api/mcp

2. Start claude.

3. Run /mcp command and navigate to Nobl9 MCP server, then select it.

4. Choose Authenticate.

ChatGPT

warning

ChatGPT app creation is currently NOT supported.
If you're interested in this integration, reach out to us.

Codex

info

Direct connection to remote Nobl9 MCP server is not supported.
You need a configured sloctl CLI.

Add the Nobl9 MCP server by running:

codex mcp add nobl9 -- sloctl mcp

Cursor

Click this: or copy this into your ~/.cursor/mcp.json:

{
  "mcpServers": {
    "nobl9": {
      "url": "https://app.nobl9.com/api/mcp",
      "auth": {
        "CLIENT_ID": "0oatwilexuu9M053R417",
        "scopes": [
          "openid"
        ]
      }
    }
  }
}

OpenCode

1. Add this to your opencode.json config file:

   {
     "mcp": {
       "nobl9": {
         "type": "remote",
         "url": "https://app.nobl9.com/api/mcp",
         "oauth": {
           "clientId": "0oatwilexuu9M053R417",
           "callbackPort": 6274,
           "scope": "openid"
         }
       }
     }
   }

2. Authenticate:

   opencode mcp auth nobl9

VS Code Copilot

1. Add this to either your workspace .vscode/mcp.json or your user configuration:

   mcp.json

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

2. Start the server.

3. Enter 0oatwilexuu9M053R417 as the client ID for your Nobl9 instance.

4. Skip the client secret.

5. Confirm and complete the browser login.

Other

If you're using any other application, the easiest connection method is through sloctl mcp command. You need a configured sloctl CLI.

If you don't want to install sloctl, you can alternatively use mcp-proxy or other HTTP-to-stdio bridge. Note that sloctl mcp does exactly that, it bridges between stdio and our remote HTTP server. We strongly recommend it over any third party software due to security and trust concerns.

However, sloctl mcp does not work for applications running in environments with no access to the terminal, for instance, web-based ChatGPT. For these applications, you need to connect to Nobl9 remote HTTP server and authenticate through OAuth.

---

Capabilities

Tools

Tool	What it does
applyObjects	Applies complete Nobl9 object definitions.
calculateAlertPolicy	Calculates Alert Policy Analyzer suggestions for an SLO objective over a time range.
deleteObjectByName	Deletes Nobl9 object by name.
getAlertAnalysis	Retrieves the status, detected alerts, and optional time series for an Alert Policy Analyzer run.
getSLOStatus	Retrieves current budget status and health metrics for one SLO.
getSLOsStatuses	Retrieves current budget status and health metrics for multiple SLOs.
get<object>	Retrieves the full Nobl9 object definition.
list<object>	Lists Nobl9 object metadata, with filters.
prometheusLabelNames	Lists supported Prometheus label names for SLO metric discovery.
prometheusLabelValues	Lists values for a Prometheus label.
prometheusMetadata	Discovers Nobl9 Prometheus metrics relevant to SLOs.
prometheusQuery	Runs an instant Prometheus query over SLO metrics.
prometheusQueryRange	Runs a Prometheus range query over SLO metrics.
retryAlertAnalysis	Retries a failed Alert Policy Analyzer run.
searchSLOs	Searches for SLOs using text queries and advanced filters across projects and services.
startAlertAnalysis	Starts an Alert Policy Analyzer run for one SLO objective and alert policy over a time range.
validateObjects	Validates complete Nobl9 object definitions.

Prompts

Prompt	What it does
calculate-alert-policy	Guides the LLM through alert policy recommendations by calculating suggestions and running Alert Policy Analyzer for a single SLO objective.

Authentication details

Remote server

Remote MCP server uses browser-based OAuth 2.1. The important constraints and implementation details are:

• Nobl9 uses a static OAuth client and does not support DCR.

  • The client expects at least one scope, you can provide openid, permission-wise it doesn't do anything, it's there for compatibility.
  • The client is public, you only need to provide its ID: 0oatwilexuu9M053R417

• The following two endpoints for OAuth metadata discovery are exposed:

  • https://app.nobl9.com/.well-known/oauth-protected-resource
  • https://app.nobl9.com/.well-known/oauth-protected-resource/api/mcp

  Both expose the same information and are duplicated for compatibility. Either GET or OPTIONS HTTP method can be used.

sloctl

sloctl acts as a bridge between the remote HTTP MCP server and local stdio. It can authenticate using either user access keys or API keys, which it uses to fetch the access token.

You need sloctl version 0.21.0 or later. To create the required machine keys use either user access keys or API keys. Both can be generated in the Nobl9 web application. For setup details, see Configure sloctl.

Useful links

Check out these related guides and references:

Configure sloctlSLOs-as-Code in Nobl9sloctl on GitHubsloctlModel Context Protocol authorizationMCP specificationPre-registered clientMCP specification