[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Supermove API and MCP server: Let your AI agent dispatch your Supermove moves. > Supermove has no MCP server, and its Developer API has four endpoints that all bring data in: new leads, website leads, surveys and project field updates (checked 28 Oct 2026). None reads a project, the Dispatch tab or an invoice. Cotlet runs 9 Supermove tools hosted, over MCP for agents and REST for scripts, in your own Office App login. Leads, projects, dispatch and invoices in your Supermove, worked by your agent. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST. [MCP setup](https://cotlet.dev/integrations/supermove-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/supermove-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Supermove - Page: https://cotlet.dev/integrations/supermove-api-mcp-server ## What can you automate in Supermove? - Put free trucks on unassigned jobs - Assign drivers and movers - Find jobs still Dispatch Not Done - Mark finished moves complete - Sort new leads by source - Flag projects with no invoice ## Does Supermove have an MCP server or an API? - Each endpoint is a URL you copy from Company Settings > Lead Providers, with no API key. Supermove's own FAQ says it does not "maintain a traditional list of API endpoints". - Data goes out only when an automation fires an Invoke Webhook action at a trigger such as Project Completed. There is no "project updated" webhook and no log of what was sent. - There is no Supermove app on Zapier and no n8n node. Supermove's AI Copilot and Voice Agents handle calls inside Supermove; nothing exposes them to your own agent. | What you need | Developer API | Automation webhooks | Cotlet | |---|---|---|---| | Send a new lead in | Yes | No | No, use the API | | List leads and projects | No | One project per trigger | Yes | | Read tomorrow's Dispatch tab | No | No | Yes | | Assign trucks and crew | No | No | Yes, after your OK | | Mark a job complete | No | No | Yes, after your OK | | Read a project's invoices | No | No | Yes | | What you build or host | A sender | An endpoint that logs | Nothing | Checked 28 Oct 2026. Sources: [Supermove Help: Developer API New Lead Endpoint](https://help.supermove.com/hc/en-us/articles/36934839868692-Developer-API-New-Lead-Endpoint), [Supermove Help: Developer API Update Project Endpoint](https://help.supermove.com/hc/en-us/articles/44293369216532-Developer-API-Update-Project-Endpoint), [Supermove Help: Custom Outbound Integration Overview](https://help.supermove.com/hc/en-us/articles/39531080065044-Custom-Outbound-Integration-Overview), [Supermove Help: Outbound Integrations, Commonly Asked Questions](https://help.supermove.com/hc/en-us/articles/39531816592532-Outbound-Integrations-Commonly-Asked-Questions) ## How does Cotlet connect to Supermove? 1. **Sign in to Supermove.** Use your own account in its Cotlet Cloud Browser. 2. **Choose MCP or REST.** Connect your agent or create a Cotlet API key. 3. **Run your workflow.** Ask your agent or send an HTTP request. We never keep your Supermove password, and no truck, crew or completion change goes in until you approve it. ## Connect Supermove to your agent or workflow Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide. 1. **Log in to the Office App once.** Create a Cotlet account, open Supermove in its Cloud Browser, log in as a dispatcher or admin and press Enable for agents. 2. **Add the Cotlet address.** Put https://cotlet.dev/mcp/v1 in the list of MCP servers or connectors of your agent. 3. **Allow the agent in.** Chat apps show a Cotlet sign-in page. Code editors, n8n and scripts take an API key from the console. Supermove sits on `https://cotlet.dev/mcp/v1` together with every other app you enable on Cotlet. Enabled Supermove after the agent connected? Refresh the connector to load the new tools. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet-supermove \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` ChatGPT: ``` Settings > Apps & Connectors > Create MCP server URL: https://cotlet.dev/mcp/v1/connect Authentication: OAuth ``` Cursor: ``` // ~/.cursor/mcp.json { "mcpServers": { "cotlet-supermove": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet-supermove] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` n8n: ``` MCP Client Tool (inside an AI Agent) Transport: HTTP Streamable URL: https://cotlet.dev/mcp/v1 Auth: Bearer, Tool: supermove_read ``` Make, Zapier: ``` Make: MCP Client > Call a tool Zapier: MCP Client by Zapier > Run Tool Server URL: https://cotlet.dev/mcp/v1 Token: Tool: supermove_write ``` ## How to use the Supermove REST API ### Create your Cotlet API key Create a Cotlet API key with access to Supermove and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. Connect Supermove in Cotlet and enable it for agents. Account access: Your own Supermove Office App login. What your agent can do follows your role in your company. You sign in in your own browser and keep any 2-step verification. ### Make your first Supermove API request REST: ``` curl https://cotlet.dev/api/v1/supermove/leads \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read leads and apply the operation limits A successful REST call puts the tool output in `result`. This illustrative response excerpt omits call IDs, messages and credit details. Illustrative response excerpt: ``` { "status": "success", "app": "supermove", "tool": "list_leads", "result": { "leads": [ { "lead_id": "lead_5cd1", "customer": "Dana Whitfield", "source": "Website form", "project_id": null, "created_at": "2026-10-27T18:42:00Z" }, { "lead_id": "lead_5cd0", "customer": "Omar Haddad", "source": "Lead provider", "project_id": "prj_9a41", "created_at": "2026-10-27T15:10:00Z" } ], "next_cursor": null } } ``` Returns each lead with its customer name, source and the project it became, if any. Leads come from every provider you set up, such as a website form. The tool only reads: it sends nothing to the customer. `cursor`: Next page cursor from the previous call. Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination. ### Supermove workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | Lists the jobs of one day as the Dispatch tab shows them. Use `list_dispatch_jobs` in your configured business report. | | Make | HTTP > Make a request | Lists the crew members and trucks free on a given date. Use `list_available_crew` in your configured business report. | | Python or Node.js | REST API | Lists the invoices of one project. Use `list_invoices` in your configured business report. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads Supermove; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template. Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports. The [API and MCP reference](https://cotlet.dev/integrations/supermove-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Supermove API endpoints and MCP tools ### Dispatch, trucks and crew One day per call, as the Dispatch tab shows it. A truck already on another job that day is refused. The crew learn of an assignment in the Crew App, so both writes ask first. - **List jobs on the Dispatch tab** (`list_dispatch_jobs`, read): Lists the jobs of one day as the Dispatch tab shows them. - **List available crew and trucks** (`list_available_crew`, read): Lists the crew members and trucks free on a given date. - **Assign trucks to a job** (`assign_trucks`, write, asks first): Assigns one or more trucks to a job, as the Assign button on the Dispatch tab does. - **Assign crew to a job** (`assign_crew`, write, asks first): Assigns crew members to a job, each with a position such as Driver or Mover. ### Projects and job completion Completing the last job turns the project Completed and opens Send Invoice. The tool does not send the invoice. - **List projects** (`list_projects`, read): Lists projects, newest first, with their status. - **Get project** (`get_project`, read): Reads one project with its jobs, dispatch state and invoices. - **Mark a job complete** (`mark_job_complete`, write, asks first): Marks one job complete, as Mark As Complete in the Office App does. ### Leads and invoices Read only. Leads from every provider you set up. Invoices need a role that sees Accounting: Admin or Operations Admin. - **List leads** (`list_leads`, read): Leads in your Supermove with customer, source and linked project, newest first. - **List project invoices** (`list_invoices`, read): Lists the invoices of one project. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/supermove-api-mcp-server#tools ## Who can see my Supermove session, and how do I revoke it? - **What we store.** Your logged-in Office App profile, AES-256-GCM, in Finland. Not the password. - **What your agent gets.** The 9 Supermove tools. No cookie, no lead provider URL. - **What the session sees.** What your Supermove role sees: projects, dispatch, crews, and Accounting for admins. - **What no tool touches.** Payments, card charges, storage autopay, payroll and tips. - **If Supermove asks for a code.** You type it in the Cloud Browser yourself. We never enter it. - **How to cut access.** Disable for agents, reset the browser, or deactivate the login in View/Edit Staff. Supermove has four roles. A Manager login sees dispatch and projects but not Accounting, so list_invoices fails on it; a Salesperson login sees only its own jobs. Pick the narrowest role that covers your jobs. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). We have no SOC 2 report or third-party pentest yet. ## Is it against Supermove's terms? Account safety > (vii) interfere or attempt to interfere with the proper working of the Service or any activities conducted on the Service; or (viii) bypass any measures Supermove may use to prevent or restrict access to the Service > > [Supermove Enterprise Terms, section 6, last updated 28 Aug 2020](https://www.supermove.com/legal) We found no clause on bots, scripts or scraping in the Enterprise Terms or the privacy policies (checked 28 Oct 2026). Section 9 lets Supermove suspend an account that is 60 days past due or whose use is "reasonably likely to result in" damage to the Service; any other breach gets 30 days to cure after written notice. A few calls a day in your own login fit inside that, though Supermove could still object. We found no public case of a moving company cut off for automation. How we keep your account looking like you: - Your own Office App login, signed in by you - One Cloud Browser with its own IP and cookies - Truck, crew and completion changes wait for your OK - No tool charges a card, sends an invoice or deletes a project - If Supermove objects, we pause the Supermove tools for everyone within 24 h > Your dispatchers work in the same Office App. Run big jobs, such as a weekly invoice pass over 25 projects, outside your busy office hours. ## What happens when Supermove changes? - **12 h** between tests of the Supermove reads - **24 h** between tests of assignments and completions your crew would see - **$0** for a call to a Supermove tool paused for repair Supermove posts a newsletter of Office App changes in its help center most months. When the Dispatch tab or a job popup moves, the repair happens on our side and your evening dispatch run keeps the same prompt. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the Unassigned tab.** Tomorrow's jobs and how many trucks each needs. 2. **Finds who is free.** Trucks with an open slot and crew available that date. 3. **Waits for your OK.** Each assignment shows up in your Cotlet console first. 4. **Reports the gaps.** Jobs staffed, and the ones short a truck or a mover. | Action | Undo | |---|---| | Assign a truck | Change it on the job; a crew member may already have seen it | | Assign crew | Remove them on the job; the Crew App may already have asked them to accept | | Mark a job complete | Not documented in the help center; your Job Completed automations may already have run | | List or read anything | Nothing changes | All 3 write tools ask first: assign_trucks, assign_crew and mark_job_complete. Six reads run at once. For a nightly dispatch run you can turn the wait off per tool once you trust it. > Check your automations before you let the agent complete jobs: a Job Completed or Project Completed trigger can email the customer or send a webhook the moment the job closes. MCP call: ``` { "name": "assign_trucks", "arguments": { "job_id": "job_77b3", "truck_ids": [ "trk_2" ] } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/supermove/jobs/job_77b3/trucks/assign \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"truck_ids":["trk_2"]}' ``` Response: ``` { "job_id": "job_77b3", "trucks": [ "Truck 2" ], "dispatch_done": false } ``` Scripts reach the same tools over REST at `/api/v1/supermove`, with the same key and price, so a cron job can pull the Dispatch Not Done list before the trucks leave. A call your role cannot make fails and costs nothing. The tools table lists the REST path of each tool. ## How much does the Supermove MCP server cost? **About $40 a month** for a 6-truck company doing about 4 moves a day, 6,960 credits. Your Supermove contract stays with Supermove. | Job | Calls | Credits | |---|---|---| | Staff tomorrow's 4 moves | 10 × 26 | 2,600 | | Morning check of Dispatch Not Done | 2 × 26 | 520 | | Complete a job the crew left open | 3 × 26 | 780 | | New leads with no project yet | 2 × 26 | 520 | | Weekly invoice check, 25 projects | 26 × 4 | 1,040 | | Cloud Browser, 30 days | | 1,500 | | Total | | 6,960 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - No developer, endpoint or webhook to host The month is our example: Supermove's customer stories show fleets of 3 to 15 trucks, and we took 6 trucks over 26 working days. Staffing is most of the bill, one call per truck and one per crew list; a slow week costs less. Supermove publishes no prices, so its fee is not in the table. Dollars at the $29 pack rate. ## Supermove MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | GitHub | No Supermove MCP server or CLI found. | [api-evangelist/supermove](https://github.com/api-evangelist/supermove) is a README profile of the public surface, 0 stars, no code. | | Automation webhooks to Zapier or your endpoint | Push a project payload when a trigger fires, such as Project Completed. | One way, one project at a time, no log on Supermove's side, no writes back. | | Developer API: Update Project | Changes names, notes, contacts, tags and job start times by project UUID. | No trucks, crew or job status, and Supermove says its changes "can't be rolled back". | | [MattyMailers/smartmoving-mcp](https://github.com/MattyMailers/smartmoving-mcp) | MCP server on the SmartMoving External API, MIT, 4 stars, last commit 20 Jun 2026. | For SmartMoving, a rival platform: you would move your company off Supermove. | | Supermove AI Copilot and Voice Agents | Supermove's own AI for calls and sales follow-up. | Inside Supermove only; your agent cannot call it. | If you only need new leads in, the Developer API is free and official. If you need a copy of finished projects in your own system, an automation webhook does it. Cotlet is for an agent that reads the Dispatch tab and staffs, completes and checks jobs without a developer. ## Who runs Cotlet Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Send questions about the Supermove tools to contact@cotlet.dev. ## Supermove API and MCP: questions ### How do I get access? Create a free account at https://cotlet.dev, open Supermove under Integrations in the console and log in to the Office App in its Cloud Browser. The trial starts with your first app and asks for no card. ### How do I connect Supermove to ChatGPT or Claude? Sign up at cotlet.dev, log in to Supermove once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Supermove account through Cotlet, in their phone apps too. ### What can ChatGPT do in Supermove? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Supermove: dispatch unassigned moving jobs; check which jobs are not dispatch done; complete finished jobs. You ask in plain words, and anything that reaches other people waits for your OK first. ### Can my agent take or record payments in Supermove? No. The tools read invoices and mark jobs complete, nothing more. Supermove has its own payment screens, such as Record Payment on the invoice tab of a project, and they stay in the Office App. ### Does the Supermove Developer API read my projects? Supermove documents endpoints that send in leads and surveys and update a project, on a URL unique to your company (checked 28 Oct 2026). It documents no endpoint that lists projects, jobs or invoices. Automations can send a webhook out when something changes. ### Does it text my crew? No tool sends an SMS. Your Supermove settings decide what the crew sees: with crew accept and decline on, an assignment shows up in the Crew App for them to accept, and the job turns Dispatch Done once everyone accepts. ### Which Supermove role should the login have? Admin or Operations Admin if you want list_invoices; both see Accounting. A Manager login runs every other tool. A Salesperson login sees only its own jobs and is too narrow for dispatch. ### Is the MCP server different from the REST API? Only the way in differs. Both carry the same 9 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts, cron jobs and HTTP steps use REST. ### Is Cotlet affiliated with Supermove? No. Cotlet is independent and not affiliated with Supermove, Inc. ### Can I use the Supermove API without an AI agent? Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.