Can my team share one Navan connection?

Yes. One administrator connects Navan in Elaichi and shares the connection with a team, and nobody else ever handles the app credentials. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who listed Navan users, not a shared account.

Travel

Navan MCP connector

The Navan connector brings your Navan user roster into Elaichi, so Claude, ChatGPT, Cursor, or any MCP client can list every Navan user inside the access of the person who signed in, with each request logged.

Connect on Elaichi How to connect

How it connects. App credentials. 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.

1 tool

How to connect

How to connect Navan to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Navan once

Open Connections, choose Add connection, and pick Navan.
Optionally set Share with to give a team access, then press Connect.
Paste your Navan app credentials. Navan authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

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

Add connection

Choose a connector.

navan

All categories

Navan

Cloudbeds

Egencia

GuestPoint

Navan SCIM

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 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 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 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 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 on Elaichi See pricing

Use cases

What teams do with Navan through Elaichi

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

Travel management

See who is set up to book travel

Ask for the full list of Navan users before a conference or sales kickoff, so you know who can already book and who still needs an account.
HR

Check new hires have Navan accounts

Pull the Navan user list after an onboarding week and compare it with the starters list, so nobody turns up to their first trip without a way to book.
Finance

Reconcile Navan users against headcount

List everyone in Navan and set it beside the payroll roster to spot accounts for people who have left, or travelers who were never expected to be there.
IT

Audit Navan access after offboarding

Ask for the current Navan users and confirm that departed employees no longer appear, without logging into the Navan admin console yourself.
Operations

Find the right traveler quickly

Ask which Navan users belong to a given office or department when planning a team offsite, and get the names back in plain language.
Executive assistants

Confirm executives and guests are in Navan

Before arranging a board trip, list Navan users to check that each executive and visiting guest already has an account to book against.

Try asking

“List everyone with an active Navan account.”
“Which teams have the most Navan users?”
“Show new Navan users added this month.”

See all 1 Navan tools below

Compare

Elaichi vs Zapier MCP vs Composio for Navan

All three can connect Navan 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, 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 tools	Allow or restrict single Navan 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 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 tools for your AI agents

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

See it in Elaichi

What connecting Navan gets you

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

The agent

Ask Navan questions, get real answers fast.

Type a question in plain language and see live Navan user records answered instantly.

users
trips
bookings
expenses

Ask Elaichi to work across your apps.

List everyone with an active Navan account.

Which teams have the most Navan users?

Show new Navan users added this month.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Connect any MCP client to Navan instantly.

Claude, ChatGPT and Cursor reach Navan 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

1 tool delivers complete Navan user coverage.

Every Navan user record is reachable through one cataloged tool, no custom code required.

List all Navan users

ElaichiTools

Tool	Action	Description
List all Navan users	List	List Navan users. Navan gates user data behind a partner/TMC entitlement that self-serve Navan API Credentials do not carry, so this method returns 403 for every credential created from Travel > Settings > Integrations. For the Navan user directory, connect the Navan SCIM integration (navanscim) instead.

Toolboxes

Every team gets its own Navan toolbox.

Each team works from a toolbox scoped to Navan, matched to what their role needs.

Travel
Finance
HR
IT

ElaichiToolboxes

Name	Source template	Tools	Created
Travel toolbox Navan · trips and bookings	Navan starter	18	Mar 4, 2026
Finance toolbox Navan · expenses and reconciliation	—	9	Mar 2, 2026
HR toolbox Navan · employee travel policy	—	24	Feb 27, 2026
IT toolbox Navan · user provisioning and access	Navan starter	6	Feb 19, 2026
Sales toolbox Navan · client visit scheduling	—	31	Jan 30, 2026
Executive toolbox Navan · travel spend oversight	—	12	Jan 22, 2026

Shared connections

Share Navan access without sharing credentials.

See who connected Navan and how many teams and members work through that connection.

Corporate Travel
Finance NA
HR EMEA
Sales APAC

ElaichiConnections

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

Audit log

Every Navan action is logged and traceable.

See who did what in Navan, when it happened, and which resource it 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	Navan Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes ryan.hayes@northwind.io	Navan Users Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker ashley.parker@northwind.io	Navan 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

Navan digests run and post themselves.

A schedule fires, Navan records are fetched and grouped, a person approves before it posts back.

Navan 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

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

Queued

Collections and dashboards

Navan health updates itself, no requests needed.

Four metrics and a 14 day chart of Navan records refresh on a schedule automatically.

Navan health

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

Live

Users

1,284 ↓ 12%

Trips

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Users created

Last 14 days

By team

Share of activity

Corporate Travel 34%

Finance NA 27%

HR EMEA 21%

Sales APAC 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Navan to Claude?

Connect Navan in Elaichi first: pick Navan from the connector list and paste in the app credentials your Navan administrator already holds. 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 the endpoint https://api.elaichi.ai/mcp. Sign in as yourself and Navan is available in your conversations.

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

Yes. Once Navan 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 Navan once and every client you use can reach it.

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

With this connector an agent can list the users in your Navan account, meaning the people who are set up to book travel. You can ask who has a Navan account, check whether a new hire or a guest appears, or compare the Navan roster with your headcount. It cannot book trips, change traveler details or touch expenses through this connector.

Does connecting Navan give the AI access to my whole company account?

No. Every request to Navan runs as the person who signed in, so the AI sees only the Navan users that person is allowed to see. Elaichi can narrow that further with restrictions, but it can never widen it beyond what Navan itself grants that person.

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

This Navan connector can only list users, it has no way to book, edit or delete anything. Even so, Elaichi restrictions work per action, and any action you block is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it. If Navan gains more actions later, you decide which ones your teams can see.

What happens to a Navan connection when someone leaves?

When you offboard a person in Elaichi their access to Navan through Elaichi ends at once, in every client they used. A Navan connection shared with a team keeps working for everyone else on it. If you want Navan gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other connected client.

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

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

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

How is Elaichi different from Composio for Navan?

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: 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 in front of your team

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

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