For developers · Model Context Protocol

ElloMind booking connector

An MCP server that lets any AI assistant check real availability and book therapy sessions with a Malayalam-speaking psychologist. It is open, stateless, and needs no API key.

Endpoint (Streamable HTTP)

https://mcp.ellomind.com/mcp

← Back to the plain-English guide

Tools

Four tools, in the order an assistant uses them.

list_services

List the session types and prices.

Inputs: None.
Returns: Session types (individual, couples, teen), their price, and the available plan codes.

check_availability

Get real open time slots (IST) for a session type over a date range.

Inputs: session_type, from (YYYY-MM-DD), to (YYYY-MM-DD).
Returns: Each date with its open times.

create_booking_draft

Hold a specific slot and return a single-use payment link to hand the customer.

Inputs: session_type, plan_code, slot_date, slot_time, name, phone, email.
Returns: pay_url, ref, amount_inr, slot, and a poll_key. The price is set by the server; a caller cannot change the amount.

get_booking_status

Read a booking's status and, once confirmed, its Google Meet link.

Inputs: ref, poll_key (both returned by create_booking_draft).
Returns: The booking status, and — only with the correct poll_key — the Meet link and therapist.

Adding it to a client

Claude

Settings → Connectors → Add custom connector → paste the URL and save. Works on free and paid plans.

ChatGPT

Needs a paid plan (Plus and up). Settings → Connectors (Apps) → Advanced → turn on Developer mode → Add custom connector → paste the URL, choose no authentication.

Cursor, Cline, Windsurf, Zed

Add an MCP server entry pointing to the URL, transport Streamable HTTP, no auth header.

Your own client / the SDK

Connect over Streamable HTTP with the @modelcontextprotocol SDK. No auth header is required.

How it stays safe

The assistant orchestrates, but it is never trusted with money, identity, or the meeting link.

The assistant is untrusted

The connector holds a scoped key on the server and calls the booking API itself. The key never reaches the AI or your chat transcript.

Prices are server-set

Amounts are computed from the catalogue. A caller cannot set or lower the price, and a mismatched payment is rejected.

Links are single-use

Each pay link is priced by us, works once, and expires. It carries a 128-bit key, so the Meet link is only released to whoever holds it.

Payment and consent stay human

The connector can hold a slot and mint a link, but it cannot pay or consent. The customer does both, every time.

FAQ

What is the ElloMind MCP connector?

It is a Model Context Protocol server at https://mcp.ellomind.com/mcp that lets any AI assistant check real availability and book a therapy session with a Malayalam-speaking psychologist on ElloMind. It is open, stateless, and needs no API key.

Do I need an API key or account to use it?

No. The endpoint is open and needs no auth header. ElloMind holds a scoped key on the server and calls its own booking API, so the key never reaches the assistant or your chat transcript.

Which MCP clients work with ElloMind?

Any client that speaks MCP over Streamable HTTP: Claude on web and desktop, ChatGPT developer mode, Cursor, Cline, Windsurf, Zed, and your own client built on the @modelcontextprotocol SDK.

Can the assistant change the price or pay on the customer's behalf?

No. Prices are computed on the server from ElloMind's catalogue, and a mismatched payment is rejected. The connector can hold a slot and mint a single-use payment link, but it cannot pay or give consent. The customer does both, every time.

Last updated July 2026.