mcp server
TaskMan of London
Book London furniture assembly, wall mounting, handyman, electrical, and smart home jobs.
Description as published by the maintainer. Source
- version 1.0.0
- slowing
slowing — Registry entry last updated 2026-03-31.
What this server can do
20 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
check_availability(postcode, service_type, preferred_date, time_preference)- Use when the user asks about dates, timing, or whether a service can likely be booked soon. Required: service_type, postcode.
check_service_area(postcode, service_type)- Use when the user provides a London postcode or asks whether TaskMan covers their area. Required: postcode.
create_booking_request(email, phone, source, postcode, photos_url, service_type, task_summary, customer_name, preferred_date, idempotency_key, time_preference, consent_to_contact)- Use when the user is ready to submit details for a real TaskMan of London booking request. Required: customer_name, phone, postcode, service_type, task_summary, consent_to_contact.
create_customer_booking(address_id, contact_id, photos_url, service_type, task_summary, session_token, preferred_date, idempotency_key, time_preference, consent_to_contact, payment_session_id)- Use after verification, detail collection, and confirmed paid payment session to create a booking scoped to the verified customer. Required: session_token, service_type, task_summary, payment_session_id.
find_services(area, query, urgency)- Use when the user needs help identifying which TaskMan of London service fits their job, especially for vague home-service requests in London.
get_booking_payment_status(session_token, payment_session_id)- Use to check whether a booking payment session is pending, paid, failed, canceled, or expired before attempting booking creation. Required: session_token, payment_session_id.
get_booking_status(email, phone, booking_request_id)- Use when the user already has a TaskMan booking request and wants an update. Required: booking_request_id.
get_customer_availability(address_id, service_type, session_token, preferred_date, time_preference)- Use after verification to check availability for a verified customer at a selected saved address. Required: session_token, service_type.
get_customer_profile(session_token)- Use after verification to load scoped customer profile details from CRM for booking. Required: session_token.
get_quote_estimate(brand, postcode, item_type, wall_type, item_count, service_type, task_summary, preferred_date, photos_provided)- Use when the user asks about likely cost, ballpark pricing, or whether a task needs a custom quote. Required: service_type, task_summary.
list_customer_addresses(session_token)- Use after verification to list saved addresses linked to the verified customer. Required: session_token.
list_service_types(session_token)- Use after verification to show supported service types before collecting booking details. Required: session_token.
match_providers(urgency, location_id, service_type, area_postcode, preferred_date)- Use when an agent needs a single deterministic provider-matching result for assignment. Returns an ordered_candidates array sorted best-to-worst, where the first can_assign=true candidate is the assignee. Required: service_type, area_postcode, urgency.
start_booking_payment(address_id, contact_id, service_type, task_summary, session_token, preferred_date, deposit_amount_minor)- Use after collecting booking details to create a Stripe checkout payment session before final booking submission. Required: session_token, service_type, task_summary.
start_customer_verification(identifier, method_preference, channel_preference)- Use when an existing customer wants to verify identity (OTP or magic link) before assistant-led booking. Required: identifier.
start_trusted_phone_session(identifier)- Use in trusted telephony flows when the caller number is already verified by the channel provider and you need a short-lived booking session without OTP. Required: identifier.
tag_contact(tags, session_token)- Use to add CRM tags to the verified customer for booking workflow tracking. Required: session_token, tags.
update_contact_note(note, session_token)- Use to append an internal CRM note for the verified customer during or after booking. Required: session_token, note.
verify_customer_otp(otp_code, challenge_id)- Use after sending an OTP challenge, to verify the one-time passcode and open a short-lived booking session. Required: challenge_id, otp_code.
verify_magic_link_token(token)- Use when the customer clicks a magic link and provides the token for verification. Required: token.
Last successful function declaration observed on . Source: https://taskman.london/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://taskman.london/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-03-31 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-03-31 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 20 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | taskman.london | |
| mcp endpoint status | ok | The server listed 20 functions when asked. | as of probe | taskman.london |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json