# 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. Source: https://elaichi.ai/connectors/navan/ ## Facts | | | | --- | --- | | Application | Navan | | Category | Travel | | AI tools | 1 | | Authentication | App credentials | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Navan is connected - List everyone with an active Navan account. - Which teams have the most Navan users? - Show new Navan users added this month. ## Connect Navan in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Navan. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Navan tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Navan to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Navan to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Navan to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Navan to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Navan tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Navan through Elaichi ### See who is set up to book travel Travel management. 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. ### Check new hires have Navan accounts HR. 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. ### Reconcile Navan users against headcount Finance. 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. ### Audit Navan access after offboarding IT. Ask for the current Navan users and confirm that departed employees no longer appear, without logging into the Navan admin console yourself. ### Find the right traveler quickly Operations. Ask which Navan users belong to a given office or department when planning a team offsite, and get the names back in plain language. ### Confirm executives and guests are in Navan Executive assistants. Before arranging a board trip, list Navan users to check that each executive and visiting guest already has an account to book against. ## 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 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. ### 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. ## All 1 Navan tools Every tool below is callable through https://api.elaichi.ai/mcp once Navan is connected, subject to the toolbox it is in and the restrictions on the caller. - **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.