Connect-MCP

Tookan MCP by usefulapi

io.usefulapi/tookan · v1.2.1

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

MCPremoteno credentialsTasks & projectsCRM & salesEmail

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 15 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 15 tools · 12 read, 3 write (incl. delete/pay) · Tasks & projects, CRM & sales, Email

Test call list_agents: needs a key: HTTP 401 (1,111 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://tookan.usefulapi.io/mcp

Tools

15 tools listed at last check
  • get_account The connected Tookan account (admin user): user_id, email, name, company name and address. Good first call. POST /v2/get_user_details.
  • list_tasks 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
  • get_tasks 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 unassig
  • get_tasks_by_order_id 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.
  • get_task_stats 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.
  • list_agents 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/g
  • get_agent 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.
  • get_agent_location An agent's last known coordinates (latitude/longitude). POST /v2/get_fleet_location.
  • list_teams 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).
  • list_customers 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.
  • find_customer_by_phone Find customers by exact phone number. POST /v2/find_customer_with_phone.
  • get_customer One customer's profile (contact details, address, coordinates). POST /v2/view_customer_profile.
  • create_delivery_task 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 t
  • assign_agent_to_task 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.
  • update_task_status 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 a

Badge

Connect-MCP badge for io.usefulapi/tookan

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.usefulapi/tookan.svg)](https://clawy.uk/mcp/s/io.usefulapi/tookan)

Repository · Website