Skip to content

Analytics

Helicone MCP connector

The Helicone connector brings your Helicone requests, prompts, evals, and usage dashboards to Claude, ChatGPT, Cursor, and the Elaichi Agent, so anyone on the team can ask about what their AI application is doing and act on it from the tool they already use.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Helicone to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Helicone once

  1. Open Connections, choose Add connection, and pick Helicone.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Helicone API key. One person generates a token in Helicone and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

helicone
Helicone
Allium
Amplitude
Artie
Botify
DoiT
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Helicone to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Helicone to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Helicone to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Helicone to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Helicone through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Engineering

    Find the request behind a bad answer

    When a user reports a strange response, pull up the exact Helicone request by ID, see the inputs that went in, and tag it with a property so the whole team can find it again.

  • Product

    Score responses without leaving the chat

    Review a batch of recent Helicone requests, submit a score or a note of feedback on each one, and build up the signal your evals depend on.

  • Data

    See how eval scores are distributed

    Ask how a Helicone eval is scoring across the last week, spot the requests that fall at the bottom, and compare against the models in use.

  • Finance

    Check AI spend before the invoice lands

    Read the Helicone dashboard figures for requests and cost by model or by property, and summarize them for the monthly budget review.

  • Support

    Trace a customer's session end to end

    List the Helicone requests tied to a customer or session property, read what was asked and answered, and attach feedback so engineering knows what to fix.

  • Engineering

    Keep prompts tidy across versions

    Create a new Helicone prompt, look up an existing one, and remove old versions that nobody should be calling any more, all from a short ask.

Try asking

  • “Summarize Helicone requests with low feedback scores this week.”
  • “Which team created the most Helicone requests yesterday?”
  • “Show scores on Helicone requests tagged production.”

See all 46 Helicone tools below

AI tools

Helicone tools for your AI agents

46 tools are ready to call through Elaichi's MCP endpoint the moment you connect Helicone, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Helicone gets you

6 screens from the product, each doing one job for your Helicone account.

The agent

Ask about Helicone requests in plain language.

Starter prompts return answers from live Helicone requests, scores and properties.

  • requests
  • completions
  • scores
  • properties

Ask Elaichi to work across your apps.

Summarize Helicone requests with low feedback scores this week.

Which team created the most Helicone requests yesterday?

Show scores on Helicone requests tagged production.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Helicone here.

One org MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

46 Helicone tools arrive ready to call.

Requests, gateway completions, feedback, scores and dashboards, with no custom code written.

  • Helicone AI gateway create chat completion
  • Helicone AI gateway create response
  • List all Helicone AI gateway
  • Helicone AI gateway list multimodal
ElaichiTools
Tool Action Description
Helicone AI gateway create chat completion Create Create a chat completion via the Helicone AI Gateway, routing the request to the specified model with pass-through billing. Returns the OpenAI-compatible completion response from the routed provider; response shape is provider-specific. Required: model, messages. In BYOK mode the standard OpenAI Chat Completions schema is allowed.
Helicone AI gateway create response Create Create a response via the Helicone AI Gateway using the OpenAI Responses API format, routing to the specified model with pass-through billing. Returns the OpenAI-compatible response from the routed provider; response shape is provider-specific. Required: model, input. In BYOK mode the standard OpenAI Responses API schema is allowed.
List all Helicone AI gateway List List all AI models available through the Helicone AI Gateway. Returns: object, data, error. OpenAI-compatible /v1/models endpoint for discovering which models are available for routing.
Helicone AI gateway list multimodal List List all multimodal AI models supported by the Helicone AI Gateway. Returns: object, data, error. This is an OpenAI-compatible endpoint for discovering models that support multiple input or output modalities (e.g., text + images).
Get single Helicone request by ID Get Retrieve a single LLM request record by its unique ID, including the prompt, response, model, tokens used, latency, cost, and metadata.

Toolboxes

Every team gets its own Helicone toolbox.

Toolboxes scope Helicone requests and dashboards to the team that needs them.

  • ML engineering
  • Platform
  • Product analytics
  • Quality
ElaichiToolboxes
Name Source template Tools Created

ML engineering toolbox

Helicone · requests and completions

Helicone starter 18 Mar 4, 2026

Platform toolbox

Helicone · gateway usage and errors

9 Mar 2, 2026

Product analytics toolbox

Helicone · dashboards and properties

24 Feb 27, 2026

Quality toolbox

Helicone · feedback and scores

Helicone starter 6 Feb 19, 2026

Finance toolbox

Helicone · token spend by team

31 Jan 30, 2026

Support toolbox

Helicone · single request lookups

12 Jan 22, 2026

Shared connections

Teammates query Helicone without holding a key.

The connections table shows who connected each Helicone account and its shared teams.

  • ML engineering
  • Platform
  • Product analytics
  • Quality
ElaichiConnections
Connection Scope Status Access
HE

Helicone (ML engineering)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
HE

Helicone (Platform)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
HE

Helicone (Product analytics)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
HE

Helicone (Quality)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
HE

Helicone (Finance)

Connected by Clara Nowak

Personal • Active Not shared
HE

Helicone (Support)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Helicone call is on the record.

When, who, what happened, type and resource, appended for each Helicone request touched.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Helicone Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Helicone Requests Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Helicone Requests List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns Helicone requests into a digest.

Six steps fetch and group requests, draft a digest, await approval, then post back.

Helicone digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch requests

    Helicone

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Helicone

    Queued

Collections and dashboards

Helicone metrics compute themselves on a schedule.

Four metrics, 14 days of requests created and a team breakdown, no model involved.

Helicone health

Refreshed 4 minutes ago · every 15 minutes · from the requests collection

Live

Requests

1,284 ↓ 12%

Completions

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Requests created

Last 14 days

By team

Share of activity

ML engineering 34%

Platform 27%

Product analytics 21%

Quality 18%

FAQ

Frequently asked questions

How do I connect Helicone to Claude?

First, connect Helicone in Elaichi by pasting in a Helicone API key, which you can copy from your Helicone settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Helicone requests, prompts, and evals are available in your conversation.

Does Helicone work with ChatGPT and Cursor as well as Claude?

Yes. Once Helicone is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Helicone once and every client picks it up, with the same access rules and the same audit log.

What can an AI agent actually do with my Helicone data?

It can look up a specific Helicone request and show you the inputs and the response, list recent requests and filter them by a property such as a customer or session, and read the dashboard numbers for usage and cost. It can also submit feedback or a score on a request, create an eval and show how its scores are distributed, list the models and properties in use, and create or retire prompts. Because Helicone exposes a large set of actions, short concrete asks such as "show request abc123" work better than long paragraphs.

Does connecting Helicone give the AI everything in my organization?

No. Access follows the person who signed in, so the AI can only see the Helicone requests, prompts, and evals that the API key behind the connection can already see. Elaichi can narrow that further, for example read only for a Support team, but it can never widen it beyond what Helicone itself allows.

Can my team share one Helicone connection?

Yes. One person connects Helicone with an API key and shares the connection with a team in Elaichi, and nobody else on the team ever handles or sees that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who looked up a Helicone request or scored a response.

Can I stop an agent from deleting or changing things in Helicone?

Yes. Restrictions in Elaichi apply per action, so you can allow reading Helicone requests and dashboards while blocking deleting prompts, submitting scores, or changing properties. A blocked action is never advertised to Claude, ChatGPT, or Cursor at all, so no prompt, however it is phrased, can reach it.

What happens to a Helicone connection when someone leaves?

Offboarding that person in Elaichi ends their access to Helicone at once, across every client they used. If they had shared a Helicone connection with a team, it keeps working for everyone else. If you want Helicone gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client in the same step.

Put Helicone in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.