Skip to main content
Glama
AgentOps-AI

AgentOps MCP

Official
by AgentOps-AI
README.md
# AgentOps MCP Server

[![smithery badge](https://smithery.ai/badge/@AgentOps-AI/agentops-mcp)](https://smithery.ai/server/@AgentOps-AI/agentops-mcp)

The AgentOps MCP server provides access to observability and tracing data for debugging complex AI agent runs. This adds crucial context about where the AI agent succeeds or fails.

## Usage

### MCP Client Configuration

Add the following to your MCP configuration file:

```json
{
    "mcpServers": {
        "agentops-mcp": {
            "command": "npx",
            "args": ["agentops-mcp"],
            "env": {
              "AGENTOPS_API_KEY": ""
            }
        }
    }
}
```

## Installation

### Installing via Cursor Deeplink

[![Install MCP Server](https://cursor.com/deeplink/mcp-install-dark.svg)](https://cursor.com/install-mcp?name=agentops&config=eyJjb21tYW5kIjoibnB4IGFnZW50b3BzLW1jcCIsImVudiI6eyJBR0VOVE9QU19BUElfS0VZIjoiIn19)

### Installing via Smithery

To install agentops-mcp for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@AgentOps-AI/agentops-mcp):

```bash
npx -y @smithery/cli install @AgentOps-AI/agentops-mcp --client claude
```

### Local Development

To build the MCP server locally:

```bash
# Clone and setup
git clone https://github.com/AgentOps-AI/agentops-mcp.git
cd mcp
npm install

# Build the project
npm run build

# Run the server
npm pack
```

## Available Tools

### `auth`
Authorize using an AgentOps project API key and return JWT token.

**Parameters:**
- `api_key` (string): Your AgentOps project API key

### `get_trace`
Retrieve trace information by ID.

**Parameters:**
- `trace_id` (string): The trace ID to retrieve

### `get_span`
Get span information by ID.

**Parameters:**
- `span_id` (string): The span ID to retrieve

### `get_complete_trace`
Get comprehensive trace information including all spans and their metrics.

**Parameters:**
- `trace_id` (string): The trace ID

## Requirements

- Node.js >= 18.0.0
- AgentOps API key (passed as parameter to tools)

TDQS

B3.2/5.0

Scored across 4 tools

Disambiguation3/5

The tools have some overlap that could cause confusion, particularly between get_trace and get_complete_trace, which both retrieve trace data by trace_id, making their boundaries unclear. However, get_span is distinct in targeting span-level data, and auth is clearly separate for authentication purposes.

Naming Consistency4/5

The naming is mostly consistent with a verb_noun pattern (e.g., get_complete_trace, get_span, get_trace), but auth deviates as a standalone verb without a noun, which is a minor inconsistency. Overall, the naming is readable and follows a predictable style.

Tool Count4/5

With 4 tools, the count is slightly low but reasonable for a server focused on trace and span retrieval, as it covers core operations without being overly thin. It could benefit from additional tools like creating or updating traces to be more comprehensive, but it's not severely lacking.

Completeness2/5

The tool surface is significantly incomplete for an observability domain like AgentOps, as it only provides read operations (get) for traces and spans, with no create, update, delete, or search capabilities. This will likely cause agent failures when trying to perform full lifecycle management of monitoring data.

Maintenance

ActivityInactive
ResponsivenessNo issues