[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) # FieldEdge MCP server: Let your AI agent run the FieldEdge office work. > FieldEdge has no MCP server and no ChatGPT or Claude app. Its Open API is real, but customers ask for access through an onboarding form and get credentials for an app FieldEdge provisions (developer portal, checked 8 Nov 2026). Cotlet runs 10 FieldEdge tools hosted, over MCP for agents and REST for scripts, in your own FieldEdge login. Your AI agent turns lead emails into work orders, balances tomorrow's dispatch board, invoices yesterday's finished jobs and logs the checks. Sign in to FieldEdge once in your own Cloud Browser. No API request form, no developer. - Free 7-day trial, no card - Unofficial, not affiliated with FieldEdge - Page: https://cotlet.dev/integrations/fieldedge-api-mcp-server ## What can your AI agent do in FieldEdge? - Turn lead emails into work orders - Balance tomorrow's dispatch board - Invoice the jobs finished yesterday - Send invoices to customers - Log checks on the right invoice - List invoices unpaid for 30 days ## Does FieldEdge have an MCP server or an API? - The FieldEdge developer portal sends partners to an integrations email and customers to an access request form. - There are no self-service API keys in the FieldEdge app. - FieldEdge has no connector in the ChatGPT apps directory or in Claude. | What you need | FieldEdge API | By hand | Cotlet | |---|---|---|---| | Work orders and customers | After approval | Yes, one by one | Yes | | Dispatch a technician | After approval | Yes, one by one | Yes, after your OK | | Invoice and send | After approval | Yes, one by one | Yes, sending after your OK | | Ask in ChatGPT or Claude | No | No | Yes | | Developer needed | Yes | No | No | Checked 8 Nov 2026. Sources: [FieldEdge Developer Portal](https://docs-dev.fieldedge.com/), [FieldEdge partners](https://fieldedge.com/partners/), [FieldEdge pricing](https://fieldedge.com/pricing/) ## How does the FieldEdge MCP server work? 1. **Sign in to FieldEdge.** 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 FieldEdge password, and no dispatch, invoice or payment goes through until you approve it. ## How to connect FieldEdge to your AI agent 1. **Sign in to FieldEdge in a Cloud Browser.** Create a Cotlet account, open FieldEdge in its Cloud Browser, sign in with your office or dispatcher 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. FieldEdge shares the address `https://cotlet.dev/mcp/v1` with every other app you enable, so one connector covers them all. Turned FieldEdge on after connecting? Refresh the connector and the 10 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: fieldedge_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: fieldedge_write ``` ## All 10 FieldEdge MCP tools ### Customers Search matches name, phone, email and address, so a repeat caller is found before a duplicate is made. The customer card shows equipment and service agreements. - **List customers** (`list_customers`, read): Customers, searchable by name, phone, email or address. - **Get customer** (`get_customer`, read): One customer with equipment, agreements and recent work orders. - **Create customer** (`create_customer`, write): Adds a customer with a service address. ### Work orders and dispatch A new work order stays unassigned until it is dispatched to a technician and a window. Your notification settings decide who hears about it. - **List work orders** (`list_work_orders`, read): Work orders by date, status or technician. - **Create work order** (`create_work_order`, write): Opens a work order for a customer, unassigned or with a window. - **Dispatch technician** (`dispatch_technician`, write, asks first): Assigns a work order to a technician and a time window. ### Invoices and payments An invoice is built from the work order and stays a draft until it is sent. Payments are checks, cash and other manual types; no card is charged. - **List invoices** (`list_invoices`, read): Invoices by status, date or customer, with balances. - **Create invoice** (`create_invoice`, write): Builds the invoice for a completed work order. - **Send invoice** (`send_invoice`, write, asks first): Emails an invoice to the customer. - **Record payment** (`record_payment`, write, asks first): Logs a check, cash or other manual payment on an invoice. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/fieldedge-api-mcp-server#tools ## Who can see my FieldEdge session, and how do I revoke it? - **What we store.** Your signed-in FieldEdge profile, AES-256-GCM encrypted, in Finland. No password. - **What your agent gets.** The 10 FieldEdge tools, never the session cookie. - **What the session sees.** What your login sees: customers, work orders, prices, invoices. - **What no tool touches.** Card charges, payroll, price book edits, users, deletes. - **If FieldEdge 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 FieldEdge 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 FieldEdge changes? - **12 h** between tests of the FieldEdge reads - **24 h** between tests of sends a customer would notice - **$0** for a call to a FieldEdge tool paused for repair When FieldEdge moves a button on the dispatch board or renames a work order status, 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 yesterday's completed work orders.** Every page, until a short one comes back. 2. **Holds back what is not ready.** No items, a zero total or a return visit booked. 3. **Builds and checks totals.** Each invoice against the work order it came from. 4. **Waits, then sends.** The batch shows up in your Cotlet console first. | Action | Undo | |---|---| | Create a work order | Yes, cancel it in FieldEdge | | Dispatch a technician | Move it; a message already sent stays sent | | Create an invoice | Yes, edit or void the draft | | Record a payment | Delete the payment in FieldEdge | | Send an invoice | No | 3 of 10 tools ask first: dispatch_technician, send_invoice, record_payment. A new customer, a work order or a draft invoice reach no customer, so they run at once. You can turn the wait off per tool once you trust a routine. MCP call: ``` { "name": "dispatch_technician", "arguments": { "work_order_id": "WO-88342", "technician": "Carlos", "window_start": "2026-11-13T13:00", "window_end": "2026-11-13T15:00" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/fieldedge/work-orders/WO-88342/technician/dispatch \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"technician":"Carlos","window_start":"2026-11-13T13:00","window_end":"2026-11-13T15:00"}' ``` Response: ``` { "work_order_id": "WO-88342", "technician": "Carlos", "window": "2026-11-13 13:00-15:00", "status": "Dispatched" } ``` A cron job or n8n flow can call the same tools over REST at `/api/v1/fieldedge` with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path. ## How much does the FieldEdge MCP server cost? **About $48 a month** for an HVAC shop with 6 technicians, 8,280 credits. Your FieldEdge plan stays as it is. | Job | Calls | Credits | |---|---|---| | Lead email into a work order | 3 × 60 | 1,800 | | Tomorrow's board checked and balanced | 4 × 22 | 880 | | Yesterday's 8 jobs invoiced and sent | 17 × 22 | 3,740 | | Unpaid invoice list, weekly | 3 × 4 | 120 | | Checks logged, weekly (5) | 6 × 4 | 240 | | Cloud Browser, 30 days | | 1,500 | | Total | | 8,280 | - 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 FieldEdge plan FieldEdge publishes no job counts, so the month is our example. Dollars at the $29 pack rate. ## FieldEdge MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | FieldEdge Open API | Customers, work orders and invoices for your own developer. | Access on request through the onboarding form; you build and host the code. | | [usefulapi FieldEdge connector](https://www.usefulapi.io/fieldedge/) | Hosted MCP connection for ChatGPT and Claude, custom setup. | Runs on API credentials you get from FieldEdge first. | | By hand | Every screen of FieldEdge, one record at a time. | Your time, during office hours. | If your developer already has FieldEdge API access, building on it is cheaper for simple reads. To book, dispatch and invoice from ChatGPT or Claude this week, Cotlet works in the FieldEdge account you already have. ### FieldEdge MCP setup on GitHub and PyPI Prefer code? Our public repo has a ready FieldEdge MCP config for Claude Code, ChatGPT and Cursor, an agent skill and a small command-line tool. Add your Cotlet API key and your agent works in your own FieldEdge account. - MCP config for Claude Code, Cursor and Codex - Agent skill and Cursor rules for FieldEdge - Clone it and run, Python standard library only - Elastic License 2.0, free in your own business - Code: https://github.com/cotlet-connect/fieldedge-mcp ## 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 FieldEdge tools go to contact@cotlet.dev. ## FieldEdge MCP server: questions ### How do I get access? Sign up free at https://cotlet.dev, open FieldEdge under Integrations in the console and sign in to FieldEdge in its Cloud Browser. The trial starts with your first app and asks for no card. ### How do I connect FieldEdge to ChatGPT or Claude? Sign up at cotlet.dev, log in to FieldEdge 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 FieldEdge account through Cotlet, in their phone apps too. ### What can ChatGPT do in FieldEdge? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in FieldEdge: book service calls from lead emails; balance the dispatch board; invoice completed work orders. 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 FieldEdge? No. FieldEdge has no ChatGPT or Claude connector of its own and FieldEdge 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 create and dispatch work orders in FieldEdge? Yes, with Cotlet. ChatGPT finds or adds the customer, opens the work order and puts it on a technician's row of the dispatch board. Dispatching waits for your OK by default. ### Can ChatGPT send invoices in FieldEdge? Yes, with Cotlet. ChatGPT builds the invoice from the completed work order and emails it to the customer after your OK. It can also list what is still unpaid. ### Can ChatGPT check the dispatch board in FieldEdge? Yes, with Cotlet. Ask "who is on tomorrow and how many calls each" and ChatGPT reads the work orders per technician and answers in plain words. ### Do I need FieldEdge API access to use Cotlet? No. Cotlet works through your own FieldEdge sign-in, so you skip the API request form. It can do what your login can do in FieldEdge. ### Can it react when a call comes in? Run it on a schedule, for example every morning at 7 for last night's lead emails, or ask it when a call arrives. Nothing needs to change in FieldEdge. ### Is the MCP server different from the REST API? Only in how it is called. Both carry the same 10 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with FieldEdge? No. Cotlet is independent and not affiliated with FieldEdge. --- 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.