Server Details
Booking-focused MCP server for real home services in Greater London, including furniture assembly, wall mounting, handyman, electrical, and smart home jobs.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
20 toolscheck_availabilityInspect
Use when the user asks about dates, timing, or whether a service can likely be booked soon.
| Name | Required | Description | Default |
|---|---|---|---|
| postcode | Yes | ||
| service_type | Yes | ||
| preferred_date | No | ||
| time_preference | No |
check_service_areaInspect
Use when the user provides a London postcode or asks whether TaskMan covers their area.
| Name | Required | Description | Default |
|---|---|---|---|
| postcode | Yes | ||
| service_type | No |
create_booking_requestInspect
Use when the user is ready to submit details for a real TaskMan of London booking request.
| Name | Required | Description | Default |
|---|---|---|---|
| No | |||
| phone | Yes | ||
| source | No | chatgpt_app | |
| postcode | Yes | ||
| photos_url | No | ||
| service_type | Yes | ||
| task_summary | Yes | ||
| customer_name | Yes | ||
| preferred_date | No | ||
| idempotency_key | No | ||
| time_preference | No | ||
| consent_to_contact | Yes |
create_customer_bookingInspect
Use after verification, detail collection, and confirmed paid payment session to create a booking scoped to the verified customer.
| Name | Required | Description | Default |
|---|---|---|---|
| address_id | No | ||
| contact_id | No | ||
| photos_url | No | ||
| service_type | Yes | ||
| task_summary | Yes | ||
| session_token | Yes | ||
| preferred_date | No | ||
| idempotency_key | No | ||
| time_preference | No | ||
| consent_to_contact | No | ||
| payment_session_id | Yes |
find_servicesInspect
Use when the user needs help identifying which TaskMan of London service fits their job, especially for vague home-service requests in London.
| Name | Required | Description | Default |
|---|---|---|---|
| area | No | ||
| query | No | ||
| urgency | No |
get_booking_payment_statusInspect
Use to check whether a booking payment session is pending, paid, failed, canceled, or expired before attempting booking creation.
| Name | Required | Description | Default |
|---|---|---|---|
| session_token | Yes | ||
| payment_session_id | Yes |
get_booking_statusInspect
Use when the user already has a TaskMan booking request and wants an update.
| Name | Required | Description | Default |
|---|---|---|---|
| No | |||
| phone | No | ||
| booking_request_id | Yes |
get_customer_availabilityInspect
Use after verification to check availability for a verified customer at a selected saved address.
| Name | Required | Description | Default |
|---|---|---|---|
| address_id | No | ||
| service_type | Yes | ||
| session_token | Yes | ||
| preferred_date | No | ||
| time_preference | No |
get_customer_profileInspect
Use after verification to load scoped customer profile details from CRM for booking.
| Name | Required | Description | Default |
|---|---|---|---|
| session_token | Yes |
get_quote_estimateInspect
Use when the user asks about likely cost, ballpark pricing, or whether a task needs a custom quote.
| Name | Required | Description | Default |
|---|---|---|---|
| brand | No | ||
| postcode | No | ||
| item_type | No | ||
| wall_type | No | ||
| item_count | No | ||
| service_type | Yes | ||
| task_summary | Yes | ||
| preferred_date | No | ||
| photos_provided | No |
list_customer_addressesInspect
Use after verification to list saved addresses linked to the verified customer.
| Name | Required | Description | Default |
|---|---|---|---|
| session_token | Yes |
list_service_typesInspect
Use after verification to show supported service types before collecting booking details.
| Name | Required | Description | Default |
|---|---|---|---|
| session_token | Yes |
match_providersInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| urgency | Yes | ||
| location_id | No | ||
| service_type | Yes | ||
| area_postcode | Yes | ||
| preferred_date | No |
start_booking_paymentInspect
Use after collecting booking details to create a Stripe checkout payment session before final booking submission.
| Name | Required | Description | Default |
|---|---|---|---|
| address_id | No | ||
| contact_id | No | ||
| service_type | Yes | ||
| task_summary | Yes | ||
| session_token | Yes | ||
| preferred_date | No | ||
| deposit_amount_minor | No |
start_customer_verificationInspect
Use when an existing customer wants to verify identity (OTP or magic link) before assistant-led booking.
| Name | Required | Description | Default |
|---|---|---|---|
| identifier | Yes | ||
| method_preference | No | auto | |
| channel_preference | No | auto |
start_trusted_phone_sessionInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| identifier | Yes |
tag_contactInspect
Use to add CRM tags to the verified customer for booking workflow tracking.
| Name | Required | Description | Default |
|---|---|---|---|
| tags | Yes | ||
| session_token | Yes |
update_contact_noteInspect
Use to append an internal CRM note for the verified customer during or after booking.
| Name | Required | Description | Default |
|---|---|---|---|
| note | Yes | ||
| session_token | Yes |
verify_customer_otpInspect
Use after sending an OTP challenge, to verify the one-time passcode and open a short-lived booking session.
| Name | Required | Description | Default |
|---|---|---|---|
| otp_code | Yes | ||
| challenge_id | Yes |
verify_magic_link_tokenInspect
Use when the customer clicks a magic link and provides the token for verification.
| Name | Required | Description | Default |
|---|---|---|---|
| token | Yes |
Verify Ownership
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [
{
"email": "your-email@example.com"
}
]
}The email address must match the email associated with your Glama account. Once verified, the connector will appear as claimed by you.
Last verification attempt failed.
Failed to fetch .well-known/glama.json: HTTP 403
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!