travel
Egencia
Connect Egencia to Elaichi and hand every teammate a governed MCP endpoint — 44 tools ready to call from Claude, Cursor, or any MCP client, clamped by roles, restrictions, and an audit log.
AI tools
Egencia tools for your AI agents
44 tools are ready to mint as an MCP endpoint the moment you connect Egencia — governed by the same roles, restrictions, and audit log as everything else in Elaichi.
egencia_auth_generate_token
Generate an OAuth2 access token for the Egencia API using the client credentials grant flow. Returns: access_token, token_type, expires_in. Required: client_id, grant_type.
list_all_egencia_users
List all Egencia users for a company via the SCIM 2.0 User Sync API. Returns: schemas, id, userName, name, displayName, title, userType, active, emails, phoneNumbers, addresses, roles, groups, meta, urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.0:User. Supports SCIM 2.0 standard filtering, sorting, and attribute selection.
create_a_egencia_user
Create a user in Egencia using the SCIM v1 User Sync API. The request body follows the SCIM 2.0 core User schema and the enterprise extension schema. Returns the created SCIM user object including its id, schemas, and userName.
get_single_egencia_user_by_id
Get a single Egencia user by id via the SCIM 2.0 User Sync API. Returns the complete SCIM user profile including its id, schemas, core user attributes, and enterprise extension attributes. Required: id.
update_a_egencia_user_by_id
Update a complete Egencia user profile by id using the SCIM 2.0 protocol; the full user profile must be sent in the request body. Returns: id, schemas, userName, name, title, emails, phoneNumbers, addresses, active, roles, userType, meta. Required: id, schemas, userName.
delete_a_egencia_user_by_id
Delete an Egencia user by id via the SCIM v1 User Sync API. Returns an empty 204 response on success. Required: id.
egencia_users_partial_update
Partially update a specific Egencia user profile by id using SCIM 2.0 PATCH operations. Returns the updated user resource including id, userName, schemas, active, and meta. Required: id. Supported operations are "add", "remove", and "replace".
list_all_egencia_groups
List Egencia SCIM groups, including arranger groups used for travel arranger role associations. Returns each group with its id, displayName, members, schemas, and meta. Follows SCIM 2.0 protocol.
get_single_egencia_group_by_id
Get a specific Egencia arranger group by its id following the SCIM 2.0 protocol. Returns: schemas, id, displayName, members, meta. Required: id.
egencia_approvals_approve_booking
Approve an Egencia booking by booking id. Returns an empty 204 response on success. Required: booking_id.
egencia_approvals_deny_booking
Deny an Egencia booking by booking id. Returns an empty 204 response on success. Required: booking_id.
egencia_approvals_approve_booking_item
Approve a specific item within an Egencia booking. Returns an empty 204 response on success. Required: booking_id, item_id.
egencia_approvals_deny_booking_item
Deny a specific item within an Egencia booking. Returns an empty 204 response on success. Required: booking_id, item_id.
list_all_egencia_cdfs
List all Custom Data Field (CDF) definitions for an Egencia company. Returns each definition's code, fieldType, id, maxLength, name, rules, and status. Required: company_id.
egencia_duty_of_care_search_bookings
Search Egencia Duty of Care bookings by partner and date range. Returns paginated booking data and metadata for travellers within the specified date range, including booking details by line of business (FLIGHT, CAR, HOTEL, TRAIN). Required: partner_id, start_date_time, end_date_time, company_id. Dates must use format YYYY-MM-DDTHH:MM:SSZ and cannot be in the future; start_date_time must not…
egencia_duty_of_care_get_report
Pull report data for a specific Egencia Duty of Care document by doc_id. Returns the report data as a HAL+JSON response; the upstream source does not document specific response fields. Required: doc_id.
egencia_bookings_cancel
Cancel an entire Egencia booking at the trip level, cancelling all trip items in the booking. Returns per-item cancellation status along with error details for any items that fail. Returns: status, error_code, error_message. Required: booking_id.
egencia_bookings_cancel_item
Cancel a single trip item within an Egencia booking at the trip item level. Returns the action-level status of the cancellation request. Returns: status, error_code, error_message. Required: booking_id, item_id.
delete_a_egencia_booking_by_id
Delete an entire Egencia booking at the trip level, deleting all eligible trip items and returning per-item statuses. Returns the action-level status along with per-item deletion results. Returns: status, error_code, error_message. Required: booking_id.
egencia_bookings_delete_item
Delete a single trip item within an Egencia booking at the trip item level. Returns the action-level status of the deletion request. Returns: status, error_code, error_message. Required: booking_id, item_id.
get_single_egencia_booking_by_id
Get a single Egencia booking by id. The response is returned in HAL+JSON format. Returns: id. Required: id.
get_single_egencia_receipt_by_id
Get a receipt PDF from Egencia by item id. Returns the receipt as a binary PDF download (application/octet-stream). Required: id.
egencia_reports_create_all_lob
Create a transaction report covering all Lines of Business in Egencia. Returns the created report object including its id and report attributes. Required: start_date, end_date.
egencia_reports_create_air
Create an air booking transaction report in Egencia, supporting report levels of ticket, segment, or leg. Returns the created report object including its id and report attributes.
egencia_reports_create_hotel
Create a hotel booking transaction report in Egencia. Returns the created report object including its id and report attributes.
egencia_reports_create_car
Create a car booking transaction report in Egencia's Business Intelligence API. Returns a generated report covering car rental transactions for the requested date range. Required: start_date, end_date.
egencia_reports_create_train
Create transaction reports for train bookings in Egencia. Supports report_level: ticket. Returns: data. Required: report_level.
create_a_egencia_validate_field
Validate booking fields in Egencia against configured CDF validation rules. Returns: errors, valid. Requires a CDFValidationRequest JSON body.
get_single_egencia_company_by_id
Get Egencia company information for a specific company by id, including its name, display_name, and other company details. Required: id.
egencia_sso_create_context
Create an Egencia SSO context to enable a seamless Single Sign-On login experience allowing travelers to log in with their company credentials. Returns: context_id.
egencia_sso_get_context
Get an Egencia SSO context by context_id to retrieve the Single Sign-On login context for a traveler. Returns: context_id. Required: context_id.
list_all_egencia_users_v_2
List all users of a company in Egencia following the SCIM 2.0 protocol. Returns a collection of user records from the Resources array, each including standard SCIM attributes such as id, userName, name, emails, and active.
create_a_egencia_users_v_2
Create a new Egencia user via the SCIM 2.0 User Sync API (v2). Returns the created user resource including id, userName, name, emails, and active. Required: schemas, userName.
get_single_egencia_users_v_2_by_id
Get a single Egencia user by id via the SCIM v2 User Sync API. Returns the SCIM 2.0 user resource including schemas, id, userName, name, displayName, emails, phoneNumbers, active, title, and meta. Required: id.
update_a_egencia_users_v_2_by_id
Update a complete Egencia user profile by id via SCIM v2. The entire user profile must be sent in the request body — partial updates require the PATCH endpoint. Returns: schemas, id, userName, name, displayName, emails, phoneNumbers, active, title, meta. Required: id.
egencia_users_v_2_partial_update
Update specific fields in an Egencia user profile using SCIM PATCH operations. Returns the updated user object including id, userName, userType, emails, and roles. Required: id, schemas, Operations. Supported operations: add, remove, and replace.
delete_a_egencia_users_v_2_by_id
Delete an Egencia user by id via the SCIM v2 User Sync API. Returns an empty 204 response on success. Required: id.
list_all_egencia_cdf_values
List all CDF values for a company and CDF definition in Egencia. Returns: id, value, description, childCount, parentCount. Required: company_id, definition_id.
create_a_egencia_cdf_value
Create a new CDF value for a CDF of field type List in Egencia. Returns: id, value, description, childCount, parentCount. Required: company_id, definition_id, value.
get_single_egencia_cdf_value_by_id
Get a single linked CDF value by id in Egencia, including its child and parent linked values. Returns: id, value, description, childCount, parentCount, links. Required: company_id, definition_id, id.
update_a_egencia_cdf_value_by_id
Update a CDF value for a CDF of field type List in Egencia. Returns: id, value, description, childCount, parentCount. Required: company_id, definition_id, id, value.
delete_a_egencia_cdf_value_by_id
Delete a CDF value for a CDF of field type List in Egencia. Returns an empty 204 response on success. Required: company_id, definition_id, id.
egencia_cdf_values_bulk_update
Update a CDF value's child/parent links in Egencia by adding or removing link associations via JSON Patch operations. Returns: childCount, description, id, links, parentCount, value. Required: company_id, definition_id, value_id. Available for CC1/CC2 linking for offices in EU/APAC.
list_all_egencia_search_users
Search Egencia users using the SCIM 2.0 POST .search endpoint. Returns complete user profile details including id, userName, emails, displayName, and active status. The response follows the SCIM 2.0 core User schema.
How it works
From Egencia account to governed MCP endpoint
Connect
Link a Egencia account through Elaichi's hosted connect flow. Credentials are vaulted — nobody, including the AI, ever sees them.
Compose
The connection becomes a toolbox instantly. Curate which Egencia tools are exposed, rename them, or freeze arguments.
Mint
Mint a personal MCP endpoint on that toolbox and paste it into Claude, Cursor, or any MCP client — governed by roles, restrictions, and audit logs.
Give every teammate a governed MCP server
Start a 14-day Gold trial — connect a product, curate a toolbox, and paste an endpoint into Claude or Cursor in minutes.