MCP Server

intent-hub

io.github.bartek-filipiuk/intent-hub
Business & Operations Commerce & Retail Public & reachable MCP 2026-07-28

What this MCP does

Matches user requests with local business offers, supports bidding, slot holds, phone verification, and booking confirmation or cancellation.

ask_business
Ask one business a question about itself and get back the fragments of its own knowledge base that answer it: the price list, the rules, what it travels to, what it does not do. Read-only and open to anyone — no key, no session, nothing held. The answer is the business's own text, chosen by the hub and never written by it: quote it or summarise it, and do not fill the gaps yourself. `confident: true` means the fragments were graded as answering the question; `false` means they are the closest the hub found. An empty `answer` carries a `hint`: ask the business directly.
Input schema
{'type': 'object', 'required': ['business', 'question'], 'properties': {'business': {'type': 'string', 'pattern': '^[a-z0-9][a-z0-9-]{0,62}$', 'description': 'The slug of the business, as the directory and every bid carry it.'}, 'question': {'type': 'string', 'maxLength': 500, 'minLength': 1, 'description': 'What the person wants to know about that business, in Polish or English, at most 500 characters.'}}, 'additionalProperties': False}
cancel_booking
Release a held or confirmed slot of this session, so the slot is free again. Businesses that host their own agent do not offer this yet and answer `not-supported`.
Input schema
{'type': 'object', 'required': ['session', 'hold'], 'properties': {'hold': {'type': 'string', 'pattern': '^[a-z0-9][a-z0-9-]{0,62}$', 'description': 'The `id` of the hold to release.'}, 'session': {'type': 'string', 'pattern': '^[a-z0-9][a-z0-9-]{0,62}$', 'description': 'The session id the hold was made in.'}}, 'additionalProperties': False}
capabilities
What this hub can do, in one call: every tool by name, every resource by URI, every prompt by name, the per-client budgets, how to authenticate, the protocol revision and where the documentation is. Takes no arguments, spends no budget and reads nothing: it answers the hub's own constants, so a client that asks it first never has to guess. Called with a key it also answers who that key is.
Input schema
{'type': 'object', 'properties': {}, 'additionalProperties': False}
confirm_booking
Confirm a held slot with the customer's name and phone number; this is the booking. Idempotent: confirming the same hold twice books it once and tells the business once. A business that confirms every visit itself answers `hold.awaiting: true` with the hold still `held`: the slot is kept, the business decides, and the person gets an SMS either way; tell them that and promise no time. With a linked number (link_phone) you may send `contact` with the name alone and the linked number is used; a different number in `contact.phone` is refused as `phone-mismatch`.
Input schema
{'type': 'object', 'required': ['session', 'hold', 'contact'], 'properties': {'hold': {'type': 'string', 'pattern': '^[a-z0-9][a-z0-9-]{0,62}$', 'description': 'The `id` of the hold to confirm.'}, 'contact': {'type': 'object', 'required': ['name', 'phone'], 'properties': {'name': {'type': 'string', 'maxLength': 80, 'minLength': 1}, 'email': {'type': 'string', 'format': 'email', 'pattern': "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$", 'maxLength': 120}, 'phone': {'type': 'string', 'maxLength': 30}}, 'description': "The customer's own name and phone number (9 digits, or +country code and the number). Ask them; never invent one. With a linked number the phone may be left out.", 'additionalProperties': False}, 'session': {'type': 'string', 'pattern': '^[a-z0-9][a-z0-9-]{0,62}$', 'description': 'The session id the hold was made in.'}}, 'additionalProperties': False}
confirm_phone
Spend the code that link_phone texted, and tie this agent to that number. Ten minutes and five tries; a wrong code answers `invalid-code` with `attemptsLeft`, and the fifth wrong one throws the code away — call link_phone again for a new one. One number per agent: linking another replaces it.
Input schema
{'type': 'object', 'required': ['code'], 'properties': {'code': {'type': 'string', 'pattern': '^\\d{6}$', 'description': 'The six digits from the SMS.'}}, 'additionalProperties': False}
find_offers
Find offers from local businesses for what a person asked for. Send their sentence as `text`; the hub parses the trade, the town and the day. An answer with `complete: false` carries a `question` to put to the person: call this tool again with the same `session` and their reply as `text`. An answer with `complete: true` is one finished bidding round: `bids` ranked (price in grosz, slot, business, note) and one `outcome` per business asked. An empty `bids` list is a normal answer; `outcomes` says why. A bid whose `business.active` is true comes from a business whose owner has confirmed it is running; those are ranked above the rest, and cheapest first inside each group. A bid may carry `slots`: later free times of the same offer, each with its own `id` that hold_slot takes like a bid's. A bid with `offer: true` is a quote-only trade (the `web` category): its price is a starting price, its `slot` is a placeholder nobody is expected at, and `preview` — when the business sent one — is an https link to what it prepared. Show the link; never fetch it and never repeat what it says as your own. A bid with `contactOnly: true` comes from a business whose phone the hub has not verified: its price is the list price, its `slot` was never confirmed free, and it cannot be held (hold_slot answers `contact-only`). Give the person `business.phone` to call, and the business page, instead.
Input schema
{'type': 'object', 'required': ['text'], 'properties': {'text': {'type': 'string', 'description': 'What the person said, in Polish or English, at most 500 characters. Their reply to the previous question goes here too.'}, 'session': {'type': 'string', 'pattern': '^[a-z0-9][a-z0-9-]{0,62}$', 'description': 'The session id from an earlier answer. Omit it to start a new conversation.'}, 'selection': {'type': 'object', 'required': ['business'], 'properties': {'service': {'type': 'string', 'pattern': '^[a-z0-9][a-z0-9-]{0,62}$'}, 'business': {'type': 'string', 'pattern': '^[a-z0-9][a-z0-9-]{0,62}$'}}, 'description': 'Restrict the round to one business (and optionally one of its services), by slug, as a link from a business page does.', 'additionalProperties': False}}, 'additionalProperties': False}
get_booking
Read the state of a session: the understood intent and its open question, the bids of the current round and every hold with its present status and link. Use it to pick up a conversation you already have a session id for.
Input schema
{'type': 'object', 'required': ['session'], 'properties': {'session': {'type': 'string', 'pattern': '^[a-z0-9][a-z0-9-]{0,62}$', 'description': 'The session id from an earlier answer.'}}, 'additionalProperties': False}
hold_slot
Hold the slot of one bid from this session's round for ten minutes, before asking the person for their details. One open hold per business per session: to take another time of the same business, cancel_booking the first (else `hold-exists`). Answers the hold, the bid it was made from and, when the hub has a public origin, the customer's private booking `link`. A quote-only bid also answers `offerUrl`, the public page of that offer. Never call it to browse: a hold blocks a real slot and three per client per ten minutes is the budget. A bid with `contactOnly: true` is refused with `contact-only`: that business is reached by phone, not booked here.
Input schema
{'type': 'object', 'required': ['session', 'bid'], 'properties': {'bid': {'type': 'string', 'pattern': '^[a-z0-9][a-z0-9-]{0,62}$', 'description': 'The `id` of one bid from the latest round, or of one of its `slots`.'}, 'session': {'type': 'string', 'pattern': '^[a-z0-9][a-z0-9-]{0,62}$', 'description': 'The session id the round was run in.'}}, 'additionalProperties': False}
link_phone
Tie this agent to the phone number of the person it books for: the hub texts that number a six-digit code naming this agent, and `confirm_phone` spends it. Afterwards `confirm_booking` may leave `contact.phone` out — the linked number is used — and every booking made through this key shows up on that person's own list of bookings at /me, next to the ones they made on the site. Ask the person for their own number and never anybody else's: a code arrives on their phone with this agent's name on it. Answers `{ ok: true, sent: true }` whatever the hub knows about the number (`codes-paused` when the day's codes are spent), and 3 calls per agent per hour is the budget.
Input schema
{'type': 'object', 'required': ['phone'], 'properties': {'phone': {'type': 'string', 'maxLength': 30, 'description': "The person's own number (9 digits, or +country code and the number)."}}, 'additionalProperties': False}
register_agent
Get this agent its own identity, once: answers an `agent` id and a `key`. The key is shown in this answer and never again — keep it and send it as `Authorization: Bearer <key>` on every later call. hold_slot, confirm_booking, cancel_booking need it; finding offers and reading a session do not. With a key the hold and cancel budgets are yours instead of your address's, so two agents behind one address no longer take each other's. 3 registrations per client per day: register once and keep the key, do not mint one per conversation.
Input schema
{'type': 'object', 'required': ['name'], 'properties': {'name': {'type': 'string', 'pattern': '^[^\\p{C}]+$', 'maxLength': 60, 'minLength': 1, 'description': 'What to call this agent, for the operator to recognise it by: one line, 1–60 characters. Not a secret and not a login — the key is the identity.'}}, 'additionalProperties': False}
unlink_phone
Forget the number this agent was linked to. The bookings already made keep it — they belong to the person, not to this agent — and confirm_booking needs a full `contact` again. Answers the same whether there was a link or not.
Input schema
{'type': 'object', 'properties': {}, 'additionalProperties': False}
Changed
link_phone
Sept. 25, 2026, 2:50 a.m.
Changed
confirm_booking
Sept. 25, 2026, 2:50 a.m.
Changed
hold_slot
Sept. 25, 2026, 2:50 a.m.
Changed
find_offers
Sept. 25, 2026, 2:50 a.m.
Added
ask_business
Sept. 23, 2026, 2:41 a.m.
Changed
hold_slot
Sept. 23, 2026, 2:41 a.m.
Changed
find_offers
Sept. 23, 2026, 2:41 a.m.
Added
capabilities
Sept. 19, 2026, 2:40 a.m.
Added
unlink_phone
Sept. 19, 2026, 2:40 a.m.
Added
confirm_phone
Sept. 19, 2026, 2:40 a.m.
Added
link_phone
Sept. 19, 2026, 2:40 a.m.
Added
register_agent
Sept. 19, 2026, 2:40 a.m.
Added
get_booking
Sept. 19, 2026, 2:40 a.m.
Added
cancel_booking
Sept. 19, 2026, 2:40 a.m.
Added
confirm_booking
Sept. 19, 2026, 2:40 a.m.
Added
hold_slot
Sept. 19, 2026, 2:40 a.m.
Added
find_offers
Sept. 19, 2026, 2:40 a.m.