[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) # FieldRoutes MCP server: Let your AI agent run the FieldRoutes office. > FieldRoutes has no MCP server and no ChatGPT or Claude app. Its API keys come through FieldRoutes support for each office, and the free tier allows "up to 50 API read requests" a day per office (FieldRoutes knowledge base, checked 8 Nov 2026). Cotlet runs 9 FieldRoutes tools hosted, over MCP for agents and REST for scripts, in your own FieldRoutes login. Your AI agent schedules visits from calls, moves a rained-out day, finds subscriptions due and chases past-due tickets. Sign in to FieldRoutes once in your own Cloud Browser. No API key, no developer. - Free 7-day trial, no card - Unofficial, not affiliated with FieldRoutes - Page: https://cotlet.dev/integrations/fieldroutes-api-mcp-server ## What can your AI agent do in FieldRoutes? - Schedule visits from calls - Move a rained-out day - Find subscriptions due - Chase past-due tickets - Log notes from the caller - Find customers and their history ## Does FieldRoutes have an MCP server or an API? - FieldRoutes issues an API key and token per office through support. - Webhooks (Trigger Rules) come only with the Premium API tier. - FieldRoutes has no connector in the ChatGPT apps directory or in Claude. | What you need | FieldRoutes API | By hand | Cotlet | |---|---|---|---| | Customers and subscriptions | 50 reads a day free | Yes, one by one | Yes | | Schedule or move a visit | With a key | Yes, one by one | Yes, after your OK | | Past-due tickets | With a key | Report export | Yes | | Ask in ChatGPT or Claude | No | No | Yes | | Developer needed | Yes | No | No | Checked 8 Nov 2026. Sources: [FieldRoutes knowledge base: API access](https://knowledgebase.fieldroutes.com/docs/fieldroutes-api-access.md), [FieldRoutes API overview](https://knowledgebase.fieldroutes.com/apidocs/fieldroutes-api-overview.md), [FieldRoutes API integrations](https://www.fieldroutes.com/operations-suite/api-integrations) ## How does the FieldRoutes MCP server work? 1. **Sign in to FieldRoutes.** Once, in a browser we host for you. 2. **Connect your AI agent.** One address in its settings. 3. **Hand it the busywork.** It drafts the work, you OK what customers get. We never keep your FieldRoutes password, and no appointment is scheduled or moved until you approve it. ## How to connect FieldRoutes to your AI agent 1. **Sign in to FieldRoutes in a Cloud Browser.** Create a Cotlet account, open FieldRoutes in its Cloud Browser, sign in with your FieldRoutes office login and press Enable for agents. 2. **Add the Cotlet address.** Enter https://cotlet.dev/mcp/v1 as the MCP server or connector URL in your agent. 3. **Let the agent in.** Chat apps open a Cotlet sign-in page. Editors, n8n and scripts send an API key made in the console. FieldRoutes shares the address `https://cotlet.dev/mcp/v1` with every other app you enable, so one connector covers them all. Turned FieldRoutes on after connecting? Refresh the connector and the 9 tools appear. Claude: ``` Settings > Connectors > Add custom connector URL: https://cotlet.dev/mcp/v1/connect Claude Code: claude mcp add --transport http cotlet \ 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": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet] 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: fieldroutes_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: fieldroutes_write ``` ## All 9 FieldRoutes MCP tools ### Customers Search matches name, phone, street and account number. New customers and notes reach no one, so they run at once. - **List customers** (`list_customers`, read): Customers, searchable by name, phone, address or account number. - **Get customer** (`get_customer`, read): One customer with subscriptions, appointments, tickets and notes. - **Create customer** (`create_customer`, write): Adds a new customer with a service address. - **Add customer note** (`add_customer_note`, write): Adds a note to a customer record. ### Scheduling New and moved appointments wait for your OK; your reminder settings decide what the customer hears. Subscriptions due show what still needs a slot. - **List appointments** (`list_appointments`, read): Appointments for a day or range, by technician, route or status. - **Schedule appointment** (`schedule_appointment`, write, asks first): Schedules a service visit for a customer. - **Reschedule appointment** (`reschedule_appointment`, write, asks first): Moves an appointment to another day, window or technician. - **List subscriptions due** (`list_subscriptions_due`, read): Recurring services due but not yet scheduled. ### Billing Unpaid tickets by days past due. Taking payments stays in FieldRoutes. - **List unpaid tickets** (`list_unpaid_tickets`, read): Open invoices (tickets) with balance and age. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/fieldroutes-api-mcp-server#tools ## Who can see my FieldRoutes session, and how do I revoke it? - **What we store.** Your signed-in FieldRoutes profile, AES-256-GCM encrypted, in Finland. No password. - **What your agent gets.** The 9 FieldRoutes tools, never the session cookie. - **What the session sees.** What your login sees: customers, subscriptions, schedule, tickets. - **What no tool touches.** Payments, refunds, routes optimization, payroll, deletes. - **If FieldRoutes signs you out.** You sign in again yourself, in the same Cloud Browser. - **How to cut access.** Disable for agents, reset the browser, or change your FieldRoutes password. Cotlet never types your password: you sign in yourself, and the agent only uses the session. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory ([live results](https://cotlet.dev/security.md)). ## What happens when FieldRoutes changes? - **12 h** between tests of the FieldRoutes reads - **24 h** between tests of sends a customer would notice - **$0** for a call to a FieldRoutes tool paused for repair When FieldRoutes moves a button on the scheduling screen or renames a customer tab, we fix the tool and your agent calls it the same way. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads Monday's appointments.** For the technician you name. 2. **Checks Wednesday.** Against the same technician's day. 3. **Proposes the moves.** And lists what does not fit. 4. **Waits, then moves.** The batch shows up in your Cotlet console first. | Action | Undo | |---|---| | Schedule an appointment | Yes, cancel it in FieldRoutes | | Move an appointment | Move it back; a reminder already sent stays sent | | Add a customer or note | Yes, edit it in FieldRoutes | 2 of 9 tools ask first: schedule_appointment, reschedule_appointment. New customers and customer notes reach no customer, so they run at once. You can turn the wait off per tool once you trust a routine. MCP call: ``` { "name": "reschedule_appointment", "arguments": { "appointment_id": "881204", "date": "2026-11-12", "window": "AM" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/fieldroutes/appointments/881204/reschedule \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"date":"2026-11-12","window":"AM"}' ``` Response: ``` { "appointment_id": "881204", "date": "2026-11-12", "window": "AM", "tech": "Brandon P.", "status": "Pending" } ``` A cron job or n8n flow can call the same tools over REST at `/api/v1/fieldroutes` with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path. ## How much does the FieldRoutes MCP server cost? **About $31 a month** for a pest and lawn company with 6 technicians, 5,350 credits. Your FieldRoutes plan stays as it is. | Job | Calls | Credits | |---|---|---| | Appointment scheduled from a call | 2 × 90 | 1,800 | | Rain day moved | 15 × 3 | 450 | | Subscriptions due, weekly | 2 × 4 | 80 | | Past-due tickets, weekly | 8 × 4 | 320 | | Customer note logged | 2 × 60 | 1,200 | | Cloud Browser, 30 days | | 1,500 | | Total | | 5,350 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Works on your current FieldRoutes package FieldRoutes publishes no stop counts, so the month is our example. Dollars at the $29 pack rate. ## FieldRoutes MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | FieldRoutes API | Customers, appointments, subscriptions and tickets for your own developer. | Key per office through support; 50 reads a day on the free tier; you build and host the code. | | Third-party MCP servers | Community servers on GitHub built on the API. | Need the same office API key first; you run them yourself. | | By hand | Every screen of FieldRoutes, one stop at a time. | Your office's time. | If you already have a Premium API key and a developer, building on the API is cheaper for syncing data. To schedule, move rain days and chase tickets from ChatGPT or Claude this week, Cotlet works in the FieldRoutes account you already have. ## Who runs Cotlet Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the FieldRoutes tools go to contact@cotlet.dev. ## FieldRoutes MCP server: questions ### How do I get access? Sign up free at https://cotlet.dev, open FieldRoutes under Integrations in the console and sign in to FieldRoutes in its Cloud Browser. The trial starts with your first app and asks for no card. ### How do I connect FieldRoutes to ChatGPT or Claude? Sign up at cotlet.dev, log in to FieldRoutes 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 FieldRoutes account through Cotlet, in their phone apps too. ### What can ChatGPT do in FieldRoutes? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in FieldRoutes: move a rained-out day; book re-services from calls; fill next week's routes. You ask in plain words, and anything that reaches other people waits for your OK first. ### Is there an official ChatGPT or Claude app for FieldRoutes? No. FieldRoutes has no ChatGPT or Claude connector of its own and FieldRoutes has no official MCP server (checked 8 Nov 2026). Cotlet is an independent one that works in ChatGPT, Claude, Cursor and any MCP client, on your signed-in account. ### Can ChatGPT schedule appointments in FieldRoutes? Yes, with Cotlet. ChatGPT finds the customer and schedules the service on the day and window you want, for example a re-service after a call. Scheduling waits for your OK by default. ### Can ChatGPT reschedule a rained-out day in FieldRoutes? Yes, with Cotlet. ChatGPT reads the day's appointments for a technician and moves them to the day you name, after your OK, and lists what does not fit. ### Can ChatGPT find unpaid invoices in FieldRoutes? Yes, with Cotlet. ChatGPT lists tickets with a balance by days past due, with the customer's contact details, so your office knows whom to call. ### Do I need a FieldRoutes API key to use Cotlet? No. Cotlet works through your own FieldRoutes login, so you do not need an office key from support or the Premium tier. It can do what your login can do in FieldRoutes. ### Does it change my routes? No. Cotlet schedules and moves appointments; route building and optimization stay in FieldRoutes, the way your office runs them today. ### Is the MCP server different from the REST API? Only in how it is called. Both carry the same 9 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with FieldRoutes? No. Cotlet is independent and not affiliated with FieldRoutes or its owner ServiceTitan. --- 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.