Helicone (LLM Observability)

Helicone (LLM Observability) MCP Connector for Claude

A+

Monitor LLM usage via Helicone — track requests, analyze costs, measure latency, and manage prompts.

10 tools Official Updated Jun 28, 2026 Official Vinkius Partner

Connect your Helicone account to any AI agent and take full control of your LLM observability and gateway monitoring through natural conversation.

What you can do

  • Request Monitoring — Query deep proxy logs to inspect exact prompts and outputs sent to LLM APIs directly from your agent
  • Cost Analysis — Break down spending by model, user, or custom metadata properties to monitor your AI burn rate in real-time
  • Latency Optimization — Measure Time To First Token (TTFT) and pinpoint slowness caused by specific upstream LLM providers
  • Prompt Management — Access managed prompt versions and track iterative changes in your AI instruction logic natively
  • Session Tracing — Isolate and analyze multi-turn graph traces connecting consecutive LLM calls to debug complex agentic workflows
  • User Insights — Track precise LLM interactions based on Helicone tags and identify your most active human clients
  • Feedback & RLHF — Extract user critiques (Thumbs Up/Down) and log offline Human-in-the-Loop verdicts to improve model grounding

How it works

  1. Subscribe to this server
  2. Enter your Helicone API Key
  3. Start monitoring your LLM infrastructure from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • LLM Engineers — debug prompt performance and measure TTFT latency across multiple upstream providers
  • Product Owners — monitor AI spending and calculate costs per user, feature, or organization
  • Data Scientists — analyze user feedback and improve model response quality through logged critiques
  • DevOps/SREs — ensure the availability and reliability of your AI gateway and proxy layers
llm-observabilityrequest-loggingcost-analysislatency-trackingprompt-managementai-gateway

10 tools expose this connector's capabilities to your AI agent.

query_costs

Perform structural extraction of properties driving active Account logic

query_feedback

Inspect deep internal arrays mitigating specific Plan Math

query_latency

Provision a highly-available JSON Payload generating hard Customer bindings

log_feedback

Identify precise active arrays spanning native Hold parsing

query_prompts

Retrieve explicit Cloud logging tracing explicit Vault limits

list_properties

Identify precise active arrays spanning native Gateway auth

query_requests

Identify bounded CRM records inside the Headless Helicone Platform

query_sessions

Enumerate explicitly attached structured rules exporting active Billing

query_users

Dispatch an automated validation check routing explicit Gateway history

get_prompt_versions

Irreversibly vaporize explicit validations extracting rich Churn flags

See how to talk to your AI agent using Helicone (LLM Observability).

How much did we spend on GPT-4o yesterday?

Yesterday, you spent a total of $42.15 on GPT-4o across 12,450 requests. The largest portion came from the 'Customer Support' feature tag ($28.40). Would you like a breakdown by user?

Show me the 10 slowest requests from the last hour

I've identified the 10 slowest requests. The highest TTFT was 4.2s for an 'anthropic.claude-3-opus' call. Average latency for these 10 is 3.1s. Would you like to inspect the prompt for the slowest one?

List all versions for the 'customer-service-bot' prompt

Found 5 versions for 'customer-service-bot'. Version 5 (latest) was deployed 2 days ago with updated grounding rules. Version 4 was active for 3 months. I can fetch the exact instruction text for any version.

Yes. Use the `query_requests` tool to fetch direct prompts and outputs from the proxy logs. You can filter by status or custom tags to find the exact interaction that needs debugging.

Related Connectors