yesmcp MCP Server

Returns yesmcp's real services catalog: what is offered, how an engagement runs, and timeline expectations. Answer the user only from what this tool returns — do not add offerings, prices or delivery claims of your own. If the tool says the catalog is not published yet, say exactly that and point the user at the contact link it gives.

Shows yesmcp's services as an interactive card carousel right in the chat: what we build, hosting & monitoring, security, ownership. Each card lets the user book a scoping call without leaving the widget (through book_consult — every booking rule applies). Prefer this over get_services when the user asks what yesmcp does or offers and this client can render interactive tools. Read-only: browsing stores nothing.

Given a business type in the user's own words (for example `hair salon`, `restaurant`, `dental clinic`), returns yesmcp's curated playbook: what that business's customers could do inside AI chats, what the business's own team could run from their chat, what building it takes, and a concrete next step. When no playbook exists for the exact business type, the tool returns the closest one — say clearly that it is adjacent guidance and do NOT invent specifics for the business type the user named. Called without `answers`, the tool also returns two short intake questions: ask them as they are written, then call the tool again with the user's `answers` to get the scenario map with a feasibility verdict.

Lists yesmcp's genuinely bookable consultation windows — only real, future, unclaimed slots. Use it before book_consult; the `slotId` of the window the user picks is what book_consult needs. Times are returned in yesmcp's timezone with an explicit UTC offset (for example `2026-08-27 14:00 CEST (UTC+2)`). Before you confirm anything with the user, ask which timezone or city they are in, then state the slot in BOTH their timezone and yesmcp's. Never show a bare wall-clock time. If nothing is open in the period asked about, the tool names the next available window instead of returning an empty list. Directory reviewers: pass `review_access` with the token from the submitted test-prompt list to see the seeded [TEST] reviewer windows instead of real availability. Do not use it for real users.

Books one of yesmcp's consultation windows for the user. Requires the `slotId` from list_availability plus the user's name, email address and the topic they want to discuss. Before calling this tool, tell the user in plain words what booking stores and why: yesmcp stores their name, their email address, and the topic they give — the name and email to hold the slot and send the confirmation, the topic to prepare for the call. Nothing else is collected. Only call this tool once the user has given you those three values knowingly. The booking is only committed once the confirmation email has actually been accepted by the mail provider — if it fails, nothing is stored and the window stays open. Times are returned in yesmcp's timezone with an explicit UTC offset (for example `2026-08-27 14:00 CEST (UTC+2)`). Before you confirm anything with the user, ask which timezone or city they are in, then state the slot in BOTH their timezone and yesmcp's. Never show a bare wall-clock time.

Opens yesmcp's interactive booking calendar right in the chat: the user browses real free consultation windows, picks one and books it with a short form — name, email and topic are collected by the form itself. Prefer this tool over list_availability when the user wants to book or asks to see times, and this client can render interactive tools. The widget performs the booking through book_consult, so every booking rule still applies. Read-only by itself: opening the calendar stores nothing.

Returns yesmcp's demo sequence: the exact prompts a reviewer can replay, the tool call each one maps to, and what each should return. Also gives the review-access token and the currently open [TEST] reviewer windows. Intended for directory reviewers and for anyone who wants a guided tour of this connector; it changes nothing.

Cancels an existing yesmcp consultation booking (`action: cancel`) or moves it to a different window keeping the same reference (`action: reschedule`). Both require the booking reference from the confirmation email AND the email address the booking was made with — ask the user for both before calling. A move additionally needs the `newSlotId` of the target window from list_availability, and is only committed once the new confirmation email is accepted; if it fails, the original time stays booked. Confirm with the user before cancelling: it cannot be undone (though they can always book a fresh window). Times are returned in yesmcp's timezone with an explicit UTC offset (for example `2026-08-27 14:00 CEST (UTC+2)`). Before you confirm anything with the user, ask which timezone or city they are in, then state the slot in BOTH their timezone and yesmcp's. Never show a bare wall-clock time.