Helicone MCP connector
The Helicone connector brings your Helicone requests, prompts, evals, and usage dashboards to Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects with an API key
- Free 14-day trial
- No credit card
Summarize Helicone requests with low feedback scores this week.
Working in Helicone with Elaichi
-
List all Helicone AI gateway
-
Helicone AI gateway list multimodal
-
Get single Helicone request by ID
How to connect Helicone to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Helicone MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Helicone MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Helicone MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Helicone MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Helicone MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Helicone to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with Helicone through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Helicone is logged.
-
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.”
What connecting Helicone gets you
6 screens from Elaichi, each doing one job for your Helicone account.
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, Cursor or Microsoft Copilot
The agent
Ask about Helicone requests in plain language.
Starter prompts return answers from live Helicone requests, scores and properties.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Helicone here.
One org MCP endpoint over OAuth, no SDK and no shared API key.
Tool catalog
46 Helicone tools arrive ready to call.
Requests, gateway completions, feedback, scores and dashboards, with no custom code written.
Toolboxes
Every team gets its own Helicone toolbox.
Toolboxes scope Helicone requests and dashboards to the team that needs them.
Shared connections
Teammates query Helicone without holding a key.
The connections table shows who connected each Helicone account and its shared teams.
Audit log
Every Helicone call is on the record.
When, who, what happened, type and resource, appended for each Helicone request touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Helicone digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch requests
Helicone
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Helicone
Queued
Automations
A schedule turns Helicone requests into a digest.
Six steps fetch and group requests, draft a digest, await approval, then post back.
Helicone health
Refreshed 4 minutes ago · every 15 minutes · from the requests collection
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%
Collections and dashboards
Helicone metrics compute themselves on a schedule.
Four metrics, 14 days of requests created and a team breakdown, no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Helicone
All three can connect Helicone to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Helicone tools | Allow or restrict single Helicone tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Helicone call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 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 restricting deleting prompts, submitting scores, or changing properties. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client in the same step.
Does the Helicone MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Helicone is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Helicone?
Yes. Both let Claude, ChatGPT or Cursor use Helicone. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Helicone call.
How is Elaichi different from Composio for Helicone?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Helicone: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Helicone in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot