Kiaaccess MCP vs LetsFG — Flights & Hotels
A side-by-side look at the Kiaaccess MCP and LetsFG — Flights & Hotels MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kiaaccess MCP for travel & transportation work as a local process; choose LetsFG — Flights & Hotels for travel & transportation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kiaaccess MCP when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
KIA_USERNAME, KIA_PASSWORD. - You want tools like
kia_healthcheck, kia_session_status, kia_start_login.
Choose LetsFG — Flights & Hotels when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search_flights, resolve_location, book_flight.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Travel & Transportation | Travel & Transportation |
| Quality signal | 63/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | other | Not declared |
| Pricing | Free | Not declared |
| Required env vars | KIA_USERNAMEKIA_PASSWORD | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2,175 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 1 installs 0 upvotes |
| Tools | 16 | 14 |
| Full listing | View Kiaaccess MCP | View LetsFG — Flights & Hotels |
Tools & capabilities
Kiaaccess MCP tools 16
kia_healthcheckResolves the credential the way real tools do, then makes one authenticated request to Kia Connect. Reports which source supplied the credential, whether Kia Connect accepted it, the round-trip time, and a plain-English hint distinguishing 'no credential' from 'credential rejected' from 'a Kia Connect-side problem'. Read-only; never returns the credential itself. Call this when a real tool fails and you want to know which hop broke.kia_session_statusWhether this server is configured and logged in to Kia: are credentials present, has the one-time MFA bootstrap been completed on this device, and which vehicle commands are registered (KIA_WRITE_MODE). Makes NO network call and returns no secret — the account email is masked, the device id is truncated, and neither the session id nor the remember-me token is ever included. Start here when a Kia tool reports it is not configured.kia_start_loginStep 1 of the ONE-TIME Kia MFA bootstrap (prof/authUser): send the configured credentials and get back the `otpKey` and `xid` the next two steps need. Only needed when kia_session_status reports hasSession:false — once the bootstrap is done the stored remember-me token refreshes sessions silently forever. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call makes NO network call and returns a preview plus a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). The gate is real: Kia counts failed logins and eventually enforces reCAPTCHA, which breaks server-side login for this account PERMANENTLY — so a rejection is never retried, and a wrong password must be fixed in the environment rather than guessed at.kia_send_otpStep 2 of the Kia MFA bootstrap (cmm/sendOTP): deliver a one-time passcode to the account by SMS or email. Takes the `otpKey` and `xid` from kia_start_login — it cannot run without them, which is why it has no separate confirmation gate. Ask the user which channel they want (kia_start_login reports the masked destinations Kia has on file). The passcode expires in about two minutes; `expiresAt` reports when.kia_verify_otpStep 3 of the Kia MFA bootstrap (cmm/verifyOTP): exchange the passcode for a session. The resulting remember-me token is stored locally and is NOT returned — from here on every Kia tool refreshes its own session silently and MFA is never needed again on this device. Takes the `otpKey` and `xid` from kia_start_login plus the code the user received.kia_forget_sessionDiscard the locally stored Kia session (the remember-me token), so the next Kia call needs the one-time MFA bootstrap again. This is the recovery path when the stored token no longer works — Kia revoked it, the password changed, or the account moved to another device — and the only alternative is deleting the session file by hand. It makes NO network call: Kia is not told anything, only this machine forgets. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call makes NO network call and returns a preview plus a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Nothing is deleted until it is confirmed.kia_list_vehiclesList the vehicles enrolled on this Kia Owners account (ownr/gvl). Returns each vehicleKey — the id every other Kia tool takes — plus nickname, model year/name/trim, mileage, fuel type and telematics unit. VINs are masked to their last 6 characters.kia_vehicle_statusRead the vehicle's CACHED status (cmm/gvi): door lock, ignition, and the remote-climate block. Fast, but it reports whatever the telematics unit last uploaded — use kia_refresh_status first when freshness matters. Requested with airTempRange/seatHeatCoolOption = "1" so the nested `climate` object is present; when it is still absent the result says so rather than reporting climate as off. Note `ign3` (not `engine`) is the ignition on an EV, and `syncDate` advances on every read, so it never proves anything changed. Per-seat heat/vent state is reported under `climate.seats` as the RAW numbers Kia sends: the `heatVentType`/`heatVentLevel` encoding is UNVERIFIED, so do not tell the user a seat is heating, ventilating or off based on them. An absent seat block means this read carried no seat data — it does NOT mean the car lacks heated seats, which this server cannot currently determine. Pass include_raw for the untrimmed status block (battery/EV detail, doors, tyres, …).kia_refresh_statusAsk the car for a fresh reading (rems/rvs, requestType 0). This WAKES THE TELEMATICS UNIT, so it is much slower than kia_vehicle_status and draws a little power — prefer the cached read unless staleness matters. Kia only acknowledges the request; it does not return the new data and gives no completion signal, so read kia_vehicle_status afterwards to see the refreshed values.kia_vehicle_locationThe vehicle's last known location, from the `location` block of the cached cmm/gvi read. This is where the telematics unit last reported being, not a live GPS fix — run kia_refresh_status first for a recent one. Latitude/longitude and a map link are derived when the block carries `coord.lat`/`coord.lon`; otherwise the raw block is returned as-is (its exact field names are not verified).kia_start_climateStart remote climate control / preconditioning (Kia `rems/start`, live-verified). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call makes NO network call and returns a preview plus a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Once confirmed it sends the command and re-reads cmm/gvi until the NESTED `climate.airCtrl` reads true (there is no flat `airCtrlOn` field). On an EV `engine` stays false while climate runs — `ign3` is the ignition proxy and is reported alongside. `commandAccepted` (Kia took the request) and `stateConfirmed` (the car actually reads running) are separate; state changes were observed to take 30–60s. TEMPERATURE IS BEST-EFFORT AND UNCONFIRMED: per docs/KIA-API.md a start requesting 70°F still read back 72°F, so the car may report its own last-set target rather than the requested one — do not promise the user a specific cabin temperature. Seat and steering-wheel/rear-window heating are not sent at all: the request body deliberately omits `heatVentSeat` (Kia validates seat capability per car) and leaves every `heatingAccessory` field at 0.kia_stop_climateStop remote climate control (Kia `rems/stop`, live-verified). Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call makes NO network call and returns a preview plus a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). Once confirmed it sends the command and re-reads cmm/gvi until the NESTED `climate.airCtrl` reads false (there is no flat `airCtrlOn` field); `ign3` — the EV ignition proxy — is reported alongside. `commandAccepted` (Kia took the request) and `stateConfirmed` (the car actually reads stopped) are separate. State changes were observed to take 30–60s.- +4 more on the listing page
LetsFG — Flights & Hotels tools 14
search_flightsSearch hundreds of airlines for live flight prices — completely FREE, unlimited, read-only. Returns structured offers with prices, airlines, times, durations, and stopovers. Some offers carry `starlink` for in-flight Starlink Wi-Fi: "confirmed_all" / "confirmed_some" mean the carrier has FULLY fitted that aircraft type, "likely_all" / "likely_some" mean the rollout on that type is underway but incomplete. State only "confirmed_*" as fact; describe "likely_*" as "the airline is fitting this aircraft type, not guaranteed on your flight". Anything ending in "_some" has at least one leg WITHOUT it. An absent field means no information, NOT an absence of Wi-Fi. Covers airlines across all continents including low-cost carriers. Search is async: this tool polls for you, including waiting out the late split-ticket merge. Some offers are SPLIT TICKETS: two separately-issued tickets through a hub, each leg booked from whatever is cheapest for it (usually two different airlines), because no one seller offers the combination as a single ticket. They carry `split_ticket: "true"`, `combo_type: "virtual_interlining"` and `self_transfer: "unprotected"`. ALWAYS tell the user when an offer is a split ticket and what unprotected means: the tickets are not linked, so if the first flight is late and the connection is missed, the second airline owes nothing — no rebooking, no refund. Never present a split ticket as though it were one through-fare. Requires LETSFG_BEARER_TOKEN or LETSFG_API_KEY. See letsfg://guide resource for the full authenticate->search->book workflow.resolve_locationConvert a city/airport name to IATA codes. Always call before search_flights if you only have a city name. Read-only, safe to call multiple times.book_flightBook a flight from a search result. FLOW: authenticate (once) -> search_flights -> book_flight CHARGES: nothing from LetsFG. A completed booking pays the airline prices from airlines and the major booking sites. RESULT: either {"booked": true, "order_id": "..."} or {"booked": false, "booking_url": "..."} — the second means the booking genuinely did not complete and nothing was charged. That is a normal outcome, NOT a transient error: do not retry, give the user the booking_url. SAFETY: use REAL passenger details — names must match passport, email receives the e-ticket.get_flight_bookingPoll a flight booking started by book_flight. REQUIRED to learn the outcome: on a PFS Bearer token book_flight returns a booking_ref and state "booking_in_progress", not a PNR - the booking itself takes 4-11 minutes. Call it every 20-30 s with that booking_ref until state is terminal: completed -> PNR issued, card charged failed -> the hold was released, nothing was charged needs_attention -> a human is looking at it; do NOT rebook Do not rebook while the state is still moving, and do not treat a slow poll as a failure - the money is HELD, not taken, until the airline confirms. Refs last one hour past the booking start.answer_booking_questionAnswer the question a paused booking is waiting on. get_flight_booking returns `awaiting_choice` when the booking agent has stopped mid-checkout holding a cart: at the airline's own seat map, at a paid extra it has just priced, or at a fare that moved. NOTHING PROGRESSES UNTIL YOU ANSWER, and the cart expires. Put the question to the traveller with the options and the time left, then send their answer here. kind "seat" -> seats: [{ d: "12A" }, ...] from the map you were shown, or skip: true kind "extra" -> confirm: true to take it (a bag, or a moved fare), or confirm: false / skip: true to decline Always pass the `round` from `awaiting_choice` - it says WHICH question you are answering. A return trip pauses twice, and an answer without it could seat the wrong leg.resolve_hotel_cityConvert a place name to the supplier city id that search_hotels needs. Always call this first if you only have a city name. Read-only and safe to repeat. Use `Id` from the first result as city_id and `Name` as city_name.search_hotelsSearch real, bookable hotel inventory. Requires a connected payment method — the SAME one that authorises flight booking. That applies to search too, not just booking, because a search opens a real session at the supplier. Every rate type is returned, refundable and non-refundable; each offer's `refundable` and `free_cancellation_until` say which. `price` is what the guest pays, in `currency` (USD unless you pass currency): the supplier's cost plus `markup_rate` (6.4% for Revolut Pay or an EEA card, 8.3% for a card issued outside the EEA). Nothing is added at booking. Keep the chosen offer whole — book_hotel needs its `session_id`, `combination_id_v2`, `price`, `expected_cost`, `currency` and `fx_rate`. Takes up to a few minutes.book_hotelBook one hotel rate. The offer's full price is HELD on the connected Revolut payment method (authorised, not taken); LetsFG books and pays the supplier; the hold is captured only once the supplier has confirmed. If the booking fails for any reason the hold is released and nothing is charged. There is no reservation fee, no deposit and no pay link. Returns a booking_job_id, NOT the booking — a booking takes minutes. Poll get_hotel_booking every ~20s until status is succeeded, failed or attention; all three are final. Copy expected_price (the offer's price), expected_cost, currency and fx_rate from the chosen offer exactly. A USD offer sent without its currency is refused (400 price_mismatch). Guest names, phone and e-mail are checked before anything is held (400 invalid_details). guests needs ONE name per guest in the room, children included — adults first, then children in child_ages order. Do NOT call book_hotel again for a booking whose job is running — poll it; a retry returns the same job (duplicate: true).get_hotel_bookingCollect the result of a booking started with book_hotel. Poll every ~20s. status is in_progress, succeeded, failed or attention; the last three are final — stop polling. - succeeded: confirmation, hotel, room, total_price + currency (what the guest is charged), supplier_paid + supplier_currency, payment_status, refundable, free_cancellation_until, cancellation_ladder and terms. - failed: error, written for the guest. The hold was released; nothing was charged. - attention: error (+ confirmation if known). The outcome could not be settled automatically; the hold is kept (nothing charged) while a person checks with the supplier. Do NOT book again. The guest is e-mailed in every case. Read-only and safe to repeat.cancel_hotel_bookingCancel a hotel booking made by this account and refund the guest. A zero-charge cancellation (a refundable rate before free_cancellation_until) refunds the charge in full; a cancellation that would cost money is refused (409) — the hotel's own ladder is in the booking terms. Takes over a minute; if it times out do NOT assume it failed — re-check before retrying.authenticateExplain how to connect a card so this server can search and book. Nothing is charged to connect — a 0.00 Revolut setup that saves the card so a booking can be charged later. Call with no arguments. It returns the current instructions and add_card_url (https://letsfg.co/connect). A PERSON must approve once in a browser — there is no endpoint that mints a token from card details, so do not ask the user for card numbers and do not try to automate this step. Two ways in: (a) add LetsFG as a connector in an assistant that supports remote MCP servers and approve it, or (b) any OAuth-capable client can register itself — see https://letsfg.co/for-agents, section "Option B". Both land on the same card screen. RETIRED 2026-09-02: the Stripe lanes (setup_url, setup_session_id, payment_method_id, card_token) and every token they issued. Passing them now fails. This does NOT create a Developer API billing account. Do not use connect_payment for this.connect_payment[Developer API only — you almost certainly want `authenticate` instead] Mints a one-time link for connecting a payment method to a PAID prepaid Developer API account. Nothing is charged to connect and card details never touch LetsFG: a PERSON opens the returned connect_url in a browser and saves a card, Revolut Pay or Google Pay there. Do not ask a user for card numbers and do not try to automate that step. Refuses to run unless LETSFG_API_KEY is set, because agents kept calling this and creating billing accounts they did not need. Replaced setup_payment on 2026-09-08, when the Stripe lane was retired.- +2 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kiaaccess MCP
{
"mcpServers": {
"kiaaccess-mcp": {
"command": "npx",
"args": [
"-y",
"kiaaccess-mcp"
],
"env": {
"KIA_USERNAME": "YOUR_KIA_USERNAME_HERE",
"KIA_PASSWORD": "YOUR_KIA_PASSWORD_HERE"
}
}
}
}
LetsFG — Flights & Hotels
{
"mcpServers": {
"letsfg-flights-hotels": {
"command": "npx",
"args": [
"-y",
"letsfg-mcp"
]
}
}
}
Frequently asked questions
Kiaaccess MCP is categorized under Travel & Transportation and uses a local stdio subprocess. LetsFG — Flights & Hotels belongs to Travel & Transportation and uses a local stdio subprocess. Pick Kiaaccess MCP for travel & transportation work and LetsFG — Flights & Hotels for travel & transportation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Kiaaccess MCP is listed as free. Auth: other. LetsFG — Flights & Hotels has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kiaaccess-mcp and letsfg-flights-hotels as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kiaaccess MCP has a quality signal of 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars. LetsFG — Flights & Hotels has 69/100 (Great) with 2 views, 1 installs and 2,175 GitHub stars.