your business · inside claude and chatgpt

Ask an assistant to book something with your business.
Today it cannot.

yesmcp builds and runs the connector that lets your customers book, order and get answers from your business right inside Claude or ChatGPT. Like the one in this chat: it is real, and you can try it.

demo: one link, any claude plan, free included · map: free, before any contract

built and run bySerhii Kravchenko

what can yesmcp actually do for a shop like mine?
▸ yesmcp · showing services
Here's what they do. Pick a card to go deeper:
yesmcp
⚒

A connector, done for you

Fixed-scope build: from the first call to live tools in your customers' chat.

☁

Hosting & monitoring

Managed infrastructure, watched by us: logs, errors, misfired conversations.

🛡

Security by default

Read and write tools separated, write actions confirmed, scoped credentials.

🗝

Yours to keep

The connector spec and code belong to you. Self-host at any point.

our own connector, live in production. the in-chat cards are our work too, yours will look like this · try it live

claude.ailive · all planschatgptvia plugin directory reviewle chatlive · free tierperplexitypro plansgeminilimited preview

availability differs per platform and changes fast, and we track it so you don't have to · last checked 9 Sep 2026

why now

A website in 1998. An app in 2008. A place in AI chats in 2026.

1,000,000,000

people talk to ChatGPT every week, at the very least · OpenAI's own number, Aug 2026 · and that is before counting Claude and Gemini

Late in the evening a customer wants to book or move a visit. Today that waits for the morning shift, and some never write back. With a connector, the assistant settles it on the spot, from your own calendar.

Your customers are done opening ten websites; they ask their assistant instead. The connector is built once, on an open standard the assistant makers themselves handed to the neutral Linux Foundation (December 2025). Each assistant has its own install and approval flow, and we handle that per platform.

what we build

We build one thing: the chat layer of your business

Two jobs, one connector: your team stops digging through tabs, and your customers stop waiting for someone to answer.

lingua studio is an invented school · read it as your business

team connector · 09:00, before the first call

The face your team sees

The same connector, behind a login. The picture of the day lives in five tabs. Your team asks for it in the chat they already sit in, and acts on it.

claude.ai · your team's chat

Morning. What's my day?

▸ lingua studio · opening the day

9 lessons. One free window at 14:00, and two trial requests waiting. Offer it to both?

Yes, offer it.

✓ two offers drafted · nothing is sent without your OK

customer connector · 21:00, nobody at the desk

The face your customers see

Booking, orders, status, answers grounded in your data, in your customer's own chat. No app, and for guest scenarios no login at all.

claude.ai · your customer's chat

Can I move tomorrow's lesson to the weekend?

▸ lingua studio · checking the calendar

Saturday 11:00 with Olena K. is free. Move it?

yes

✓ moved · the calendar is already up to date

Shown as text on purpose: this is how the same scenario reads in any assistant. In Claude the connector also draws live cards at the moments that decide a sale. The demo at the top is ours, running right now.

  1. 01 · one call

    You pick the scenarios

  2. 02 · access and one person to ask

    We build against your systems

  3. 03 · nothing on your side

    A link for customers, a login for your team

scenarios

Your front desk and your back office, in the chat

Run a professional practice or an agency? The page for your field →

Your customers · guest · no login

language school

“What's my son's homework for Thursday, and how is he doing?”

→ reads the class journal

Homework, progress notes and what the group covered, read from your class journal rather than a group-chat scroll.

Google SheetsGoogle Calendar

accounting firm

“What do you still need from me for the quarterly filing?”

→ builds your checklist

A list built from your own records: which documents are already in, which are missing, and a secure link to upload the rest.

QuickBooksGoogle Drive

online shop

“Where is my order?”

→ checks the order

A customer who ordered in the chat asks in the same chat: a live answer from your system's data instead of a support ticket.

ShopifyWooCommerce

one connector · two sides

Your team · signed in

Every tool below ships its own single-tool connector. Our work is the system: all of them, plus your custom software, wired into one place under your rules.

HubSpotJiraQuickBooksGoogle CalendarZendesk{ } your custom systemsone connector

clinic front desk

“Who's coming at 11:00, and where did we leave off?”

→ reads the schedule and visit notes

Today's schedule plus the client's history, read from your systems before the person walks in.

Google Calendar{ } your clinic system

agency partner

“What needs attention this week?”

→ reads CRM, tracker and books

Stale proposals, unbilled work and overdue invoices in one answer instead of three tabs.

HubSpotJiraQuickBooks

any team

“Ihor paid in cash. Log it and book his next visit.”

→ logs the payment, books the visit

Write actions run behind a login and are confirmed before they fire: sanctioned, scoped, auditable.

QuickBooksGoogle Calendar

your business

“Can my customers and my team do this in a chat too?”

Almost any system can be connected. The scenario map is the fastest way to see yours.

{ } your own system

Everything above is what a connector can do. Everything below is what ours already does.

proof you can check

Don't take our word for it. It's running right now.

live in claude.ai

8 tools serving customers

every answer traced to your own data

the engineer

Serhii Kravchenko · AI engineer, founder

Every scenario here is designed, tested and run by the person you will actually talk to. You work with the builder, not an account manager.

The routine is run by a team of AI agents Serhii built, which is why your connector is watched every day, weekends included.

more about Serhii →

check us in one minute

Open our connector in your Claude and book a call inside the chat: the same experience your customers would get.

Open our connector in Claude →

one link · any claude plan, free included

case №1 · ourselves

We are our own first client

Scoping calls for yesmcp have been booked, moved and cancelled through this same connector since 21 August 2026. The chat is one of three doors onto the same calendar.

every week our agents count the claude connector directory: read the census →·open dataset, CC BY 4.0

before you write

Fair questions

Couldn't my own developer build this?

He will. The question is not who writes the server: it is who decides which five of your customers' questions belong in a chat, where the line sits that the assistant may never cross, and who is watching on Friday evening when a scenario starts answering wrongly. We work with your developers on exactly that.

How do my customers actually get the connector?

Today: a one-link install page. A customer adds your connector to Claude in under a minute, on any plan. In ChatGPT the path is the official app directory: OpenAI reviews every submission, and when you want a place there, we prepare and shepherd your submission through that review. We tell you exactly what works today versus what is pending review.

What about our data and security?

Your data stays in your systems: the connector reads them with scoped credentials and never with direct database access. Read and write are separated, and irreversible actions ask for confirmation before they fire. A guest booking stores a name and an email, and that is all; when a scenario truly needs identity, we build it on OAuth 2.1 and run that in production too. And we attack our own server with forged headers and hostile payloads before anyone else gets the chance.

What does it cost, and why is there no price here?

Because every connector is scoped to one business, and a number without that scope would be a guess. The diagnosis is free, and you leave that free step with a number for your case. Two commitments stand in for a price list: if the first scenario turns out to be the wrong one, we build the next one from your map at no extra cost; and against a system with an API, the first scenario takes about two weeks.

Will I be locked into you?

No. The spec and code belong to you from day one, and you can move the connector to your own servers whenever you choose. Clients stay for the work.

next step

say yes.

Tell us what your business does. One call is enough for us to propose connector scenarios and an exact quote.

Pick a time for the call →

Prefer chat? Book a personal call with Serhii on Telegram

Not ready to talk? Start with the scenario map: pick your business, answer two questions, see your own scenarios.

Prefer email? yes@yesmcp.com