Artificial Intelligence
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.
In Elaichi
Connect Portkey once
-
Open Connections, choose Add connection, and pick Portkey.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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 Portkey to 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.
Connect Portkey to 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.
Connect Portkey to 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 Portkey 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 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.”
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.
No tools match your search.
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.
Copy the endpoint
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
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
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
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
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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch prompts
Portkey
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
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
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 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.
Put Portkey in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.