MCP tools

Tool names below are exactly what MCP clients discover on the wire.

Public route

The public route (https://mcp.visamundi.io/) needs no key. It serves travel reference data and lets an AI agent prepare a visa application for a traveller. The same tools are available to browser agents on the application form through WebMCP.

Reference data

Results are compact summaries meant for answering a traveller, not a bulk data feed. Each anonymous client gets 200 reference lookups per day (reset at midnight, Paris time); application tools are not counted. For structured data at volume, use the REST API with a key.

Tool	Parameters	What it does
`get_visa_requirements`	`nationality`, `destination`, `language?`	Whether a visa is required, or visa-free entry applies, for a nationality visiting a destination.
`list_visas`	`destination`, `nationality?`, `reason?`, `stay_duration?`, `language?`	Visa products available for a destination.
`get_visa`	`id`, `language?`	Full details for one visa product.
`get_vaccines`	`country_code`	Required and recommended vaccines for a destination.
`get_customs`	`country_code`	Customs rules for a destination.

Submit an application

These tools prepare a Visamundi application on the traveller’s behalf and return a payment link. The agent never pays and never accepts terms, consents or disclaimers: the traveller does it on the page opened by the link.

Tool	Parameters	What it does
`get_application_form`	`visaId`, `language?`	Accepted purposes and nationalities, JSON Schema of `values` and `travelers`, visa questionnaire, date and passport-validity constraints, options, estimated price.
`save_application`	`visaId`, `locale`, `applicationId?`, `resumeToken?`, `values?`, `travelers?`, `affiliateCode?`	Creates the application (without `applicationId`) or updates it. Returns `applicationId`, `resumeToken`, `reference`, `pricing` and `missing`. `affiliateCode` is the partner code (`ag404`) when the traveller came through a partner link; an application keeps its first code.
`get_payment_link`	`applicationId`, `resumeToken`	Payment link, total and estimated delivery date for a complete application.

Workflow:

list_visas then get_visa: agree on the visa product with the traveller. Its id is the visaId of the next tools.
get_application_form: read what is required.
save_application: keep the returned applicationId and resumeToken (the token gives access to the application: do not show it).
While missing is not empty, ask the traveller for the listed fields and call save_application again with the same applicationId and resumeToken. Each entry has a path, a reason and sometimes a hint (allowed values, minimum date, expected format):
```
{ "path": "travelers[0].nationality", "reason": "not_allowed",
  "hint": "ISO 3166-1 alpha-3 code from the schema enum, e.g. FRA" }
```
get_payment_link: give the url to the traveller.

get_payment_link also returns estimatedDelivery, or null when no estimate is available:

{
  "url": "https://form.visamundi.app/en/reprendre/…?step=recapitulatif",
  "total": 29,
  "currency": "EUR",
  "estimatedDelivery": {
    "latestDate": "2026-12-14",
    "cappedFarTrip": false,
    "condition": "Subject to the immediate provision and validation of the required documents after payment."
  }
}

latestDate is an estimate, not a guarantee: always quote it with its condition. When cappedFarTrip is true, issuance is deliberately scheduled closer to a distant trip and cappedExplanation says why.

Notes:

Country codes in values and travelers are ISO 3166-1 alpha-3 (FRA), dates are YYYY-MM-DD. Up to 10 travellers per application.
Priority processing, document-based visas and multi-country packs are not available through these tools.
Errors come back as tool errors with the action to take: missing fields, invalid resumeToken, application already paid, or too many requests (write calls are rate limited per client).

Partner route

The hosted partner MCP server exposes tools dynamically from the tools enabled on your credential. Two partners may see different tool sets even when they connect to the same partner endpoint.

After you change tool toggles in the portal, Cursor and other clients may keep showing the old list until you reconnect the MCP entry. See Refreshing tools after portal changes on the Connect page — MCP logout alone is often not enough.

Connect visa catalog

These tools read visa catalog data from Visamundi Connect using a server-side token. That token is never returned to the MCP client.

Tool	Parameters	What it does
`list_visas`	`destination`, `nationality?`, `reason?`, `stay_duration?`, `language?`	Discover visa products for a destination; optionally filter by nationality, trip reason, minimum stay (days), or response language.
`get_visa`	`id`, `language?`	Fetch full details for one visa product by numeric ID. Use after `list_visas` when a product is chosen.

Country codes are ISO 3166-1 alpha-2 or alpha-3 (for example TH, IND). Optional language values are ISO 639-1 (for example en, fr). Optional reason is a slug such as tourism or business.

Partner portal data

These tools return information from the partner portal for the company linked to your MCP key.

Tool	Parameters	What it does
`get_company`	—	Return the partner company profile bound to the current MCP credential.
`list_travel_groups`	—	List B2B travel groups for the current partner account.
`get_travel_group`	`travel_group_id`	Fetch one travel group with traveler details, invoice metadata, and partner-visible operational fields.
`list_referred_applications`	—	List applications generated through the partner’s affiliate links.
`get_referred_application`	`referred_application_id`	Fetch one referred application with traveler details and invoice metadata.
`list_invoices`	—	List invoice metadata for travel groups and referred applications.
`get_processing_load`	`country_code`, `visa_id?`	Return average processing load for a destination and optional visa id.
`get_delivery_window`	`record_id`	Estimate the delivery window for a travel group or referred application.
`get_affiliate_stats`	`from?`, `to?`	Return click and conversion aggregates for the company over an optional date range (`YYYY-MM-DD`).

Portal vocabulary

A travel group is a B2B case managed from the Travel Groups section.
A referred application is an application generated through affiliate links.
MCP exposes them as separate tools so the names match what you see in the portal.

Options worth knowing

Call get_company first when you need account context before other portal tools.
For visa eligibility questions, use list_visas (and get_visa for one product) on the partner endpoint; the public MCP route additionally exposes get_visa_requirements, get_vaccines, and get_customs.
For get_travel_group, get_referred_application, and get_delivery_window, say which case you mean in plain terms — for example the destination and the name of the travel group, or similar details for a referred application — so the client can locate the right record before calling the detail tool.

Access

Partner portal tools only show your company’s data: your travel groups, referred applications, invoices, and the rest of the information tied to your account. You do not see other partners’ records.