Lockii
Lockii
  • Docs
  • Changelog
  • Feature requests
  • Support portal
    • User MCP
    • Login with Lockii
    • Customer MCP
    • Lockii REST API
    • Booking API
Docs / API & MCP

Customer MCP

We currently support connecting to AI support tools via a customer specific MCP

Overview

The Customer MCP (Model Context Protocol) server enables customer-facing tools and support systems to access booking and inventory data. It also provides tools for customer support workflows.

This MCP is for direct integration with customer-facing tools and has limited access. It includes tools designed for customer support operations, not a general-purpose MCP. Let us know if this is something you want.

Finding Your MCP URL

  1. Navigate to Settings → Integrations → Customer Support

  2. Click "View MCP Details"

  3. Copy your MCP Server URL

Your MCP URL follows this format:

https://[your-api-url]/mcp/customer?companyId=[your-company-id]

Connecting Your MCP Client

  1. Configure your MCP client (e.g., Claude Desktop, Cline, etc.)

  2. Add the MCP server using the URL from your settings

  3. The server will be available for use

Available Tools

1. Get Inventory (get_inventory)

Retrieves all public products with their available locations.

Description: Returns a list of all public, non-archived products with the locations where they are available. Note: This does not show real-time availability, only which locations stock each product.

Parameters: None

Returns:

{
  "products": [
    {
      "id": "product_123",
      "name": "Product Name",
      "description": "Product description",
      "category": "Category Name",
      "locations": [
        {
          "id": "location_456",
          "name": "Location Name"
        }
      ]
    }
  ]
}

Use Cases:

  • Help customers find products

  • Check which locations carry specific items

  • Provide product information during support calls

2. Get Booking by Details (get_booking_by_details)

Retrieves booking information using customer last name and booking number.

Description: Returns booking details including links to confirmation, return, and extend pages. Useful for redirecting customers to complete their requests.

Parameters:

  • lastName (string, required): Customer's last name

  • bookingNumber (number, required): The booking/order number

Returns:

{
  "id": "booking_private_id",
  "number": 12345,
  "status": "confirmed",
  "priceInCents": 10000,
  "startHireDate": 1234567890,
  "endHireDate": 1234567890,
  "product": {
    "name": "Product Name"
  },
  "location": {
    "name": "Location Name"
  },
  "confirmationPageLink": "https://...",
  "extendBookingPageLink": "https://..."
}

Use Cases:

  • Look up bookings when customers call

  • Provide booking details and status

  • Direct customers to confirmation or extension pages

  • Verify booking information

Error Handling:

  • Returns an error if no booking matches the provided details

  • Last name matching is case-insensitive

3. Send Booking Lookup Email (send_booking_lookup_email)

Sends a booking lookup email to a customer when they can't provide booking details.

Description: Sends the standard "can't find booking" email to a customer's email address. This is used when the customer doesn't have their booking details or can't provide accurate enough information to retrieve their booking.

Parameters:

  • email (string, required): Customer's email address (must be a valid email format)

Returns:

{
  "success": true,
  "message": "If there's an email address associated with this company, you'll receive an email with your order details."
}

Use Cases:

  • Help customers who lost their booking confirmation

  • Provide booking information via email

  • Support customers who can't remember their booking number

Security Notes:

  • Always returns a success message (does not reveal whether the email exists)

  • Only sends email if a matching customer and order are found

  • Email errors are not exposed to the client

Example Workflows

Workflow 1: Customer Can't Find Their Booking

  1. Customer calls support without booking details

  2. AI uses send_booking_lookup_email with the customer's email

  3. Customer receives an email with their booking information

Workflow 2: Customer Wants to Extend Booking

  1. Customer provides last name and booking number

  2. Use get_booking_by_details to retrieve booking information

  3. AI provides the extendBookingPageLink to the customer

  4. Customer can extend their booking directly

Workflow 3: Customer Asks About Product Availability

  1. Customer asks about a product

  2. Use get_inventory to find products and locations

  3. AI provide information about which locations carry the product

  4. Note: This shows locations, not real-time availability

Error Handling

All tools return errors in a consistent format:

{
  "error": "Error type",
  "message": "Human-readable error message"
}

Security & Privacy

  • This MCP can safely be publicly exposed to AI & customer facing tools without risking security.

  • No privileged customer information is available without customer details

  • The MCP only accesses data for your specific company

  • Customer email lookups always return success (doesn't reveal if email exists)

  • All data access is scoped to your company ID

  • No sensitive customer data is exposed beyond what's necessary for support

Future Enhancements

We are expanding the Customer MCP with:

  • Additional customer support tools

  • Enhanced booking management capabilities

  • More detailed inventory information

  • Additional integration options

Check back regularly for updates as we continue to improve the Customer MCP.

PrevLogin with Lockii
NextLockii REST API
Was this helpful?