MCP Server Quick Start¶

Owl MCP Server is the server-side implementation provided by TrueWatch based on the Model Context Protocol. It encapsulates TrueWatch's capabilities such as Metrics, LOG, events, monitors, dashboards, APM, RUM, and infrastructure as MCP tools for AI clients that support MCP to call.

This document explains how to connect to Owl MCP Server via streamableHttp.

Prerequisites¶

Before connecting, please ensure the following preparations are complete:

A TrueWatch API Key with corresponding business permissions has been created.
The Owl MCP Endpoint corresponding to the site where the workspace belongs has been obtained.
The Owl MCP service connection configuration has been completed in the MCP client.
The current network environment can access the Owl MCP Endpoint.

Endpoint¶

Owl MCP Server provides independent Endpoints by site. Please select the corresponding address based on the site where your workspace belongs.

Deployment Type	Site Name	Endpoint
SaaS Deployment	Global Region 1 (Oregon)	`https://us1-owl-mcp.truewatch.com/mcp`
SaaS Deployment	Europe Region 1 (Frankfurt)	`https://eu1-owl-mcp.truewatch.com/mcp`
SaaS Deployment	Asia Pacific Region 1 (Singapore)	`https://ap1-owl-mcp.truewatch.com/mcp`
SaaS Deployment	Africa Region 1 (South Africa)	`https://za1-owl-mcp.truewatch.com/mcp`
SaaS Deployment	Indonesia Region 1 (Jakarta)	`https://id1-owl-mcp.truewatch.com/mcp`
SaaS Deployment	Middle East Region 1 (UAE)	`https://me1-owl-mcp.truewatch.com/mcp`

Authentication Method¶

Configure the request header in the MCP client:

Authorization: Bearer <API Key>

Here, <API Key> is the TrueWatch API Key. Please keep it secure and do not write it into public code repositories, shared documents, or long-term logs.

Client Configuration¶

Owl MCP Server uses the standard streamableHttp connection method and can be connected to MCP clients that support this transport method. The configuration entry and field names may vary slightly across different clients. Please refer to the actual client documentation.

The following examples use Cherry Studio, OpenClaw, and Hermes to illustrate the configuration methods for common MCP clients. Other MCP clients supporting streamableHttp can be configured following the same principles:

URL: Fill in the Owl MCP Endpoint corresponding to the site where your workspace belongs.
Request Header: Configure Authorization: Bearer <API Key>.
Enable this MCP service.

The following examples use the placeholder address your-owl-mcp-endpoint. When actually connecting, please replace it with the Owl MCP Endpoint corresponding to the site where your workspace belongs.

Cherry Studio¶

Add a new MCP service in Cherry Studio and configure it as follows:

Type: streamableHttp
URL: your-owl-mcp-endpoint
Request Headers: Authorization=Bearer <API Key>

After completing the configuration, save and enable it, then return to the client homepage and select this MCP service.

OpenClaw¶

openclaw mcp set owl '{
  "type": "streamableHttp",
  "url": "your-owl-mcp-endpoint",
  "headers": {
    "Authorization": "Bearer <API Key>"
  },
  "enabled": true
}'

Verify the configuration:

openclaw mcp list
openclaw mcp show owl

Hermes¶

Edit ~/.hermes/config.yaml:

mcp_servers:
  owl:
    type: streamableHttp
    url: your-owl-mcp-endpoint
    headers:
      Authorization: Bearer <API Key>
    enabled: true

Verify the configuration:

hermes mcp list
hermes mcp test owl

Usage Conventions¶

When using Owl MCP Server, it is recommended to follow these conventions:

Type	Convention
Time Range Tools	Use 13-digit millisecond timestamps uniformly.
Pagination Tools	Typically support `page_size` and `page_index`.
Detail Tools	Usually rely on identifier fields returned by list tools, such as `dashboard_uuid`, `rule_uuid`, `incident_uuid`, `issue_id`.
Data Query Tools	It is recommended to use in the order of "discover first, then query". First, obtain available `source`, `field`, `index` through discovery tools, then perform the formal query.

Verification Method¶

After configuration is complete, you can ask in the MCP client:

List the currently available metric sources.

The client should be able to discover and call owl.metric.list. If connection fails, authentication fails, the tool list is empty, or results are empty, please refer to Troubleshooting.