Claude MCP Server for Observability Demo

by agardnerIT

3 408 downloads Not rated yet Apache-2.0
GitHub

About

# Claude MCP Server for Observability Demo Companion repo to this video: [Claude MCP Server for Observability](https://youtu.be/lWO9M9SpGAg) [![Claude MCP Server for Observability](https://img.youtube.com/vi/lWO9M9SpGAg/0.jpg)](https://www.youtube.com/watch?v=lWO9M9SpGAg) ## Prerequisites You'll need Claude Desktop…

Details

License
Apache-2.0

Explore

- Three tools for reading and analyzing logs
- Works with Claude Desktop (free account ok)
- Identifies error sources and their timing
- Suggests remediation actions (e.g., contact person)
- Integrates via the MCP protocol

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Claude MCP Server for Observability Demo
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

You'll need Claude Desktop for this (a free account is OK)

Open Claude Desktop. Go to Claude > Settings > Developer and click Edit config.

This will open a folder and highlight a particular JSON file. Open that file and set the content to what's below.

This step makes Claude Desktop aware of your MCP server.

{
  "mcpServers": {
    "logreader": {
            "command": "uv",
            "args": [
                "--directory",
                "/full/path/claude-mcp-server-observability",
                "run",
                "logreader.py"
            ]
    }
  }
}

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "claude mcp server for observability demo": {
            "logreader": {
                "command": "uv",
                "args": [
                    "--directory",
                    "/full/path/claude-mcp-server-observability",
                    "run",
                    "logreader.py"
                ]
            }
        }
    }
}

McpServers

{
    "logreader": {
        "command": "uv",
        "args": [
            "--directory",
            "/full/path/claude-mcp-server-observability",
            "run",
            "logreader.py"
        ]
    }
}

Companion repo to this video: Claude MCP Server for Observability

Claude MCP Server for Observability

Prerequisites

You'll need Claude Desktop for this (a free account is OK)

Step 1: Start MCP Server

- Clone this repo
- Install dependencies pip install -r requirements.txt
- Start the server with python logreader.py

Step 2: Install MCP Servers in Claude Desktop

Open Claude Desktop. Go to Claude > Settings > Developer and click Edit config.

This will open a folder and highlight a particular JSON file. Open that file and set the content to what's below.

This step makes Claude Desktop aware of your MCP server.

{
  "mcpServers": {
    "logreader": {
            "command": "uv",
            "args": [
                "--directory",
                "/full/path/claude-mcp-server-observability",
                "run",
                "logreader.py"
            ]
    }
  }
}

Step 3: Launch Claude

You should see the little "connector" icon. Click that and it should show one installed server called logreader.

Step 4: Ask Claude for Help!

Start a new chat and ask something like: I noticed errors in the logs on the 22nd March. Help me investigate

Claude should figure out that it should use your MCP server (and the three tools it offers) to help answer your query. Claude may request permission to run the tools. Accept the permissions.

Sooner or later (may need additional hints / prompts) you should get the answer and suggested remediation:

- Pipeline C and the release was most likely responsible for the errors
- You should contact Susan

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.