Merchant360 MCP by usefulapi

Read shifts and requests; create, change, publish and delete shifts; decide requests in Merchant360.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
84%
Naming quality
76%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (2)

  • LOWTool 'merchant360_list_schedule_requests' name length outside 3-30 rangein merchant360_list_schedule_requests
  • LOWTool 'merchant360_decide_schedule_request' name length outside 3-30 rangein merchant360_decide_schedule_request

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~2,474Tokens (tool definitions)
~1.5 KBTypical response size
Moderate attention impact (1.93% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "merchant360": {
      "url": "https://merchant360.usefulapi.io/mcp"
    }
  }
}

Remote endpoints

https://merchant360.usefulapi.io/mcpstreamable-http

What it can do

Tool inventory

Tools (10)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢merchant360_check_key

Show the merchant the API key acts on, the key's name, its scopes and whether it is live or test. Use it first to confirm the connection. Merchant360 API: GET /me.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢merchant360_list_staff

List the staff roster (name, title, sort order, whether the person has a login). This list is read-only and not paginated. Shift workers use the roster key from merchant360_list_shifts. Merchant360 API: GET /staff.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢merchant360_list_shifts(from, to)

List team shifts that start in a window, draft and published, earliest first, with the roster of people who can be scheduled (roster[].key is the worker_key to use when writing a shift). Not paginated. The default window starts at Sunday midnight of the current week (server time zone) and lasts 14 days; the window may be at most 92 days. Merchant360 API: GET /shifts.

Input Schema

{
  "type": "object",
  "properties": {
    "from": {
      "type": "string",
      "description": "Window start, inclusive, ISO 8601 with offset (for example 2026-11-23T09:00:00-05:00)."
    },
    "to": {
      "type": "string",
      "description": "Window end, exclusive; must be after from and at most 92 days after it. Default: from plus 14 days, ISO 8601 with offset (for example 2026-11-23T09:00:00-05:00)."
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢merchant360_get_shift(shift_id)

Get one shift by id: worker, start and end, unpaid break, role, note, and whether it is a draft or published. Merchant360 API: GET /shifts/{id}.

Input Schema

{
  "type": "object",
  "properties": {
    "shift_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The shift id (from merchant360_list_shifts)."
    }
  },
  "required": [
    "shift_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🟢merchant360_list_schedule_requests(status)

List staff time-off requests and shift trade requests (drop, pickup, handoff), newest first. Filter by status when set. Not paginated. Old requests are left out by the vendor. Merchant360 API: GET /schedule-requests.

Input Schema

{
  "type": "object",
  "properties": {
    "status": {
      "description": "Only requests in this status. accepted applies only to trade requests.",
      "type": "string",
      "enum": [
        "pending",
        "approved",
        "denied",
        "canceled",
        "accepted"
      ]
    }
  },
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴merchant360_create_shift(worker_key, starts_at, ends_at, break_min, role, ...)

WRITE: create a DRAFT shift. Staff do not see it and no text is sent until merchant360_publish_shifts publishes its window. Omit worker_key for an open shift. A shift lasts at most 24 hours. Merchant360 API: POST /shifts.

Input Schema

{
  "type": "object",
  "properties": {
    "worker_key": {
      "description": "u:<user_id> or c:<cashier_id> from the roster in merchant360_list_shifts. Omit or null for an open shift.",
      "type": [
        "string",
        "null"
      ]
    },
    "starts_at": {
      "type": "string",
      "description": "Shift start, ISO 8601 with offset (for example 2026-11-23T09:00:00-05:00)."
    },
    "ends_at": {
      "type": "string",
      "description": "Shift end, after starts_at, ISO 8601 with offset (for example 2026-11-23T09:00:00-05:00)."
    },
    "break_min": {
      "description": "Unpaid break in minutes (default 0).",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    },
    "role": {
      "description": "Role or station, for example Server. Cut to 40 characters.",
      "type": "string",
      "maxLength": 40
    },
    "note": {
      "description": "Note the worker sees with the shift.",
      "type": "string",
      "maxLength": 500
    },
    "idempotency_key": {
      "description": "Optional Idempotency-Key. Reuse the same key only when retrying the same call after a timeout.",
      "type": "string",
      "maxLength": 255
    }
  },
  "required": [
    "starts_at",
    "ends_at"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴merchant360_update_shift(shift_id, worker_key, starts_at, ends_at, break_min, ...)

WRITE: change one shift. Fields you omit keep their value. Send worker_key null to make the shift open, and role or note null (or empty) to clear them. A published shift shows the change to staff only after merchant360_publish_shifts runs again. Merchant360 API: PATCH /shifts/{id}.

Input Schema

{
  "type": "object",
  "properties": {
    "shift_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The shift id (from merchant360_list_shifts)."
    },
    "worker_key": {
      "description": "u:<user_id> or c:<cashier_id>; null makes the shift open.",
      "type": [
        "string",
        "null"
      ]
    },
    "starts_at": {
      "type": "string",
      "description": "New shift start, ISO 8601 with offset (for example 2026-11-23T09:00:00-05:00)."
    },
    "ends_at": {
      "type": "string",
      "description": "New shift end, after starts_at, ISO 8601 with offset (for example 2026-11-23T09:00:00-05:00)."
    },
    "break_min": {
      "description": "Unpaid break in minutes.",
      "type": "integer",
      "minimum": 0,
      "maximum": 9007199254740991
    },
    "role": {
      "description": "Role or station; null or empty clears it.",
      "type": [
        "string",
        "null"
      ]
    },
    "note": {
      "description": "Note for the worker; null or empty clears it.",
      "type": [
        "string",
        "null"
      ]
    }
  },
  "required": [
    "shift_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴merchant360_delete_shift(shift_id)

WRITE: permanently delete one shift, draft or published. No text is sent. A deleted published shift leaves the staff schedule at the next publish. Merchant360 API: DELETE /shifts/{id}.

Input Schema

{
  "type": "object",
  "properties": {
    "shift_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The shift id (from merchant360_list_shifts)."
    }
  },
  "required": [
    "shift_id"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴merchant360_publish_shifts(from, to, idempotency_key)

WRITE: publish every DRAFT shift that starts in the window, so staff can see it. Each worker with a published shift and a mobile number gets a text with a link to their schedule. Publishing an already-published window publishes nothing new. Merchant360 API: POST /shifts/publish.

Input Schema

{
  "type": "object",
  "properties": {
    "from": {
      "type": "string",
      "description": "Window start, inclusive, ISO 8601 with offset (for example 2026-11-23T09:00:00-05:00)."
    },
    "to": {
      "type": "string",
      "description": "Window end, exclusive; must be after from, ISO 8601 with offset (for example 2026-11-23T09:00:00-05:00)."
    },
    "idempotency_key": {
      "description": "Optional Idempotency-Key. Reuse the same key only when retrying the same call after a timeout.",
      "type": "string",
      "maxLength": 255
    }
  },
  "required": [
    "from",
    "to"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}
🔴merchant360_decide_schedule_request(request_id, decision, note, idempotency_key)

WRITE: approve or deny one staff time-off or shift trade request. The worker is texted the outcome, with the note when given. Approved time off also blocks those days on the public booking calendar. A decided request returns 409. Merchant360 API: POST /schedule-requests/{id}.

Input Schema

{
  "type": "object",
  "properties": {
    "request_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      "description": "The request id (from merchant360_list_schedule_requests)."
    },
    "decision": {
      "type": "string",
      "enum": [
        "approve",
        "deny"
      ],
      "description": "approve or deny."
    },
    "note": {
      "description": "Optional note for the worker's text (first 100 characters are sent).",
      "type": "string",
      "maxLength": 100
    },
    "idempotency_key": {
      "description": "Optional Idempotency-Key. Reuse the same key only when retrying the same call after a timeout.",
      "type": "string",
      "maxLength": 255
    }
  },
  "required": [
    "request_id",
    "decision"
  ],
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded10 tools