[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) # RazorSync MCP server: Let your AI agent run the RazorSync office work. > RazorSync has no MCP server and no ChatGPT or Claude app. It documents a JSON API with a "unique token" header, but there is no self-service way to create the token; you contact support (RazorSync help, checked 8 Nov 2026). Cotlet runs 9 RazorSync tools hosted, over MCP for agents and REST for scripts, in your own RazorSync login. Your AI agent turns service requests into work orders, schedules them on your technicians, invoices yesterday's finished jobs and logs the checks. Sign in to RazorSync once in your own Cloud Browser. No token request, no developer. - Free 7-day trial, no card - Unofficial, not affiliated with RazorSync - Page: https://cotlet.dev/integrations/razorsync-api-mcp-server ## What can your AI agent do in RazorSync? - Turn service requests into work orders - Schedule open work orders - Invoice completed work orders - Send invoices to customers - Log checks on the right invoice - List invoices unpaid for 30 days ## Does RazorSync have an MCP server or an API? - Each API request needs your portal name and a token from RazorSync. - The API covers customers, work orders, scheduling, estimates, invoices and payments for your own developer. - RazorSync has no connector in the ChatGPT apps directory or in Claude. | What you need | RazorSync API | By hand | Cotlet | |---|---|---|---| | Customers and work orders | With a token | Yes, one by one | Yes | | Schedule a technician | With a token | Yes, one by one | Yes, after your OK | | Invoice and send | With a token | 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: [RazorSync help: API Documentation](https://help.razorsync.com/api-documentation), [RazorSync help: contact](https://help.razorsync.com/contact-razorsync), [RazorSync pricing](https://www.razorsync.com/pricing/) ## How does the RazorSync MCP server work? 1. **Sign in to RazorSync.** 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 RazorSync password, and no schedule, invoice or payment goes through until you approve it. ## How to connect RazorSync to your AI agent 1. **Sign in to RazorSync in a Cloud Browser.** Create a Cotlet account, open RazorSync in its Cloud Browser, sign in to your company portal with your 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. RazorSync shares the address `https://cotlet.dev/mcp/v1` with every other app you enable, so one connector covers them all. Turned RazorSync 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: razorsync_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: razorsync_write ``` ## All 9 RazorSync MCP tools ### Customers Search matches name, phone, email and address, so a repeat caller is found before a duplicate is made. - **List customers** (`list_customers`, read): Customers, searchable by name, phone, email or address. - **Create customer** (`create_customer`, write): Adds a customer with a service location. ### Work orders and schedule A new work order stays unscheduled until it is put on a technician and a time. 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. - **Schedule work order** (`schedule_work_order`, write, asks first): Assigns a work order to a technician and a time. ### Invoices and payments An invoice is built from the work order and stays unsent until you OK the send. Payments are checks, cash and other manual types; no card is charged. - **List invoices** (`list_invoices`, read): Invoices by status, customer or age, 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/razorsync-api-mcp-server#tools ## Who can see my RazorSync session, and how do I revoke it? - **What we store.** Your signed-in RazorSync profile, AES-256-GCM encrypted, in Finland. No password. - **What your agent gets.** The 9 RazorSync tools, never the session cookie. - **What the session sees.** What your login sees: customers, work orders, prices, invoices. - **What no tool touches.** Card charges, users and permissions, price list edits, deletes. - **If RazorSync 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 RazorSync 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 RazorSync changes? - **12 h** between tests of the RazorSync reads - **24 h** between tests of sends a customer would notice - **$0** for a call to a RazorSync tool paused for repair When RazorSync moves a button on the schedule 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 line items or a return visit booked. 3. **Builds and checks totals.** Each invoice against its work order. 4. **Waits, then sends.** The batch shows up in your Cotlet console first. | Action | Undo | |---|---| | Create a work order | Yes, cancel it in RazorSync | | Schedule a work order | Move it; a message already sent stays sent | | Create an invoice | Yes, edit or void it before sending | | Record a payment | Delete the payment in RazorSync | | Send an invoice | No | 3 of 9 tools ask first: schedule_work_order, send_invoice, record_payment. A new customer, a work order or an unsent 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": "schedule_work_order", "arguments": { "work_order_id": "WO-7790", "technician": "Marcus", "start": "2026-11-13T14:00", "duration_min": 90 } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/razorsync/work-orders/WO-7790/schedule \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"technician":"Marcus","start":"2026-11-13T14:00","duration_min":90}' ``` Response: ``` { "work_order_id": "WO-7790", "technician": "Marcus", "scheduled": "2026-11-13T14:00", "status": "Scheduled" } ``` A cron job or n8n flow can call the same tools over REST at `/api/v1/razorsync` with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path. ## How much does the RazorSync MCP server cost? **About $42 a month** for an appliance repair business with 4 technicians, 7,220 credits. Your RazorSync plan stays as it is. | Job | Calls | Credits | |---|---|---| | Request into a work order | 3 × 50 | 1,500 | | Open work orders scheduled | 4 × 22 | 880 | | Yesterday's jobs invoiced and sent | 13 × 22 | 2,860 | | Unpaid list, weekly | 2 × 4 | 80 | | Checks logged | 2 × 20 | 400 | | Cloud Browser, 30 days | | 1,500 | | Total | | 7,220 | - 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 RazorSync plan RazorSync publishes no job counts, so the month is our example. Dollars at the $29 pack rate. ## RazorSync MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | RazorSync API | Customers, work orders, scheduling and invoices in JSON for your own developer. | Token through support; you build and host the code. | | By hand | Every screen of RazorSync, one record at a time. | Your office time. | If your developer already has a RazorSync token, building on the API is cheaper for simple reads. To open, schedule and invoice work orders by asking in ChatGPT or Claude, Cotlet works in the RazorSync account you already have. ### RazorSync MCP setup on GitHub and PyPI Prefer code? Our public repo has a ready RazorSync 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 RazorSync account. - MCP config for Claude Code, Cursor and Codex - Agent skill and Cursor rules for RazorSync - Clone it and run, Python standard library only - Elastic License 2.0, free in your own business - Code: https://github.com/cotlet-connect/razorsync-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 RazorSync tools go to contact@cotlet.dev. ## RazorSync MCP server: questions ### How do I get access? Sign up free at https://cotlet.dev, open RazorSync under Integrations in the console and sign in to RazorSync in its Cloud Browser. The trial starts with your first app and asks for no card. ### How do I connect RazorSync to ChatGPT or Claude? Sign up at cotlet.dev, log in to RazorSync 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 RazorSync account through Cotlet, in their phone apps too. ### What can ChatGPT do in RazorSync? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in RazorSync: turn service requests into work orders; schedule unscheduled work orders; 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 RazorSync? No. RazorSync has no ChatGPT or Claude connector of its own and RazorSync 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 schedule work orders in RazorSync? Yes, with Cotlet. ChatGPT finds or adds the customer, opens the work order and puts it on a technician's schedule after your OK. ### Can ChatGPT send invoices in RazorSync? Yes, with Cotlet. ChatGPT builds the invoice from the completed work order and emails it to the customer after your OK. ### Do I need a RazorSync API token to use Cotlet? No. Cotlet works through your own RazorSync sign-in, so you skip the support request for a token. It can do what your login can do in RazorSync. ### Can it react when a request comes in? Run it on a schedule, for example every morning at 7 for last night's requests, or ask it when one arrives. Nothing needs to change in RazorSync. ### 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 RazorSync? No. Cotlet is independent and not affiliated with RazorSync. --- 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.