Respan MCP Server

Model Context Protocol (MCP) server for Respan - access logs, prompts, traces, and customer data directly from your AI assistant.

Features

• Logs and traces - Query requests and inspect complete execution trees
• Behaviors and errors - Analyze quality signals, errors, and incidents
• Monitors - Manage alerts, versions, deployment, and delivery history
• Prompts - Manage prompt templates and versions
• Datasets, experiments and evaluators - Build datasets from logs, run experiments, test graders
• Project settings - API keys, caches, exports, webhooks, tags, saved views and limits
• Tool search - Everyday tools are listed; tool_search and tool_run reach the rest

---

Quick Start

Option 1: Public HTTP (Recommended)

No installation required.

1. Get your API key from platform.respan.ai

2. Add to your MCP config file:

Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "respan": {
      "url": "https://mcp.respan.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_RESPAN_API_KEY"
      }
    }
  }
}

Claude Desktop (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "respan": {
      "url": "https://mcp.respan.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_RESPAN_API_KEY"
      }
    }
  }
}

3. Restart Cursor/Claude Desktop

Read-only by default. When you connect with OAuth (sign in through the browser instead of pasting a key), the client only gets tools that read your data. To let it create, update, deploy or delete, tick Also allow changes on the consent page. Calls to change tools from a read-only connection return an insufficient_scope error that explains how to reconnect. With an API key, the key’s own permissions apply; create a key with read-only permissions for the same effect. OAuth connections made before this change keep their access until they expire.

A URL that can never write. https://mcp.respan.ai/mcp/readonly (and /mcp/enterprise/readonly) serves only read-only tools for every credential, OAuth or API key. A sign-in started from it grants read access only, and the consent page offers no “allow changes” option (this relies on the client sending the URL as its OAuth resource, or the mcp:read scope it advertises, as MCP clients do). Even a token that can write lists only read-only tools here. Use it when a connector must stay read-only whatever the user picks.

---

Option 2: Local Stdio

Run the MCP server locally for personal development or offline use.

Prerequisites: Node.js v18+

git clone https://github.com/respanai/respan-mcp.git
cd respan-mcp
npm install
npm run build

{
  "mcpServers": {
    "respan": {
      "command": "node",
      "args": ["/absolute/path/to/respan-mcp/dist/lib/index.js"],
      "env": {