# Taskman Home Services MCP server

Source: https://glimind.com/server/mcp-registry%2Flondon.taskman%2Fhome-services
Registry id: `mcp-registry/london.taskman/home-services`
Status: live (checked 2026-10-27T01:48:11.509Z)

## Measurements (30 days)

- Uptime: 99.97%
- Checks: 4971
- Outages (90 days): 18

## Install

```json
{
  "mcpServers": {
    "taskman-home-services-mcp-server": {
      "type": "http",
      "url": "https://taskman.london/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http taskman-home-services-mcp-server https://taskman.london/mcp
```

## Tools (20)

- `check_availability`: Use when the user asks about dates, timing, or whether a service can likely be booked soon.
- `check_service_area`: Use when the user provides a London postcode or asks whether TaskMan covers their area.
- `create_booking_request`: Use when the user is ready to submit details for a real TaskMan of London booking request.
- `create_customer_booking`: Use after verification, detail collection, and confirmed paid payment session to create a booking scoped to the verified customer.
- `find_services`: 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`: Use to check whether a booking payment session is pending, paid, failed, canceled, or expired before attempting booking creation.
- `get_booking_status`: Use when the user already has a TaskMan booking request and wants an update.
- `get_customer_availability`: Use after verification to check availability for a verified customer at a selected saved address.
- `get_customer_profile`: Use after verification to load scoped customer profile details from CRM for booking.
- `get_quote_estimate`: Use when the user asks about likely cost, ballpark pricing, or whether a task needs a custom quote.
- `list_customer_addresses`: Use after verification to list saved addresses linked to the verified customer.
- `list_service_types`: Use after verification to show supported service types before collecting booking details.
- `match_providers`: Use when an agent needs a single deterministic provider-matching result for assignment. Returns an ordered_candidates array sorted best-to-worst, where the firs
- `start_booking_payment`: Use after collecting booking details to create a Stripe checkout payment session before final booking submission.
- `start_customer_verification`: Use when an existing customer wants to verify identity (OTP or magic link) before assistant-led booking.
- `start_trusted_phone_session`: 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.
- `tag_contact`: Use to add CRM tags to the verified customer for booking workflow tracking.
- `update_contact_note`: Use to append an internal CRM note for the verified customer during or after booking.
- `verify_customer_otp`: Use after sending an OTP challenge, to verify the one-time passcode and open a short-lived booking session.
- `verify_magic_link_token`: Use when the customer clicks a magic link and provides the token for verification.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.