ENDPOINT 1
https://taskman.london/mcp
MCP server metadata
- Name
- TaskMan of London
- Version
- 1.0.0
Known tools 20
find_servicesUse when the user needs help identifying which TaskMan of London service fits their job, especially for vague home-service requests in London.
Inferred read-onlycheck_service_areaUse when the user provides a London postcode or asks whether TaskMan covers their area.
Inferred read-onlyget_quote_estimateUse when the user asks about likely cost, ballpark pricing, or whether a task needs a custom quote.
Inferred read-onlycheck_availabilityUse when the user asks about dates, timing, or whether a service can likely be booked soon.
Inferred read-onlymatch_providersUse when an agent needs a single deterministic provider-matching result for assignment.
Inferred read-onlycreate_booking_requestUse when the user is ready to submit details for a real TaskMan of London booking request.
Inferred read-onlyget_booking_statusUse when the user already has a TaskMan booking request and wants an update.
Potential side effectsstart_trusted_phone_sessionUse 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.
Inferred read-onlystart_customer_verificationUse when an existing customer wants to verify identity (OTP or magic link) before assistant-led booking.
Inferred read-onlyverify_customer_otpUse after sending an OTP challenge, to verify the one-time passcode and open a short-lived booking session.
Inferred read-onlyverify_magic_link_tokenUse when the customer clicks a magic link and provides the token for verification.
Inferred read-onlyget_customer_profileUse after verification to load scoped customer profile details from CRM for booking.
Inferred read-onlylist_customer_addressesUse after verification to list saved addresses linked to the verified customer.
Inferred read-onlylist_service_typesUse after verification to show supported service types before collecting booking details.
Inferred read-onlyget_customer_availabilityUse after verification to check availability for a verified customer at a selected saved address.
Inferred read-onlystart_booking_paymentUse after collecting booking details to create a Stripe checkout payment session before final booking submission.
Potential side effectsget_booking_payment_statusUse to check whether a booking payment session is pending, paid, failed, canceled, or expired before attempting booking creation.
Potential side effectscreate_customer_bookingUse after verification, detail collection, and confirmed paid payment session to create a booking scoped to the verified customer.
Potential side effectsupdate_contact_noteUse to append an internal CRM note for the verified customer during or after booking.
Inferred read-onlytag_contactUse to add CRM tags to the verified customer for booking workflow tracking.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.taskman-of-london]
url = "https://taskman.london/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"taskman-of-london": {
"type": "http",
"url": "https://taskman.london/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: taskman-of-london
Remote MCP URL: https://taskman.london/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"taskman-of-london": {
"url": "https://taskman.london/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"taskman-of-london": {
"type": "http",
"url": "https://taskman.london/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "taskman-of-london",
"transport": "streamable-http",
"url": "https://taskman.london/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.