Can my team share one Navan SCIM connection?

Yes. One administrator connects Navan SCIM with the API key, then shares the connection with a team in Elaichi, and nobody else on that team ever sees or handles the key. Each person still signs in to Elaichi as themselves, so every lookup of a Navan user is logged under the name of the person who asked.

Travel

Navan SCIM MCP connector

The Navan SCIM connector brings the list of people provisioned in Navan into Elaichi, so Claude, ChatGPT, Cursor, or any MCP client can look up who has a Navan account, and every lookup is recorded.

Connect on Elaichi How to connect

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.

2 tools

How to connect

How to connect Navan SCIM to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Navan SCIM once

Open Connections, choose Add connection, and pick Navan SCIM.
Optionally set Share with to give a team access, then press Connect.
Paste a Navan SCIM API key. One person generates a token in Navan SCIM 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.

navan scim

All categories

Navan SCIM

Cloudbeds

Egencia

GuestPoint

Navan

Otto

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.

Navan SCIM 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.

Navan SCIM 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.

Navan SCIM 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 Navan SCIM 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.

Connect Navan SCIM on Elaichi See pricing

Use cases

What teams do with Navan SCIM through Elaichi

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

IT

Check who has a Navan account

Ask for the full list of people provisioned in Navan and spot accounts that should not be there anymore, without opening the admin console.
People

Confirm a new hire is set up

Look up a starter by their user ID to see that their Navan profile exists and is active before their first trip is booked.
Finance

Reconcile Navan seats against headcount

Pull every Navan user and compare the count with the people you are paying for, ready for a license review.
Security

Audit active users before a review

List all Navan SCIM users, filter to who is still active, and hand the compliance team a clean roster in minutes.
Travel

Find out who can book travel

Check whether a colleague already has a Navan profile before asking them to book, instead of guessing or emailing IT.
Operations

Verify a leaver has been removed

Look up a departed employee in Navan by ID and confirm their status has changed, closing the offboarding checklist with evidence.

Try asking

“List all Navan SCIM users added this month.”
“Find the Navan SCIM record for this traveler.”
“Summarize user roles across our Navan SCIM directory.”

See all 2 Navan SCIM tools below

Compare

Elaichi vs Zapier MCP vs Composio for Navan SCIM

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

Navan SCIM tools for your AI agents

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

See it in Elaichi

What connecting Navan SCIM gets you

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

The agent

Ask about travelers, get real answers.

Type a question about Navan SCIM users and see live records answer back.

users
profiles
roles
emails

Ask Elaichi to work across your apps.

List all Navan SCIM users added this month.

Find the Navan SCIM record for this traveler.

Summarize user roles across our Navan SCIM directory.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint, any client, no keys shared.

Claude, ChatGPT and Cursor connect to Navan SCIM through a single governed endpoint.

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

2 tools, full SCIM user coverage.

List every Navan SCIM user or fetch one by id, no custom code required.

List all Navan SCIM users
Get single Navan SCIM user by ID

ElaichiTools

Tool	Action	Description
List all Navan SCIM users	List	List the users in the Navan company directory over Navan's SCIM 2.0 endpoint.
Get single Navan SCIM user by ID	Get	Fetch a single Navan user by SCIM id.

Toolboxes

Every team gets its own toolbox.

IT, security and HR each work from a toolbox scoped to their own needs.

IT
Security
HR
Travel ops

ElaichiToolboxes

Name	Source template	Tools	Created
IT toolbox Navan SCIM · provisioning and access requests	Navan SCIM starter	18	Mar 4, 2026
Security toolbox Navan SCIM · identity review and offboarding	—	9	Mar 2, 2026
HR toolbox Navan SCIM · new hire and leaver records	—	24	Feb 27, 2026
Travel ops toolbox Navan SCIM · traveler profile lookups	Navan SCIM starter	6	Feb 19, 2026
Finance toolbox Navan SCIM · expense and travel policy checks	—	31	Jan 30, 2026
Support toolbox Navan SCIM · user account troubleshooting	—	12	Jan 22, 2026

Shared connections

Delegated access, no credentials exposed.

See who connected Navan SCIM and how many teams work through it, without sharing logins.

Corporate travel
EMEA HR
US IT
APAC operations

ElaichiConnections

Connection	Scope	Status	Access
NA Navan SCIM (Corporate travel) Connected by Emily Carter	Personal	• Active	1 team · 6 members
NA Navan SCIM (EMEA HR) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
NA Navan SCIM (US IT) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
NA Navan SCIM (APAC operations) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
NA Navan SCIM (Finance shared) Connected by Ryan Hayes	Personal	• Active	Not shared
NA Navan SCIM (Security team) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit log

Every SCIM call, logged and traceable.

See who looked up which user, when, and what the call returned.

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	Navan SCIM Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes ryan.hayes@northwind.io	Navan SCIM Users Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker ashley.parker@northwind.io	Navan SCIM Users 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 triggers real provisioning work.

Navan SCIM users are fetched, grouped, drafted into a digest, approved, then posted back.

Navan SCIM digest

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

Run now

✓

Schedule

Every weekday at 8:00 AM

0.2s
✓

Fetch users

Navan SCIM

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

Navan SCIM

Queued

Collections and dashboards

User health, computed on a schedule.

Four metrics and a 14 day chart track Navan SCIM users with no model involved.

Navan SCIM health

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

Live

Users

1,284 ↓ 12%

Profiles

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Users created

Last 14 days

By team

Share of activity

Corporate travel 34%

EMEA HR 27%

US IT 21%

APAC operations 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Navan SCIM to Claude?

Connect Navan SCIM in Elaichi first, which asks you to paste the API key from your Navan admin settings, and nothing more. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Navan SCIM is available in your chat.

Does Navan SCIM work with ChatGPT and Cursor as well as Claude?

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

What can an AI agent actually do with my Navan SCIM data?

With Navan SCIM connected, an agent can list everyone who has a Navan account and look up a single person by their user ID to see details such as their name, email, and whether the account is active. That makes it useful for checking a new hire is set up, confirming a leaver has been removed, or comparing Navan seats against headcount. This connector reads user records, it does not create or change them.

Does connecting Navan SCIM give the AI my whole Navan user directory?

The agent sees only what the API key you connected is allowed to see in Navan SCIM. Elaichi never widens that access, and an administrator can narrow it further by restricting which actions a team is allowed to use. If the key can only read users, that is all any agent connected through Elaichi can do.

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

The Navan SCIM connector in Elaichi can only list users and look up a single user, so there is no delete or edit action for an agent to reach. Restrictions in Elaichi still apply per action, and any action you block is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.

What happens to a Navan SCIM connection when someone leaves?

When you offboard a person in Elaichi, their access to Navan SCIM through every client ends at once. A shared Navan SCIM connection keeps working for everyone else on the team. If you want to remove Navan SCIM entirely, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor, and every other client.

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

Yes. Navan SCIM 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 Navan SCIM?

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

How is Elaichi different from Composio for Navan SCIM?

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

Put Navan SCIM in front of your team

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

Connect Navan SCIM Talk to us

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.