Chatbot + MCP server

Let your website talk and get things done.

Botito sets up a chat assistant that learns your website and your API. Visitors type or speak to book appointments, place orders and pay. They can also connect their own AI assistants (Claude, ChatGPT…) to your site in one click.

Runs on your own server · Your data stays with you

More than a chat box

The assistant doesn't just talk: it does the things your site does, on the user's behalf, within the limits you set.

💬

An assistant that knows your site

Provide your sitemap and your pages are crawled. It answers questions about prices, hours and policies from your own content and points to the right page.

🛠️

Uses your API

Upload your OpenAPI/Swagger schema and every operation becomes a tool for the assistant. Operations that change data ask the user to confirm first.

🎙️

Voice conversations

Press the microphone and talk. Same tools, same confirmation cards, with a real-time voice assistant.

🔌

Public MCP server

Every site is an MCP server. Users add its address to Claude and sign in with OAuth, with no keys to copy.

👤

Easy customer sign-in

Email and password, Google, or an emailed code. One account in the chat and in their own assistant.

💳

Secure payments

Stripe and iyzico. The customer enters the card on the provider's page; saved cards ask for confirmation. You set the amount, never the assistant.

Live in minutes

Start without writing code; connect your own systems whenever you're ready.

Add your site

Enter a name and address. Multi-tenant by design: every site is separate and isolated.

Give it knowledge

A sitemap, an OpenAPI schema or a ready-made module: any one is enough.

Add one line

Paste the embed code into your site and the chat window is ready.

Share the MCP server

Share your connect page with visitors so they can link their own assistants.

<script src="https://bot.srhtlabs.com/widget.js" data-site="site_abc123" async></script>

No API? Use a ready-made module

Install, configure and go; it all runs inside Botito. Data lives in the dashboard, tools appear in the assistant and in MCP automatically.

📅AppointmentsServices, opening hours, free-slot calculation, rescheduling and cancellation.
👥CRMPeople who leave contact details or ask for a call back merge into one record.
🛍️Catalog & ordersProducts, stock, orders and payment. Bulk product upload from CSV.
🧩Your own APIPresets like Dokploy connect in one step; manage everything through MCP too.
Payments

Even take payments

Let the assistant that took the order finish the payment in the same conversation. Customers pay in your site's chat or in their own AI assistant.

  • Stripe and iyzico. You connect your own account; the money goes straight to you.
  • One confirmation with a saved card. Customers save a card once and only confirm later payments.
  • You set the amount. An order, a deposit or a payment request from your own system; the assistant can't make up an amount.
  • Orders mark themselves "paid". Payment events can also be sent to your own endpoint.

Security by design

An assistant that takes real actions needs clear limits.

  • Write actions need approval. Appointments, orders, payments: nothing runs until the user confirms on the card.
  • OAuth 2.1 + PKCE. Tokens are bound to a single site; admin access is separate and carries its own warning.
  • Encrypted keys. API and payment keys are stored with AES-256-GCM and are never sent back to the dashboard.
  • SSRF protected. The server only calls public addresses; the model can't invent paths or amounts.

Let an agent run Botito too

An assistant connected to the admin MCP creates sites, installs modules, uploads products from CSV, manages appointments and orders and opens payment requests.

"Create a site for Rose Salon and
 install the booking and CRM modules."

"Add the 300 products in this CSV
 to the catalog and update prices."

"List this week's callback
 requests."

Give your site an assistant

Setup takes a few minutes; you create the first account.

Open dashboard