Codefresh MCP connector
The Codefresh connector brings Codefresh accounts, users, access rules and analytics reports to Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can ask questions and make changes under their own Codefresh access.
-
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 Codefresh to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Codefresh once
-
Open Connections, choose Add connection, and pick Codefresh.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Codefresh API key. One person generates a token in Codefresh 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.
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.
Codefresh 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.
Codefresh 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 today. The plugin directory lives at chatgpt.com/plugins.
Codefresh 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.
Connect Codefresh 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.
Use cases
What teams do with Codefresh through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Platform engineering
Audit who can touch which pipelines
Ask for every access rule in Codefresh, see which team each one grants access to, and tighten the ones that reach too far.
-
DevOps
Onboard a new engineer in one ask
Add the engineer to the Codefresh account, resend the invite if it was missed, and attach the right team rule without opening the admin console.
-
Security
Review admin accounts before a quarterly check
List every Codefresh admin, spot the people who no longer need that level of access, and remove them in one batch.
-
Engineering management
Pull build analytics into Monday's standup
Read the analytics reports Codefresh already produces and get a short summary of how the week went, ready to paste into the standup notes.
-
IT
Clean up accounts after a reorg
Find Codefresh accounts that belonged to teams that no longer exist and delete them together, with each removal recorded in the audit log.
-
Developer experience
See which GitHub Actions are in use
List the GitHub Actions and their contexts in Codefresh to understand what pipelines depend on before a migration or a cleanup.
Try asking
- “List every Codefresh admin and when they were added”
- “Which access rules give the payments team write access?”
- “Summarize last week's Codefresh analytics reports for the standup”
Compare
Elaichi vs Zapier MCP vs Composio for Codefresh
All three can connect Codefresh 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 Codefresh tools | Allow or restrict single Codefresh 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 Codefresh 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 | $15 per user per month. | 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.
AI tools
Codefresh tools for your AI agents
410 tools are ready to call through Elaichi's MCP endpoint the moment you connect Codefresh, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 275 of 410 Codefresh tools here. Connect Codefresh and call search_tools or tools/list over the MCP endpoint for the complete set.
See it in Elaichi
What connecting Codefresh gets you
6 screens from the product, each doing one job for your Codefresh account.
The agent
Ask Codefresh who has access, in plain words.
Answers come from live Codefresh accounts, access rules and analytics reports, not a stale export.
- accounts
- admins
- github actions
- analytics reports
Ask Elaichi to work across your apps.
List every Codefresh admin and when they were added
Which access rules give the payments team write access?
Summarize last week's Codefresh analytics reports for the standup
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts Codefresh in every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
410 Codefresh tools, ready without writing code.
Access rules, tags rules, accounts, users, admins and analytics reports, each covered as its own tool.
- List all Codefresh abacs
- Create a Codefresh abac
- Get single Codefresh abac by ID
- Codefresh abacs bulk delete
Toolboxes
Each team gets its own Codefresh toolbox.
Security reviews access rules while engineering managers read analytics, each from a toolbox scoped to them.
- Platform engineering
- DevOps
- Security
- Engineering management
Shared connections
Share one Codefresh connection, never the API key.
One person connects Codefresh, shares with teams, and teammates work through it without seeing a credential.
- Platform
- Security
- Core engineering
- Payments
Audit log
Every Codefresh change names who made it.
When, who, what happened, type and resource, appended for every call and never edited.
- When
- Who
- What happened
- Type
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 runs Codefresh work, you approve it.
Analytics reports are fetched, grouped, drafted into a digest, approved, then posted back to Codefresh.
Codefresh digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch accounts
Codefresh
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 Michael Brennan
Approve Deny -
Post the digest
Codefresh
Queued
Collections and dashboards
Codefresh health numbers, computed without a model.
Four metrics, 14 days of accounts created and a breakdown by team, refreshed on schedule.
Codefresh health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Admins
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts created
Last 14 days
By team
Share of activity
Platform 34%
Security 27%
Core engineering 21%
Payments 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Codefresh to Claude?
Connect Codefresh in Elaichi first: paste a Codefresh API key when asked, and the connection is live. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. There is no OAuth application to register in Codefresh and no client ID or secret to generate.
Does Codefresh work with ChatGPT and Cursor as well as Claude?
Yes. Once Codefresh 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 Codefresh once and every client picks it up.
What can an AI agent actually do with my Codefresh data?
It can list and explain Codefresh access rules and tags rules, add or update users and admins, resend invites, read analytics reports, and show which GitHub Actions are set up. You ask in plain language, and short concrete asks like "list every Codefresh admin" work better than long paragraphs. Anything it changes shows up in the audit log under your name.
Does connecting Codefresh give the AI everything in my Codefresh account?
No. Every call runs inside the Codefresh access of the person who signed in, so the agent sees and changes only what that person already could. Elaichi can narrow that further with restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Codefresh?
Yes. Restrictions in Elaichi work per action, so you can allow reading Codefresh access rules and analytics reports while blocking deletes of accounts or admins. A restricted action is never advertised to the AI client at all, so no prompt can reach it.
What happens to a Codefresh connection when someone leaves?
Offboarding that person in Elaichi ends their access to Codefresh through every AI client at once. A shared Codefresh connection keeps working for everyone else on the team. If you want Codefresh gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.
Does the Codefresh MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Codefresh 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, 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 Codefresh?
Yes. Both let Claude, ChatGPT or Cursor use Codefresh. 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 Codefresh call.
How is Elaichi different from Composio for Codefresh?
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 Codefresh: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Codefresh in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.