Tookan MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.7.3 · published by io.usefulapi

Read Tookan tasks, agents, teams and customers; create delivery tasks and assign agents.

Deletes · 3

Compare Registry entry

15 tools: 3 can delete or cancel things and 12 only read.

Scanned Oct 21, 2026

Deletes or cancels3Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things0Claude Code: ask
Only reads12Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

15 tools

Deletes or cancels 3Removes, cancels or revokes something.Claude Code: deny

assign_agent_to_taskWRITE: assign (or reassign) a task to an agent of a team; replaces any previous agent.No findings
Why it is in this group
- The name "assign_agent_to_task" says "assign": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: assign (or reassign) a task to an agent of a team; replaces any previous agent. Notifies the agent unless notify is false (so repeating the call notifies again). POST /v2/assign_fleet_to_task.
Annotations the server declares
- title: Assign an agent to a task
- destructiveHint: true
- idempotentHint: false
create_delivery_taskWRITE: create a delivery task (job) for a customer address, due by job_delivery_datetime in the given timezone.No findings
Why it is in this group
- The name "create_delivery_task" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE: create a delivery task (job) for a customer address, due by job_delivery_datetime in the given timezone. Optionally assign it to an agent (fleet_id) or team, or let Tookan auto-assign it within the team. Returns job_id and tracking link. Always uses the address given here, not one saved for the customer's phone (ignore_customer_lat_long 1). POST /v2/create_task (has_pickup 0, has_delivery 1, layout_type 0).
Annotations the server declares
- title: Create a delivery task
- destructiveHint: true
update_task_statusWRITE (DESTRUCTIVE): force a task's status, overriding the agent app.No findings
Why it is in this group
- The name "update_task_status" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
WRITE (DESTRUCTIVE): force a task's status, overriding the agent app. Completing (2 successful, 3 failed) or cancelling (9) closes the task and notifies per the account's settings; confirm with the user first. Deleting (10) is not offered. Settable: 0 assigned, 1 started, 2 successful, 3 failed, 4 arrived, 6 unassigned, 7 accepted, 8 declined, 9 cancelled. POST /v2/update_task_status.
Annotations the server declares
- title: Update task status
- destructiveHint: true

Only reads 12Looks things up and changes nothing.Claude Code: allow

find_customer_by_phoneFind customers by exact phone number.No findings
Why it is in this group
- The name "find_customer_by_phone" says "find": a word for reading.
Description, as the server wrote it
Find customers by exact phone number. POST /v2/find_customer_with_phone.
Annotations the server declares
- title: Find customer by phone
- readOnlyHint: true
get_accountThe connected Tookan account (admin user): user_id, email, name, company name and address.No findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
Description, as the server wrote it
The connected Tookan account (admin user): user_id, email, name, company name and address. Good first call. POST /v2/get_user_details.
Annotations the server declares
- title: Get account
- readOnlyHint: true
get_agentOne agent's profile (name, email, phone, tags, transport, location, rating, active state) and current tasks.No findings
Why it is in this group
- The name "get_agent" says "get": a word for reading.
Description, as the server wrote it
One agent's profile (name, email, phone, tags, transport, location, rating, active state) and current tasks. Only profile fields are returned; app tokens and password hashes never are. POST /v2/view_fleet_profile.
Annotations the server declares
- title: Get agent profile
- readOnlyHint: true
get_agent_locationAn agent's last known coordinates (latitude/longitude).No findings
Why it is in this group
- The name "get_agent_location" says "get": a word for reading.
Description, as the server wrote it
An agent's last known coordinates (latitude/longitude). POST /v2/get_fleet_location.
Annotations the server declares
- title: Get agent location
- readOnlyHint: true
get_customerOne customer's profile (contact details, address, coordinates).No findings
Why it is in this group
- The name "get_customer" says "get": a word for reading.
Description, as the server wrote it
One customer's profile (contact details, address, coordinates). POST /v2/view_customer_profile.
Annotations the server declares
- title: Get customer profile
- readOnlyHint: true
get_task_statsTask counts per status (e.g.No findings
Why it is in this group
- The name "get_task_stats" says "get": a word for reading.
Description, as the server wrote it
Task counts per status (e.g. successful vs failed), optionally for one task type, one team and a date range. Task status codes: 0 assigned, 1 started, 2 successful, 3 failed, 4 in progress/arrived, 6 unassigned, 7 accepted/acknowledged, 8 declined, 9 cancelled, 10 deleted. POST /v2/user_task_stats.
Annotations the server declares
- title: Task statistics
- readOnlyHint: true
get_tasksFull details of up to 100 tasks by job id: customer, addresses, agent (fleet_id/fleet_name), status, timestamps (started/arrived/completed), tracking link, custom fields; optionall…No findings
Why it is in this group
- The name "get_tasks" says "get": a word for reading.
Description, as the server wrote it
Full details of up to 100 tasks by job id: customer, addresses, agent (fleet_id/fleet_name), status, timestamps (started/arrived/completed), tracking link, custom fields; optionally the status history. Task status codes: 0 assigned, 1 started, 2 successful, 3 failed, 4 in progress/arrived, 6 unassigned, 7 accepted/acknowledged, 8 declined, 9 cancelled, 10 deleted. POST /v2/get_job_details.
Annotations the server declares
- title: Get task details
- readOnlyHint: true
get_tasks_by_order_idFull details of the tasks carrying the given order ids (the reference you set when creating a task).No findings
Why it is in this group
- The name "get_tasks_by_order_id" says "get": a word for reading.
Description, as the server wrote it
Full details of the tasks carrying the given order ids (the reference you set when creating a task). POST /v2/get_job_details_by_order_id.
Annotations the server declares
- title: Get tasks by order id
- readOnlyHint: true
list_agentsList agents (drivers / field workers; Tookan calls them fleets) with fleet_id, name, phone, tags, team and live status (0 available, 1 offline, 2 busy).No findings
Why it is in this group
- The name "list_agents" says "list": a word for reading.
Description, as the server wrote it
List agents (drivers / field workers; Tookan calls them fleets) with fleet_id, name, phone, tags, team and live status (0 available, 1 offline, 2 busy). Filter by name, tags, availability or fleet ids. The API returns the whole list; this tool returns a window (limit/offset, next_offset). POST /v2/get_all_fleets.
Annotations the server declares
- title: List agents
- readOnlyHint: true
list_customersList customers (customer_id, name, phone, email, address), optionally searched by name or phone.No findings
Why it is in this group
- The name "list_customers" says "list": a word for reading.
Description, as the server wrote it
List customers (customer_id, name, phone, email, address), optionally searched by name or phone. Paginated: one Tookan page per call (page, default 1). POST /v2/get_all_customers.
Annotations the server declares
- title: List customers
- readOnlyHint: true
list_tasksList tasks (Tookan calls them jobs) of one task type within a date range of the task date (at most 31 days, within the last 31 days).No findings
Why it is in this group
- The name "list_tasks" says "list": a word for reading.
Description, as the server wrote it
List tasks (Tookan calls them jobs) of one task type within a date range of the task date (at most 31 days, within the last 31 days). Paginated: one Tookan page per call (page, default 1). Filter by status, agent (fleet_id), team, customer, job ids or your order ids. Task status codes: 0 assigned, 1 started, 2 successful, 3 failed, 4 in progress/arrived, 6 unassigned, 7 accepted/acknowledged, 8 declined, 9 cancelled, 10 deleted. POST /v2/get_all_tasks.
Annotations the server declares
- title: List tasks
- readOnlyHint: true
list_teamsList teams (team_id, name, address, tags).No findings
Why it is in this group
- The name "list_teams" says "list": a word for reading.
Description, as the server wrote it
List teams (team_id, name, address, tags). With include_agents, each team also lists its agents. Returns a window (limit/offset, next_offset). POST /v2/view_all_team_only (or /v2/view_teams with agents).
Annotations the server declares
- title: List teams
- readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.7.3. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__tookan__get_account",
      "mcp__tookan__list_tasks",
      "mcp__tookan__get_tasks",
      "mcp__tookan__get_tasks_by_order_id",
      "mcp__tookan__get_task_stats",
      "mcp__tookan__list_agents",
      "mcp__tookan__get_agent",
      "mcp__tookan__get_agent_location",
      "mcp__tookan__list_teams",
      "mcp__tookan__list_customers",
      "mcp__tookan__find_customer_by_phone",
      "mcp__tookan__get_customer"
    ],
    "ask": [],
    "deny": [
      "mcp__tookan__create_delivery_task",
      "mcp__tookan__assign_agent_to_task",
      "mcp__tookan__update_task_status"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as tookan. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/tookan/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 19:23 UTC.

For agents: Markdown · JSON · report this listing