Skip to main content
The Helicone MCP (Model Context Protocol) server enables AI assistants like Claude Desktop, Cursor, and other MCP-compatible tools to query your Helicone observability data directly. This allows you to debug errors, search logs, analyze performance, and examine request/response bodies without leaving your AI assistant.

Quick Start

1

Generate a Helicone API Key

  1. Go to Settings → API Keys (or EU)
  2. Click Generate New Key
  3. Copy your API key
2

Add to Your MCP Client

Add the Helicone MCP server to your client’s configuration file:
Config file location:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
Replace sk-helicone-xxxxxxx-xxxxxxx-xxxxxxx-xxxxxxx with your actual API key.
3

Restart Your Client

Restart your MCP client (Claude Desktop, Cursor, etc.) to load the new configuration.

Available Tools

query_requests

Query requests with filters, pagination, sorting, and optional body content. Parameters: Example use cases:
  • “Show me the last 10 failed requests”
  • “Find all requests to GPT-4 in the last hour”
  • “Search for requests with high latency”
  • “Show me requests from a specific user”

query_sessions

Query sessions with search, time range filtering, and advanced filters. Parameters: Example use cases:
  • “Show me all sessions from today”
  • “Find sessions named ‘checkout-flow’”
  • “Debug conversation flows in a specific time range”
  • “Analyze session performance metrics”

Filter Capabilities

Both tools support comprehensive filtering options:
  • Model/Provider: Filter by specific models or providers
  • Status/Error: Find successful or failed requests
  • Time: Filter by time ranges
  • Cost/Latency: Filter by performance metrics
  • Custom Properties: Filter by your custom Helicone properties
  • Complex Filters: Combine filters with AND/OR logic