Skip to content

Luckin Coffee

Updated View as Markdown

Official Luckin Coffee store search, drink selection and pickup orders. Creating or cancelling an order requires exact human approval.

Example workflows

Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.

Find Luckin stores

Help me with this task in Luckin Coffee: Find Luckin stores. Ask me for any required inputs and confirm the resources and scope before calling the command. Read one response page. Turn the returned data into a concise working summary with original IDs, dates and source links when available. Separate missing information from confirmed results and tell me whether more pages remain. Do not invent fields or change data.

Explore this command: luckin.shops.list

Find Luckin drinks

Help me with this task in Luckin Coffee: Find Luckin drinks. Ask me for any required inputs and confirm the resources and scope before calling the command. Read one response page. Turn the returned data into a concise working summary with original IDs, dates and source links when available. Separate missing information from confirmed results and tell me whether more pages remain. Do not invent fields or change data.

Explore this command: luckin.products.search

What you can do (8)

What you can do

Available commands: 8 (6 read, 2 write). Enable only the commands your application needs.

Command Effect
Find Luckin stores — luckin.shops.list Read
Find Luckin drinks — luckin.products.search Read
Change drink options — luckin.products.switch Read
Read Luckin drink details — luckin.products.get Read
Preview a Luckin order and discounts — luckin.orders.preview Read
Create a Luckin pickup order — luckin.orders.create Write
Read a Luckin order and pickup code — luckin.orders.get Read
Cancel a Luckin order — luckin.orders.cancel Write

Connect and use

Connect and use

This connection uses your provider account.

Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.

Get your provider credentials

Follow these steps for Luckin Coffee, then enter the issued values in the connection form below.

  1. Get an MCP access token from the official Luckin Coffee open platform and enter it in your connection. Start with a store or product read. Enable read-write access only when you intend to create or cancel an order, and approve the exact order before submission. Provider charges apply.

Official credential setup

Where to enter credentials

In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.

Connection field Requirement
Application token (leave empty for personal accounts) Optional
Access mode Optional
Account authorization Optional

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "longitude": 116.392435,
    "latitude": 39.982376
  }
}'

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Commands

Find Luckin stores — luckin.shops.list

Run Find Luckin stores with Luckin Coffee. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
longitude number Required Longitude minimum: -180; maximum: 180
latitude number Required Latitude minimum: -90; maximum: 90
deptName string Optional Store name minLength: 1; maxLength: 200; pattern: "^[^\\p{C}]+$"

Full JSON Schema

Full JSON Schema

Example input

{
  "longitude": 116.392435,
  "latitude": 39.982376
}

At most 3 provider requests per invocation; timeout: 15 seconds.

Change drink options — luckin.products.switch

Run Change drink options with Luckin Coffee. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
deptId integer Required Store ID minimum: 1; maximum: 9007199254740991
productId integer Required Product ID minimum: 1; maximum: 9007199254740991
skuCode string Required SKU code minLength: 1; maxLength: 200; pattern: "^[^\\p{C}]+$"
attrOperationParam object Required additionalProperties: false
attrOperationParam.attributeId integer Required Attribute group ID minimum: 1; maximum: 9007199254740991
attrOperationParam.subAttr object Required additionalProperties: false
attrOperationParam.subAttr.attributeId integer Required Attribute value ID minimum: 1; maximum: 9007199254740991
attrOperationParam.subAttr.operation integer Required const: 3
amount integer Required Quantity minimum: 1; maximum: 20

Full JSON Schema

Full JSON Schema

Example input

{
  "deptId": 245062453,
  "productId": 123,
  "skuCode": "example-sku",
  "amount": 1,
  "attrOperationParam": {
    "attributeId": 1,
    "subAttr": {
      "attributeId": 2,
      "operation": 3
    }
  }
}

At most 3 provider requests per invocation; timeout: 15 seconds.

Read Luckin drink details — luckin.products.get

Run Read Luckin drink details with Luckin Coffee. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
deptId integer Required Store ID minimum: 1; maximum: 9007199254740991
productId integer Required Product ID minimum: 1; maximum: 9007199254740991

Full JSON Schema

Full JSON Schema

Example input

{
  "deptId": 245062453,
  "productId": 123
}

At most 3 provider requests per invocation; timeout: 15 seconds.

Preview a Luckin order and discounts — luckin.orders.preview

Run Preview a Luckin order and discounts with Luckin Coffee. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
deptId integer Required Store ID minimum: 1; maximum: 9007199254740991
productList array Required Products minItems: 1; maxItems: 20
productList[] object Optional additionalProperties: false
productList[].amount integer Required Quantity minimum: 1; maximum: 20
productList[].productId integer Required Product ID minimum: 1; maximum: 9007199254740991
productList[].skuCode string Required SKU code minLength: 1; maxLength: 200; pattern: "^[^\\p{C}]+$"

Full JSON Schema

Full JSON Schema

Example input

{
  "deptId": 245062453,
  "productList": [
    {
      "productId": 123,
      "skuCode": "example-sku",
      "amount": 1
    }
  ]
}

At most 3 provider requests per invocation; timeout: 15 seconds.

Create a Luckin pickup order — luckin.orders.create

Run Create a Luckin pickup order with Luckin Coffee. This command can change provider data. Review the target and input before invoking it.

This operation can change provider data. Review the input before allowing an agent to call it.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
deptId integer Required Store ID minimum: 1; maximum: 9007199254740991
productList array Required Products minItems: 1; maxItems: 20
productList[] object Optional additionalProperties: false
productList[].amount integer Required Quantity minimum: 1; maximum: 20
productList[].productId integer Required Product ID minimum: 1; maximum: 9007199254740991
productList[].skuCode string Required SKU code minLength: 1; maxLength: 200; pattern: "^[^\\p{C}]+$"
longitude number Required Longitude minimum: -180; maximum: 180
latitude number Required Latitude minimum: -90; maximum: 90
couponCodeList array Optional Coupon codes from the order preview maxItems: 20; uniqueItems: true
couponCodeList[] string Optional Coupon code minLength: 1; maxLength: 200; pattern: "^[^\\p{C}]+$"
remark string Optional Order note minLength: 1; maxLength: 500; pattern: "^[^\\p{C}]+$"

Full JSON Schema

Full JSON Schema

Example input

{
  "deptId": 245062453,
  "productList": [
    {
      "productId": 123,
      "skuCode": "example-sku",
      "amount": 1
    }
  ],
  "longitude": 116.392435,
  "latitude": 39.982376
}

At most 3 provider requests per invocation; timeout: 15 seconds.

Read a Luckin order and pickup code — luckin.orders.get

Run Read a Luckin order and pickup code with Luckin Coffee. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
orderId string Required Order ID minLength: 1; maxLength: 32; pattern: "^[0-9]{1,32}$"

Full JSON Schema

Full JSON Schema

Example input

{
  "orderId": "1234567890123456789"
}

At most 3 provider requests per invocation; timeout: 15 seconds.

Cancel a Luckin order — luckin.orders.cancel

Run Cancel a Luckin order with Luckin Coffee. This command can change provider data. Review the target and input before invoking it.

This operation can change provider data. Review the input before allowing an agent to call it.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
orderId string Required Order ID minLength: 1; maxLength: 32; pattern: "^[0-9]{1,32}$"

Full JSON Schema

Full JSON Schema

Example input

{
  "orderId": "1234567890123456789"
}

At most 3 provider requests per invocation; timeout: 15 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Official provider documentation

Type to search…

↑↓ navigate↵ selectEsc close