Read stops, orders, trips and ratings; add notes to stops and shipments in Locate2u. For delivery and field service teams that plan routes and drivers in Locate2u. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"locate2u": {
"url": "https://locate2u.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"locate2u": {
"type": "http",
"url": "https://locate2u.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
List the stops that are scheduled for a day. List the stops and shipments that no driver has yet.
locate2u_list_scheduled_stops locate2u_list_unassigned_stops locate2u_list_unassigned_shipments
Get a summary of all trips of the team with driver, distance, time and stop counts. Open one trip to read its stops.
locate2u_get_team_trips_summary locate2u_list_team_trips locate2u_get_trip
Find an order by order number or purchase order number. Read the order, and the stop that belongs to it.
locate2u_search_orders locate2u_find_order locate2u_get_order locate2u_get_stop
Read the answers that a driver gave on a stop. List the delivery ratings that customers left over a date range.
locate2u_get_stop_pod_answers locate2u_list_customer_ratings
Read the distance and the time that each team member drove over a date range.
locate2u_team_travel_statistics locate2u_list_team_members
Add a text note to a stop or to a shipment. The team and the driver can read it.
Changes data · locate2u_add_stop_note locate2u_add_shipment_note
The login page asks for your Locate2u Client Id and Locate2u Client Secret.
In Locate2u open Team settings → Apps and click + (a Team Owner can do this). Copy the Client Secret at once: Locate2u shows it only one time. Your credentials are used only to call the API on your behalf and to derive a private account id.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Locate2u Client Id and Locate2u Client Secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the Locate2u connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
locate2u_get_me | read | Get the current user Get the user that owns the connected app: name, email, role, time zone. Locate2u API: GET /users/me. |
locate2u_get_team | read | Get the team Get the connected team with its settings and branding. Locate2u API: GET /team. |
locate2u_list_team_members | read | 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 | read | Get a team member Get one team member by public user id. Locate2u API: GET /team-members/{publicUserId}. |
locate2u_list_team_regions | read | List team regions List the regions of the team. Locate2u API: GET /team-regions. |
locate2u_list_warehouses | read | List warehouses List the team's warehouses. Locate2u API: GET /warehouses. |
locate2u_list_services | read | List services List all services the team offers. Locate2u API: GET /services. |
locate2u_list_customers | read | List customers List the team's customers. Locate2u API: GET /customers. |
locate2u_search_customers | read | Search customers Search customers by text (name, company, email, phone). Locate2u API: GET /customers/search. |
locate2u_get_customer | read | Get a customer Get one customer by id. Locate2u API: GET /customers/{id}. |
locate2u_search_orders | read | Search orders Search orders by order number, purchase order number, status, payment status, customer or date. Locate2u API: GET /orders/search. |
locate2u_get_order | read | Get an order Get one order by id. Locate2u API: GET /orders/{id}. |
locate2u_find_order | read | Find an order by reference Find a single order by its order number, or by a source and source reference pair. Locate2u API: GET /orders. |
locate2u_list_orders_created | read | List orders created in a date range List orders created between two dates, optionally with stops and items. Locate2u API: GET /orders/created. |
locate2u_get_stop | read | Get a stop Get one stop (a delivery or pickup) with status, contact, address and time window. Locate2u API: GET /stops/{id}. |
locate2u_search_stops | read | Find stops by source reference Find stops by the source reference that the integration stored on them. Locate2u API: GET /stops/search. |
locate2u_list_scheduled_stops | read | 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 | read | List unassigned stops List stops that no driver has yet. Locate2u API: GET /stops/unassigned. |
locate2u_list_stop_notes | read | List notes of a stop List all notes on a stop, with attachments. Locate2u API: GET /stops/{id}/notes. |
locate2u_get_stop_pod_answers | read | Get proof-of-delivery answers of a stop Get the answers a driver gave to the proof-of-delivery questions on a stop. Locate2u API: GET /stops/{id}/podquestionanswers. |
locate2u_get_shipment | read | Get a shipment Get a shipment with its pickup and drop stops and items. Locate2u API: GET /shipments/{id}. |
locate2u_list_unassigned_shipments | read | List unassigned shipments List shipments that no team member has yet. Locate2u API: GET /shipments/unassigned. |
locate2u_list_shipment_notes | read | List notes of a shipment List all notes on a shipment. Locate2u API: GET /shipments/{id}/notes. |
locate2u_get_team_trips_summary | read | Summarize the team's trips for a day 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 | read | List all trips of the team for a day All trips (assigned and unassigned) for a day, each with its driver and stops. Locate2u API: GET /trips/team/{tripDate}. |
locate2u_get_driver_trip | read | Get a driver's trip for a day Get the trip of one team member on a day, optionally filtered by status. Locate2u API: GET /trips/user/{publicUserId}/{tripDate}. |
locate2u_get_trip | read | Get a trip by id Get one trip by id with its stops. Locate2u API: GET /trips/id/{id}. |
locate2u_list_runs | read | List runs for a day 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 | read | 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 | read | List delivery 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 | read | Search inventory items Search inventory items by keyword, warehouse or status. Locate2u API: GET /items/search. |
locate2u_get_item | read | Get an inventory item Get one inventory item by id. Locate2u API: GET /items/{id}. |
locate2u_add_stop_note | write | Add a note to a stop 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 note to a shipment 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. |
locate2u_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
locate2u_request_feature | Request a missing feature Tell usefulapi that the user needs something the Locate2u tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
locate2u_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Locate2u (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
locate2u_cancel_subscription | Cancel the Pro subscription Cancel the caller's Locate2u Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run locate2u_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this Locate2u server only. Subscribe with locate2u_upgrade (it returns a Stripe Checkout link). Cancel any time with locate2u_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running locate2u_upgrade before then undoes the cancel. Or write to [email protected].
Plan tomorrow: stops and missing drivers. Review the trips of every driver for a day. Find an order by its reference. Check proof of delivery and customer ratings. Report the distance driven by the team. Leave a note for the driver on a stop. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Locate2u. The server calls the Locate2u API with your own Locate2u access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Locate2u Client Id and Locate2u Client Secret. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Locate2u Client Id and Locate2u Client Secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Locate2u API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Locate2u.
Yes, if you approve it. 2 of the 34 Locate2u tools can create or change data. The other 32 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this Locate2u server only. Cancel any time: Pro then runs to the end of the paid period. Run locate2u_usage_status to see how many calls you used.
Ask the AI to run locate2u_upgrade: it returns a Stripe Checkout link. To cancel, run locate2u_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with locate2u_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.