# Tookan Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Tookan

Manage delivery tasks, agents and customers in Tookan from Muse.

- Record: https://musedirectory.ai/connector/tookan
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/tookan/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 288ms, checked 2026-10-29T10:45:44Z
- Endpoint: https://tookan.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T12:46:22Z)
- Source: Found in the official MCP Registry (io.usefulapi/tookan) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Ftookan

Connect to Tookan to view and manage delivery tasks, field agents, teams and customers. Create delivery tasks, assign agents, track status and view task history. Requires a Tookan account and API key.

Example request: "Create a delivery task for a customer and assign it to an available driver."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Tookan to help me. It is a free service with an MCP server at https://tookan.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- tookan_get_account: The connected Tookan account (admin user): user_id, email, name, company name and address. Good first call. POST /v2/get_user_details.
- tookan_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 
- tookan_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 progres
- tookan_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.
- tookan_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 /
- tookan_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
- tookan_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.
- tookan_get_agent_location: An agent's last known coordinates (latitude/longitude). POST /v2/get_fleet_location.
- tookan_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).
- tookan_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.
- tookan_find_customer_by_phone: Find customers by exact phone number. POST /v2/find_customer_with_phone.
- tookan_get_customer: One customer's profile (contact details, address, coordinates). POST /v2/view_customer_profile.
- tookan_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,
- tookan_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.
- tookan_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 succe

Screening checks:
- MCP handshake: pass (Answered in 465ms)
- Domain against threat feeds (Cloudflare security DNS): pass (tookan.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (15 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)