INDIVIDUAL MCP TOOL

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).

usefulapi.ionone authenticationAvailability not checked

LIVE ENDPOINT

https://tookan.usefulapi.io/mcp

No auth detected

Connect to this endpoint to inspect the live schema for list_agents and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

usefulapi.io

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.tookan-mcp]
url = "https://tookan.usefulapi.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "tookan-mcp": {
      "type": "http",
      "url": "https://tookan.usefulapi.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: tookan-mcp
Remote MCP URL: https://tookan.usefulapi.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "tookan-mcp",
  "transport": "streamable-http",
  "url": "https://tookan.usefulapi.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

get_account — The connected Tookan account (admin user): user_id, email, name, company name and address.
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).
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.
get_tasks_by_order_id — Full details of the tasks carrying the given order ids (the reference you set when creating a task).
get_task_stats — Task counts per status (e.
get_agent — One agent's profile (name, email, phone, tags, transport, location, rating, active state) and current tasks.
get_agent_location — An agent's last known coordinates (latitude/longitude).
list_teams — List teams (team_id, name, address, tags).