name: Lightspeed Commerce MCP <-> OpenAPI Tool Crosswalk
generated: '2026-08-27'
method: derived
source: >-
  mcp/lightspeed-x-series-tools-list.json, mcp/lightspeed-k-series-tools-list.json,
  openapi/lightspeed-x-series-openapi.json, openapi/lightspeed-k-series-openapi.json
summary: >-
  Lightspeed's two MCP servers are meta-tools over the specification, not projections of it. Every tool
  operates on the OpenAPI document or the documentation portal; none binds to a business operation. The
  crosswalk is therefore almost entirely mcp_only on one side and rest_only on the other, and that
  asymmetry is the finding: 292 published REST operations (201 X-Series + 91 K-Series) have zero direct
  tool representation.
surfaces:
  openapi:
  - api: lightspeed:retail-x-series
    file: openapi/lightspeed-x-series-openapi.json
    version: '3.0.1'
    operations: 201
    gated: false
  - api: lightspeed:restaurant-k-series
    file: openapi/lightspeed-k-series-openapi.json
    version: '3.1.0'
    operations: 91
    webhooks: 11
    gated: false
  graphql: none
  mcp:
  - endpoint: https://x-series-api.lightspeedhq.com/mcp
    gated: false
  - endpoint: https://api-docs.lsk.lightspeed.app/mcp
    gated: false
crosswalk:
- tool: execute-request
  server: x-series
  category: generic-proxy
  rest: ALL
  binding: proxy
  confidence: high
  note: >-
    Accepts an arbitrary HAR request object, so it can reach any of the 201 X-Series operations, but it
    inherits none of their parameter schemas. An agent must already know the path, method, body shape
    and required OAuth scope; the tool provides no operation-level inputSchema. Recorded as a proxy
    binding rather than 201 separate rows because that is what it actually is.
- tool: get-endpoint
  server: x-series
  category: contract-introspection
  rest: []
  binding: metadata
  confidence: high
  note: Returns the OpenAPI definition of one path+method, including its securitySchemes and servers.
- tool: list-endpoints
  server: x-series
  category: contract-introspection
  rest: []
  binding: metadata
  confidence: high
- tool: search-endpoints
  server: x-series
  category: contract-introspection
  rest: []
  binding: metadata
  confidence: high
- tool: get-server-variables
  server: x-series
  category: contract-introspection
  rest: []
  binding: metadata
  confidence: high
  note: >-
    Materially useful here — the X-Series server URL is templated
    (https://{domain_prefix}.retail.lightspeed.app/api/2026-07) and an agent cannot call the API
    without resolving domain_prefix.
- tool: search
  server: k-series
  category: docs-retrieval
  rest: []
  binding: documentation
  confidence: high
- tool: get_pages
  server: k-series
  category: docs-retrieval
  rest: []
  binding: documentation
  confidence: high
- tool: list_pages
  server: k-series
  category: docs-retrieval
  rest: []
  binding: documentation
  confidence: high
- tool: list_changes
  server: k-series
  category: docs-retrieval
  rest: []
  binding: changelog
  confidence: high
  note: Maps semantically onto the published K-Series changelog at https://api-docs.lsk.lightspeed.app/changes.
- tool: get_change
  server: k-series
  category: docs-retrieval
  rest: []
  binding: changelog
  confidence: high
mcp_only:
- tool: search
  reason: Portal full-text search has no REST equivalent in either product API.
- tool: get_pages
  reason: Documentation content retrieval; not a business operation.
- tool: list_pages
  reason: Portal hierarchy navigation; not a business operation.
- tool: list_changes
  reason: Changelog is published as HTML/portal content, not as a REST collection.
- tool: get_change
  reason: Same as above.
- tool: list-endpoints
  reason: Spec introspection; the OpenAPI document itself is the only "REST" equivalent.
- tool: search-endpoints
  reason: Spec introspection.
- tool: get-endpoint
  reason: Spec introspection.
- tool: get-server-variables
  reason: Spec introspection.
rest_only:
  count: 292
  note: >-
    All 201 X-Series operations and all 91 K-Series operations are rest_only in the strict sense — no
    named MCP tool corresponds to any of them. X-Series operations are reachable indirectly through
    execute-request; K-Series operations are not reachable through MCP at all.
  examples:
  - operationId: ListProducts
    api: lightspeed:retail-x-series
  - operationId: CreateSale
    api: lightspeed:retail-x-series
  - operationId: ListCustomers
    api: lightspeed:retail-x-series
  - operationId: apeLocalOrder
    api: lightspeed:restaurant-k-series
  - operationId: financial-apiGetDailyFinancials
    api: lightspeed:restaurant-k-series
coverage:
  mcp_tools: 10
  tools_bound_to_rest_operations: 0
  tools_proxying_rest_operations: 1
  rest_operations_total: 292
  rest_operations_with_a_named_tool: 0