# Ridekick Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Ridekick

Get written out-the-door prices from nearby dealerships on the car you want.

- Record: https://musedirectory.ai/connector/ridekick
- Category: Shopping & Commerce
- Developer: Ridekick (https://www.ridekick.com/developers/mcp)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 286ms, checked 2026-11-20T13:31:00Z
- Endpoint: https://www.ridekick.com/api/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-17T21:26:26Z)
- Source: Found in the official MCP Registry (com.ridekick/ridekick) https://registry.modelcontextprotocol.io/v0/servers?search=com.ridekick%2Fridekick

Connects to Ridekick to search new and used cars near a ZIP code, compare listings side by side, and send price requests to up to five dealerships. Muse can read written offers, reply to dealers, book a visit, and withdraw a request, with a preview before anything is sent.

Example request: "Find me a used Honda CR-V near 78704 and get out-the-door prices from a few dealerships."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Ridekick to help me. It is a free service with an MCP server at https://www.ridekick.com/api/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- how_ridekick_works: Explains what Ridekick does, what dealerships see, how prices work, what to tell a buyer when Ridekick isn't connected, is disconnected or stops working, and the rules for using Ridekick's tools. It needs no sign-in and reads nothing about the buyer. It answers questions about ho
- requests_list: Shows the buyer's requests, one summary each: the car, where it stands (`section`: `ready`, `in_progress` or `inactive`) and, once a dealership has put its price in writing, the lowest offer so far. A request has an offer when `lowestWrittenOtdCents` is set, in any section. When 
- requests_get: Shows one request in full: each dealership's out-the-door price and its state. A row whose state is "written" is an offer: the dealership's price in writing. A row whose state is "waiting" is not in writing yet. A row in any other state is not an offer. It takes an id from `reque
- requests_preview: Shows what `requests_submit` would do, and contacts no dealership. It also shows what a new-car request would do, after `see_car_choices`. It returns the request as given, what happens next, and a `previewToken` that works for 15 minutes, for this exact request and `idempotencyKe
- requests_submit: A sent request contacts real dealerships, by email, by text or through the dealership's own contact form, and cannot be undone. On a practice account it contacts only Ridekick's test dealerships, never a real one. The preview says when a request goes to Ridekick's test dealership
- get_offer_sheet: Shows the price in writing from ONE dealership the buyer can see on Ridekick: the out-the-door total and, when the dealership itemized it, the vehicle price, sales tax and fees, in whole cents, with the date the dealership wrote it (`asOf`). When the dealership broke the price ou
- access_get: Shows what THIS connection may do for the buyer and, if it can send requests to dealerships, its own daily limit and how much of it is used today (a class or client limit may refuse sooner). It needs no extra permission and shows nothing about dealerships or prices. It also names
- see_car_choices: Shows the model years and the trim levels Ridekick lists for one make and model. `year` and `trim` narrow the trims, and `trimsYear` is the model year the trims are for. A new-car ask starts here: a buyer who asks for a new car of a make and model, with or without a model year, a
- see_car_choices_options: The Configure card calls this tool to load the next steps. The assistant does not call it.
- see_cars_near_buyer: Returns up to five cars listed near a ZIP code. It lists cars on a dealership's lot. It answers a buyer who asks to see cars on lots, names a listing, or asks for a used car. A buyer who asks for a new car and has named no listing is a new-car ask, which starts at `see_car_choice
- compare_listings: Puts two or three of the cars that `see_cars_near_buyer` returned side by side. It takes their `handles`. It answers `cars` (each with a short `title`, and `condition`, new or used, when the listing says) and `rows`: year, trim, exterior color, mileage and the listed price, one v
- see_cars_near_buyer_page: The cars card calls this tool to load the next five cars of a search. The assistant does not call it.
- messages_preview: Shows the exact message that `messages_send` would send to one dealership, and sends nothing. It answers with the text as the dealership would get it, how it would be sent (`sms` or `email`), whether it can be sent now, and a `previewToken` that is valid for 15 minutes and only f
- messages_send: Sends the message shown by `messages_preview` to the one dealership on one row of a request. It reaches a real dealership and cannot be undone. It takes the `previewToken` that `messages_preview` returned for the same text, the same row and the same `idempotencyKey`. A call repea
- messages_list: Shows the messages exchanged with one dealership on one row of a request, oldest first, a page at a time. Each message says who wrote it (`dealer`, `buyer`, `assistant` or `ridekick`), when, and by which channel (`sms` or `email`). `buyer` is a message the buyer typed on Ridekick
- show_go_ahead_card: Shows the card where the buyer can go ahead with one car on a request. It is for a buyer who said they want to go ahead with this car. An offer can be read without this card through requests_get. It takes the request's `dealSetId` (`id` in requests_list) and the car's `negotiatio
- commit_confirm: The card's Confirm button calls this tool. The assistant does not call it.
- commit_pick_time: The card's time picker calls this tool. The assistant does not call it.
- commit_handoff: The Commit card calls this tool to read where the dealership hand-off stands after the buyer confirms a choice. The assistant does not call it. It answers one `state`: `held` (the hand-off is waiting and has not gone yet), `sending` (it is on its way), `sent` (the dealership has 
- archive_request: Files one CLOSED request away for the buyer. It takes the `id` of the request. For a request to several dealerships, it also takes the `rowKey` of the one dealership. No dealership is told, and nobody is notified. An open request is not archived. It does nothing else to the reque
- cancel_visit: Cancels the buyer's visit to this dealership. Use it only when the buyer says to. The buyer's go-ahead on this car stays. withdraw is different: it ends the go-ahead, and the visit with it. If the dealership already had the visit, it is told the visit is off (`told: true`). With 
- withdraw: Ends the buyer's go-ahead on this car, and the visit with it if there is one. Use it only when the buyer says to. cancel_visit is different: it ends only the visit and keeps the go-ahead. Going ahead with another car is a separate step. If the dealership already had the go-ahead,
- requests_stop_dealership: Stops one dealership's part of the buyer's request. The dealership is not told, and it gets no more messages from this request. The other dealerships keep going. If it is the last dealership still going, the request ends. Set confirm to true only after the buyer has said which de
- visit_times: Checks a visit time the buyer stated in chat, or lists up to three times the dealership is open. It sends nothing, and it never picks a time: the buyer picks. The buyer must have gone ahead with this car before the time can be sent.
- book_visit: Sends the visit time the buyer confirmed. The dealership gets the buyer's name, phone number and email. It needs the previewToken that visit_times returned, and the same idempotencyKey as that visit_times call. Before the buyer has gone ahead with this car, it answers go_ahead_fi

Screening checks:
- MCP handshake: pass (Answered in 434ms)
- Domain against threat feeds (Cloudflare security DNS): pass (www.ridekick.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (25 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 6661 days ago)
- AI review of purpose and tool behavior: pass (sends real messages to dealerships, gated by preview tokens and buyer consent; dealer-written text is flagged as untrusted input)
