Summary
Tookan (Jungleworks) delivery and field workforce management: create, edit, assign and track pickup, delivery, appointment and field tasks, update their status, see agents with their location and status, teams and customers. One API key.
Guided setup
Connect Tookan to Microsoft Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect Tookan in the guided setup, then add your MCP URL to Microsoft Copilot. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for Tookan
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Tookan, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Tookan + Microsoft Copilot
Tookan (Jungleworks) delivery and field workforce management: create, edit, assign and track pickup, delivery, appointment and field tasks, update their status, see agents with their location and status, teams and customers. One API key.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
TOOKAN_API_KEY
Step 1 — Get credentials
Setting up takes about 2 minutes. You need a Tookan account at app.tookanapp.com with access to Settings → API Keys. The connector needs one API key.
- Sign in at app.tookanapp.com and open Settings → API Keys.
- On the V2 tab copy the API key into
TOOKAN_API_KEY. If the list is empty, click Generate Key first. - Install the connector. Run
tookan_list_teamsto check the connection: it lists your teams with their ids.
Cloud and self-hosted work the same way: the key is the same, and there is no redirect URL to set.
Authentication: every Tookan call is a POST with a JSON body, and the connector adds api_key to each body. The key gives full access to the account, so treat it like a password.
Where to start: tookan_list_teams for team ids, tookan_list_agents for agents and their status, tookan_list_tasks for the tasks of a day (it needs the task type, a start date and an end date) and tookan_get_task_details for one task.
What it reads: tasks of one type in a date range of at most 31 days, paged with requested_page; up to 100 tasks at once with their history; tasks by your own order ids; the pickup and delivery that belong to one order; agents with their status, profile, current tasks and last known location; agents within a radius of a point (up to 100 km); teams; customers by name or phone.
What it writes: tookan_create_task, tookan_edit_task, tookan_update_task_status, tookan_assign_task, tookan_add_customer and tookan_edit_customer are switched on. With tookan_assign_task, notify 1 alerts the agent.
Switched off at install: tookan_delete_task (delete a task) and tookan_delete_customer (delete a customer). Neither can be restored. To stop a task but keep it, the AI sets status 9 (cancelled) with tookan_update_task_status. Switch them on on the connector page if the AI should use them; the AI asks you to confirm every change.
Task kinds: tookan_create_task chooses the kind with layout_type, has_pickup and has_delivery: pickup 0, 1, 0; delivery 0, 0, 1; pickup and delivery 0, 1, 1; appointment 1, 0, 0; field workforce 2, 0, 0. In lists the task types are 0 pickup, 1 delivery, 2 appointment and 3 field workforce.
Statuses: tasks are 0 assigned, 1 started, 2 successful, 3 failed, 4 in progress or arrived, 6 unassigned, 7 accepted, 8 declined, 9 cancelled and 10 deleted. Agents are 0 available, 1 offline and 2 busy.
Times: task times are local, YYYY-MM-DD HH:MM:SS; list filters take YYYY-MM-DD. timezone is the UTC offset in minutes with the sign inverted: India -330, Central Europe -60 in winter and -120 in summer, New York 300 in winter. Answers use 0000-00-00 00:00:00 for empty times.
Privacy: login tokens and password hashes that Tookan includes in agent and customer answers are removed before they reach the AI.
Limits: Tookan publishes no rate limits, so the AI avoids tight loops and uses the date and id filters.
Common errors: Tookan reports the result in the body: status 100 means a missing parameter, 101 an invalid API key, 201 a refused action with the reason in message, and 404 an execution error. The connector reports these as failed calls with the message.
Not covered: agent wallet transactions, payouts and fare estimates (nothing moves money), merchant administration, geofences and webhooks.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Microsoft Copilot
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.
- In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
- Enter a Server name (for example
AnythingMCP), a Server description that says what the connector does, and the Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server. - Under authentication, choose API key, set Type to Header and the header name to
X-API-Key, then select Create. - In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
- Try it in the agent's Test pane: ask for something that needs the
Tookantools. - Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.
Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.
Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.
Available tools
| Tool | What it does |
|---|---|
tookan_list_tasks | List tasks of one type in a date range (at most 31 days): job_id, order_id, job_status (0 assigned, 1 started, 2 successful, 3 failed, 4 in… |
tookan_get_task_details | Read up to 100 tasks by id: status, type, agent, team, customer, addresses and coordinates, scheduled, started, arrived and completed times… |
tookan_get_tasks_by_order_id | Read the tasks created with your own order ids (order_id field of create): the same details as tookan_get_task_details |
tookan_get_related_tasks | Read the pickup and delivery tasks that belong together, by the pickup_delivery_relationship value of a task |
tookan_list_agents | List agents (drivers, field staff, called fleets in the API): fleet_id, name, username, email, phone, status (0 available, 1 offline, 2… |
tookan_get_agent_profile | Read one agent's profile and current tasks: name, contact, tags, transport, team, status, location, and the jobs assigned to them |
tookan_get_agent_location | Read the last known latitude and longitude of one agent |
tookan_find_agents_nearby | Find agents within a radius of a point (up to 100 km), with their distance and status |
tookan_list_teams | List teams: team_id, team_name, address, coordinates, tags, battery_usage |
tookan_list_customers | List customers: customer_id, name, phone, email, address and coordinates |
tookan_find_customer_by_phone | Find customers by phone number: customer_id, name, email, phone, address and coordinates |
tookan_get_customer | Read one customer's profile: name, phone, email, address, coordinates and created date |
tookan_create_task | Create a task |
tookan_edit_task | Change an existing task: addresses, times, customer, description, team, agent, tags or custom fields |
tookan_update_task_status | Set the status of one or more tasks: 0 assigned, 1 started, 2 successful, 3 failed, 4 in progress or arrived, 6 unassigned, 7 accepted, 8… |
tookan_assign_task | Assign a task to an agent of a team (or reassign it). notify 1 alerts the agent |
tookan_delete_task | Delete a task |
tookan_add_customer | Add a customer to the Tookan customer list |
tookan_edit_customer | Change a customer's name, phone, email, address or coordinates by customer_id |
tookan_delete_customer | Delete a customer |
Example prompts
- "Which delivery tasks for today are still unassigned?"
- "Which agents are available right now, and which are within 5 km of the depot?"
- "Show the pickup and delivery tasks of order 10452 and their status."
- "Create a delivery task to 12 Market Street for tomorrow at 10:00 for the customer with phone +15551234567."
- "Assign task 98765 to the nearest available agent of the downtown team and notify them."
FAQ
Can it delete tasks? tookan_delete_task exists but is switched off at install. To stop a task and keep its history, the AI sets status 9 (cancelled) with tookan_update_task_status.
Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.
What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.
The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.
Next steps
Was this guide helpful?