Locate2u MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 网店与支付

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://locate2u.usefulapi.io/mcp

claude mcp add --transport http locate2u https://locate2u.usefulapi.io/mcp

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

{
  "servers": {
    "locate2u": {
      "type": "http",
      "url": "https://locate2u.usefulapi.io/mcp"
    }
  }
}

https://locate2u.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• locate2u_get_me

  Get the user that owns the connected app: name, email, role, time zone. Locate2u API: GET /users/me.

• locate2u_get_team

  Get the connected team with its settings and branding. Locate2u API: GET /team.

• locate2u_list_team_members

  List the drivers and staff in the team, optionally with their current location. Locate2u API: GET /team-members.

• locate2u_get_team_member

  Get one team member by public user id. Locate2u API: GET /team-members/{publicUserId}.

• locate2u_list_team_regions

  List the regions of the team. Locate2u API: GET /team-regions.

• locate2u_list_warehouses

  List the team's warehouses. Locate2u API: GET /warehouses.

• locate2u_list_services

  List all services the team offers. Locate2u API: GET /services.

• locate2u_list_customers

  List the team's customers. Locate2u API: GET /customers.

• locate2u_search_customers

  Search customers by text (name, company, email, phone). Locate2u API: GET /customers/search.

• locate2u_get_customer

  Get one customer by id. Locate2u API: GET /customers/{id}.

• locate2u_search_orders

  Search orders by order number, purchase order number, status, payment status, customer or date. Locate2u API: GET /orders/search.

• locate2u_get_order

  Get one order by id. Locate2u API: GET /orders/{id}.

• locate2u_find_order

  Find a single order by its order number, or by a source and source reference pair. Locate2u API: GET /orders.

• locate2u_list_orders_created

  List orders created between two dates, optionally with stops and items. Locate2u API: GET /orders/created.

• locate2u_get_stop

  Get one stop (a delivery or pickup) with status, contact, address and time window. Locate2u API: GET /stops/{id}.

• locate2u_search_stops

  Find stops by the source reference that the integration stored on them. Locate2u API: GET /stops/search.

• locate2u_list_scheduled_stops

  List stops scheduled for a day (default: today in the team's zone), with paging. Locate2u API: GET /stops/scheduled.

• locate2u_list_unassigned_stops

  List stops that no driver has yet. Locate2u API: GET /stops/unassigned.

• locate2u_list_stop_notes

  List all notes on a stop, with attachments. Locate2u API: GET /stops/{id}/notes.

• locate2u_get_stop_pod_answers

  Get the answers a driver gave to the proof-of-delivery questions on a stop. Locate2u API: GET /stops/{id}/podquestionanswers.

• locate2u_get_shipment

  Get a shipment with its pickup and drop stops and items. Locate2u API: GET /shipments/{id}.

• locate2u_list_unassigned_shipments

  List shipments that no team member has yet. Locate2u API: GET /shipments/unassigned.

• locate2u_list_shipment_notes

  List all notes on a shipment. Locate2u API: GET /shipments/{id}/notes.

• locate2u_get_team_trips_summary

  Summary of every trip in the team on a day: driver, distance, time, stop counts, status. Locate2u API: GET /team/trips/{tripDate}.

• locate2u_list_team_trips

  All trips (assigned and unassigned) for a day, each with its driver and stops. Locate2u API: GET /trips/team/{tripDate}.

• locate2u_get_driver_trip

  Get the trip of one team member on a day, optionally filtered by status. Locate2u API: GET /trips/user/{publicUserId}/{tripDate}.

• locate2u_get_trip

  Get one trip by id with its stops. Locate2u API: GET /trips/id/{id}.

• locate2u_list_runs

  List the runs scheduled for a day, optionally for one team member, customer or run number. Locate2u API: GET /runs/{tripDate}.

• locate2u_team_travel_statistics

  Distance and time driven by the team's members and asset groups over a date range. Locate2u API: GET /team/reports/travel-statistics.

• locate2u_list_customer_ratings

  Delivery ratings that customers left for the team's stops over a date range. Locate2u API: GET /team/{teamId}/customer-ratings.

• locate2u_search_items

  Search inventory items by keyword, warehouse or status. Locate2u API: GET /items/search.

• locate2u_get_item

  Get one inventory item by id. Locate2u API: GET /items/{id}.

• locate2u_add_stop_note

  WRITE: add a text note to a stop. It is visible to the team and the driver. Each call adds a new note (do not retry blindly). Locate2u API: POST /stops/{id}/notes.

• locate2u_add_shipment_note

  WRITE: add a text note to a shipment, optionally tied to one of its stops. Each call adds a new note (do not retry blindly). Locate2u API: POST /shipments/{id}/notes.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 9 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 34 个工具描述，未发现针对 AI 的隐藏指令

与“网店与支付”中的其他服务器比较i

• 星标数多于此分类中其他 1743 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1743 个服务器的 96% 更新
• 基础检查结果等于或优于此分类中其他 1743 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{