Skip to content

Application Development

Port MCP connector

The Port connector lets Claude, ChatGPT, Cursor, or any MCP client browse your Port catalog, run self-service actions, and check scorecards, with each person signed in as themselves and every call logged.

Connect on Elaichi How to connect

  • How it connects. Connects over OAuth. 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 Port to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Port once

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

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

  3. Approve it in Port. Port's own window opens. Whoever approves it decides what this connection can reach.

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

Add connection

Choose a connector.

port
Port
Apache Airflow
Apify
Boomi
Browserbase
Caspio
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.

Port 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.

Port 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.

Port 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 Port 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.

Connect Port on Elaichi See pricing

Use cases

What teams do with Port through Elaichi

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

  • Platform engineering

    See which services fail a scorecard

    Ask which services in Port are missing an owner, an on-call rotation, or a passing production readiness score, and get the list without opening the portal.

  • Developers

    Run a self-service action from chat

    Scaffold a new service, request a test environment, or trigger any self-service action in Port by asking for it, then track the run until it finishes.

  • SRE

    Check what a workflow run actually did

    Pull up a workflow run in Port, see each step and its outcome, and find out why a deploy or rollback stalled during an incident.

  • Security

    Answer who ran what, and when

    Search the Port audit log for who triggered an action on a production service and what changed, so an access review takes minutes rather than a day.

  • Engineering managers

    Find the owner before an incident grows

    Look up a service entity in Port to find its team, its dependencies, and its recent runs, so the right person is paged first.

  • Platform engineering

    Keep action permissions tidy

    Review who is allowed to run an action in Port, simulate what a blueprint change would let people do, and update the permissions when a team is reorganized.

Try asking

  • “Which services are failing the production readiness scorecard?”
  • “Run the scaffold new service action for the payments team”
  • “Who owns the checkout service and which scorecards does it pass?”

See all 51 Port tools below

Compare

Elaichi vs Zapier MCP vs Composio for Port

All three can connect Port 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 Port, 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 Port tools Allow or restrict single Port 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 Port 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

Port tools for your AI agents

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

See it in Elaichi

What connecting Port gets you

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

The agent

Ask Port about services, owners and scorecards.

Type a question in plain language and get answers from live Port entities.

  • blueprints
  • entities
  • actions
  • workflows

Ask Elaichi to work across your apps.

Which services are failing the production readiness scorecard?

Run the scaffold new service action for the payments team

Who owns the checkout service and which scorecards does it pass?

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint puts Port in every client.

Claude, ChatGPT and Cursor connect to Port through one governed endpoint, no SDK or shared 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

51 Port tools, no code to write.

Blueprints, entities, actions, workflows, scorecards and audit logs, ready without any custom code.

  • Get action permissions
  • Get workflow run
  • List actions
  • List self service triggers
ElaichiTools
Tool Action Description
Get action permissions Get Get permissions/approval config for actions.
Get workflow run Get Get the status and details of a workflow run by its identifier. Use after trigger_run to poll for completion, or to inspect any previously-triggered run. Returns status, result, per-node execution details, and timestamps.
List actions List List actions and automations in your organization. Without identifiers, returns a summary list. With identifiers, returns full action details including complete input schemas. Self-service workflow triggers are a separate concept - use list_self_service_triggers to discover…
List self service triggers List List self-service workflow triggers the caller can execute. Returns workflow metadata, the trigger nodeIdentifier, and the input schema for each trigger. Use before trigger_run to discover available operations and required inputs.
List workflows List List workflows in your organization. Without identifiers, returns a summary list. With identifiers, returns full workflow details including trigger configuration and node definitions.

Toolboxes

Every team gets its own Port toolbox.

Scope Port tools to platform, SRE, security or developer teams, each with its own toolbox.

  • Platform engineering
  • SRE
  • Security
  • Developers
ElaichiToolboxes
Name Source template Tools Created

Platform engineering toolbox

Port · blueprints and actions

 Port starter 18 Mar 4, 2026

SRE toolbox

Port · workflows and runs

 — 9 Mar 2, 2026

Security toolbox

Port · permissions and audit logs

 — 24 Feb 27, 2026

Developers toolbox

Port · self-service actions

 Port starter 6 Feb 19, 2026

Engineering managers toolbox

Port · scorecards and ownership

 — 31 Jan 30, 2026

Developer experience toolbox

Port · pages and widgets

 — 12 Jan 22, 2026

Shared connections

Share a Port connection, not a credential.

One person connects Port, teammates run actions through it and never see a token.

  • Platform
  • SRE
  • Security
  • Payments team
ElaichiConnections
Connection Scope Status Access
PO

Port (Platform)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
PO

Port (SRE)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
PO

Port (Security)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
PO

Port (Payments team)

Connected by Tyler Reed

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

Port (Core services)

Connected by Ryan Hayes

 Personal • Active Not shared
PO

Port (Infra)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Audit log

Know who ran which Port action, always.

Every call shows when, who, what happened, type and the Port 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

[email protected]

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

[email protected]

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

[email protected]

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

[email protected]

 Port Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

[email protected]

 Port Blueprints Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

[email protected]

 Port Blueprints 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 runs Port work end to end.

Scorecard results are fetched, grouped, drafted into a digest, approved, then posted back to Port.

Port digest

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

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch blueprints

    Port

    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

    Port

    Queued

Collections and dashboards

Port health numbers arrive on a schedule.

Four metrics, 14 days of entities created and a team breakdown, computed without a model.

Port health

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

Live

Blueprints

1,284 ↓ 12%

Entities

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Blueprints created

Last 14 days

By team

Share of activity

Platform 34%

SRE 27%

Security 21%

Payments team 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Port to Claude?

Connect Port in Elaichi first: pick Port from the catalog, sign in to your Port organization when the OAuth screen appears, and approve the access. 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 https://api.elaichi.ai/mcp as the endpoint. Claude signs you in through Elaichi and Port is ready to use.

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

Yes. Once Port 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 Port once and every client you use picks it up.

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

An agent connected to Port can look up services, teams, and other entities in your catalog, tell you which ones are failing a scorecard, run a self-service action such as scaffolding a service, and follow a workflow run step by step. It can also search the Port audit log, review who is allowed to run an action, and read your Port pages and knowledge sources. Short concrete asks, such as naming the service and the scorecard, work better than long sentences.

Does connecting Port give the AI access to everything in my Port organization?

No. Every request to Port runs as the person who signed in, so the agent sees only the blueprints, entities, and actions that person can already see in Port, and can only run the actions that person is allowed to run. Elaichi can narrow that access further with roles and restrictions, but it can never widen it beyond what Port itself grants.

Can my team share one Port connection?

Yes. One person connects Port in Elaichi and shares the connection with a team, and nobody else has to handle a token or sign-in detail. Each teammate still signs in to Elaichi as themselves, so every action run or entity read in Port is logged under their own name, not the name of the person who connected it.

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

Yes. Restrictions in Elaichi apply per action, so you can allow reading entities and scorecards while blocking the ability to delete an action, delete a workflow, or change action permissions in Port. A restricted tool is never advertised to the AI client at all, so no prompt, however it is worded, can reach it.

What happens to a Port connection when someone leaves?

When a person is offboarded in Elaichi, their access to Port through Elaichi ends at once, across every client they used. A Port connection shared with a team keeps working for everyone else on that team. If you want Port gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time.

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

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

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

How is Elaichi different from Composio for Port?

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

Put Port in front of your team

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

Connect Port Talk to us
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.