Skip to content

Portkey MCP connector

The Portkey connector brings your prompts, prompt versions, collections, labels and partials to Claude, ChatGPT, Cursor and any MCP client, so your team can find, edit and test prompts in plain language once Portkey is connected in Elaichi.

  • 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 Portkey to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Portkey once

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

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

  3. Paste a Portkey API key. One person generates a token in Portkey 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.

portkey
Portkey
AirOps
Algolia
Botpress
Braintrust
Chatbase
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.

Portkey MCP connector for 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.

Portkey MCP connector for 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.

Portkey MCP connector for 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 Portkey 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 Portkey through Elaichi

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

  • AI team

    Find the prompt behind a feature

    Ask which Portkey prompt powers the onboarding assistant and read its current text, without clicking through the dashboard.

  • Product

    Tighten a prompt after user feedback

    Describe the change you want, review the new prompt version, and set it as the default once you are happy with it.

  • Platform

    Keep prompts organized by collection

    Move prompts into the right Portkey collections and add labels such as production or experiment so the catalog stays tidy as it grows.

  • Data science

    Test a prompt with a real completion

    Run a chat completion through Portkey with a sample question and compare the answer against the previous version before rolling it out.

  • Support

    Check which prompt version is live

    Confirm which version of a Portkey prompt customers are hitting right now when an odd answer gets reported, then decide whether to roll back.

  • Engineering

    Reuse shared text with prompt partials

    Create a Portkey partial for the standard safety instructions once, then reference it from every prompt instead of pasting the same paragraph around.

Try asking

  • “Which Portkey prompts changed in the last week?”
  • “List Portkey collections and the labels on each.”
  • “Summarize completion volume across our Portkey collections.”

See all 239 Portkey tools below

Compare

Elaichi vs Zapier MCP vs Composio for Portkey

All three can connect Portkey to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Portkey, by what to check
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 Portkey tools Allow or restrict single Portkey 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 Portkey 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

Portkey tools for your AI agents

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

See it in Elaichi

What connecting Portkey gets you

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

The agent

Ask about Portkey prompts, get real answers.

Plain language questions read live Portkey collections, labels and prompts.

  • prompts
  • collections
  • labels
  • completions

Ask Elaichi to work across your apps.

Which Portkey prompts changed in the last week?

List Portkey collections and the labels on each.

Summarize completion volume across our Portkey collections.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Portkey.

One governed 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

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

239 Portkey tools ready to call.

Completions, collections, labels, prompts and realtimes, with no custom code written.

  • Create a Portkey chat completion
  • List all Portkey realtimes
  • Create a Portkey completion
  • List all Portkey collections
ElaichiTools
Tool Action Description
Create a Portkey chat completion Create Create a chat completion in Portkey by sending a conversation's messages and a model name. Returns: id, choices, created, model, system_fingerprint, object, usage. Required: messages, model.
List all Portkey realtimes List Connect to the Portkey Realtime API WebSocket endpoint for streaming realtime sessions. Returns a WebSocket upgrade (101) response on success; the subsequent streaming session follows the provider's realtime protocol. The model query parameter is often required for OpenAI-style realtime sessions.
Create a Portkey completion Create Create a text completion in Portkey by sending a prompt to a model via the AI gateway. Returns: id, choices, created, model, system_fingerprint, object, usage. Required: model, prompt.
List all Portkey collections List List collections in a Portkey workspace, optionally filtered by name search. Returns each collection with id, slug, name, workspace_id, and parent_collection_id. Required: workspace_id.
Create a Portkey collection Create Create a new collection in a Portkey workspace. Returns: id, slug. Required: name.

Toolboxes

Every team gets its own Portkey toolbox.

Curate toolboxes per team so each one sees only relevant Portkey tools.

  • AI Platform
  • Engineering
  • Data Science
  • Product
ElaichiToolboxes
Name Source template Tools Created

AI Platform toolbox

Portkey · prompts and completions

Portkey starter 18 Mar 4, 2026

Engineering toolbox

Portkey · collections and labels

— 9 Mar 2, 2026

Data Science toolbox

Portkey · prompt evaluation runs

— 24 Feb 27, 2026

Product toolbox

Portkey · prompt versions and labels

Portkey starter 6 Feb 19, 2026

Support toolbox

Portkey · completion history lookups

— 31 Jan 30, 2026

Finance toolbox

Portkey · completion usage reporting

— 12 Jan 22, 2026

Shared connections

Teammates use Portkey without seeing keys.

See who connected each Portkey account and which teams and members it reaches.

  • AI Platform
  • Engineering
  • Data Science
  • Product EMEA
ElaichiConnections
Connection Scope Status Access
PO

Portkey (AI Platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
PO

Portkey (Engineering)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
PO

Portkey (Data Science)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
PO

Portkey (Product EMEA)

Connected by Tyler Reed

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

Portkey (Support)

Connected by Ryan Hayes

Personal • Active Not shared
PO

Portkey (Finance)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Answer who called Portkey and when.

Append-only log records time, person, action, type and Portkey resource touched.

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

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Portkey Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Portkey Prompts Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Portkey Prompts 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 drafts your Portkey digest.

Fetch prompts, group them, draft a digest, approve, then post back to Portkey.

Portkey digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch prompts

    Portkey

    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

    Portkey

    Queued

Collections and dashboards

Portkey health, counted not guessed.

Four metrics, 14 days of collections created, split by team, refreshed on schedule.

Portkey health

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

Live

Prompts

1,284 ↓ 12%

Collections

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Prompts created

Last 14 days

By team

Share of activity

AI Platform 34%

Engineering 27%

Data Science 21%

Product EMEA 18%

FAQ

Frequently asked questions

How do I connect Portkey to Claude?

Connect Portkey in Elaichi by pasting a Portkey API key, which takes about a minute. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, and Claude will ask you to sign in to Elaichi as yourself.

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

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

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

With Portkey connected, an agent can list your prompts, read a specific prompt or version, create and edit prompts, set which version is the default, and organize prompts into collections and labels. It can also create partials for shared text and run chat completions through Portkey to test a prompt. Short, concrete asks such as "show me the live version of the refund prompt" work better than long instructions.

Does connecting Portkey give the AI my whole Portkey workspace?

No. Every call to Portkey runs inside the access of the person who signed in, so the agent can only see the prompts, collections and labels that person can already reach in Portkey. Elaichi can narrow that further, for example to reading only, and it never widens what someone could do on their own.

Can my team share one Portkey connection?

Yes. One person connects Portkey in Elaichi and shares it with a team, and nobody else ever handles the Portkey API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every prompt change.

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

Yes. Restrictions in Elaichi work per action, so you can allow reading Portkey prompts and collections while blocking deletes or edits. A blocked action is never advertised to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.

What happens to a Portkey connection when someone leaves?

Offboarding that person in Elaichi ends their access to Portkey through every client at once. If they had shared a Portkey connection with a team, it keeps working for everyone else. When you no longer want Portkey connected at all, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

Does the Portkey MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Portkey 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 Portkey?

Yes. Both let Claude, ChatGPT or Cursor use Portkey. 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 Portkey call.

How is Elaichi different from Composio for Portkey?

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 Portkey: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Portkey in front of your team

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

Works with
Claude ChatGPT Cursor 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.