Navan MCP Server

Navan

Navan is a corporate travel and expense platform. This bundle is read-only across every capability — mutations stay in the Navan Admin UI.

Capability areas

Travel bookings

Paginated corporate travel bookings — flights, hotels, cars, rail — with traveler identity, itinerary, cost, policy flags, and optional payment transactions.

• Filter by trip UUID or booking UUID for a single trip or booking.
• Request include-transactions for payment lines (beta).
• Date windows use Unix epoch seconds on created-from/created-to or updated-from/updated-to. When omitted (and no UUID filter), defaults to bookings created in the last 90 days.
• Pagination: zero-based integer page, default page size 25.

Workspace users

Company user directory — department, cost centre, policy level, manager. Requires users:read on the credential; returns a structured not-granted response when the Booking Data API key lacks that scope.

Expense transactions

Cursor-paginated lists under the Expense Partner API when Navan enabled it on the tenant:

• Navan-issued card charges
• External card programs via Navan Connect
• Manual / reimbursement submissions
• Employee repayments, platform and FX fees, credit/debit memos, daily rebates, card disputes
• Presigned receipt download URLs (expire ~7 days)

Shared expense parameters:

• Modified-date from / to — ISO dates (YYYY-MM-DD); default last 30 days (receipts: last 7).
• Max 93 days per request; oldest allowed date is the first of the month two months ago.
• Cursor from prior response; page size up to 500.
• EU workspaces need credential base URL https://app-fra.navan.com (adds EU region header on expense calls).

When expense access is not granted, the response explains that Expense Partner API is not enabled — not a tool failure.

Workflows

T&E reconciliation: sweep bookings and card/manual transactions for the same modified window; join on traveler email and travel dates.

Compliance audit: filter bookings by type and out-of-policy flag; cross-check card transactions in the same period.

Receipt retrieval: list receipt URLs and download promptly — presigned links expire in about seven days.

Gotchas

• Scope varies by tenant — bookings-only credentials are common; expense and user capabilities degrade gracefully when not granted.
• Date formats differ — bookings use epoch integers; expense uses ISO dates on modified-from/modified-to.
• One booking date window — use either created-from/created-to or updated-from/updated-to, not both in the same call.
• EU region — wrong base URL causes invalid_client on token exchange or expense errors without the EU header.
• Read-only — no booking creation, user provisioning, or expense submission through this bundle.