# 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. Source: https://elaichi.ai/connectors/navanscim/ ## Facts | | | | --- | --- | | Application | Navan SCIM | | Category | Travel | | AI tools | 2 | | Authentication | Connects with an API key | | 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 SCIM is connected - List all Navan SCIM users added this month. - Find the Navan SCIM record for this traveler. - Summarize user roles across our Navan SCIM directory. ## Connect Navan SCIM in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Navan SCIM. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Navan SCIM tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Navan SCIM 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 SCIM 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 SCIM 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 SCIM 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 SCIM 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 SCIM through Elaichi ### Check who has a Navan account IT. Ask for the full list of people provisioned in Navan and spot accounts that should not be there anymore, without opening the admin console. ### Confirm a new hire is set up People. Look up a starter by their user ID to see that their Navan profile exists and is active before their first trip is booked. ### Reconcile Navan seats against headcount Finance. Pull every Navan user and compare the count with the people you are paying for, ready for a license review. ### Audit active users before a review Security. List all Navan SCIM users, filter to who is still active, and hand the compliance team a clean roster in minutes. ### Find out who can book travel Travel. Check whether a colleague already has a Navan profile before asking them to book, instead of guessing or emailing IT. ### Verify a leaver has been removed Operations. Look up a departed employee in Navan by ID and confirm their status has changed, closing the offboarding checklist with evidence. ## 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 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. ### 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. ## All 2 Navan SCIM tools Every tool below is callable through https://api.elaichi.ai/mcp once Navan SCIM is connected, subject to the toolbox it is in and the restrictions on the caller. - **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.