[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) # SingleOps MCP server: Let your AI agent run the SingleOps office. > SingleOps has no MCP server, no ChatGPT or Claude app and no Zapier app. Its API only enters leads: "It is not a general-purpose job-creation or read/write API" (SingleOps help, checked 9 Nov 2026). Cotlet runs 6 SingleOps tools hosted, over MCP for agents and REST for scripts, in your own SingleOps login. Your AI agent logs calls as leads, follows up open proposals, fills the crews' schedule and chases unpaid invoices. Sign in to SingleOps once in your own Cloud Browser. No API token, no developer. - Free 7-day trial, no card - Unofficial, not affiliated with SingleOps - Page: https://cotlet.dev/integrations/singleops-api-mcp-server ## What can your AI agent do in SingleOps? - Log calls as leads - Follow up open proposals - Schedule crew visits - Chase unpaid invoices - Look up a property's history - See what is left to schedule ## Does SingleOps have an MCP server or an API? - The SingleOps API token comes by email to support, one per account. - SingleOps has no native Zapier integration. - SingleOps has no connector in the ChatGPT apps directory or in Claude. | What you need | SingleOps API | By hand | Cotlet | |---|---|---|---| | Create leads | Yes, with a token | Yes | Yes | | Proposals and jobs | No | Yes, one by one | Yes | | Schedule visits | No | Yes, one by one | Yes, after your OK | | Ask in ChatGPT or Claude | No | No | Yes | | Developer needed | Yes | No | No | Checked 8 Nov 2026. Sources: [SingleOps help: Lead Entry API](https://intercom.help/singleops-49bd59/en/articles/15938604-lead-entry-api), [SingleOps by Granum](https://granum.com/singleops/), [SingleOps help: scheduling visits and tasks](https://intercom.help/singleops-49bd59/en/articles/15938537-scheduling-visits-tasks) ## How does the SingleOps MCP server work? 1. **Sign in to SingleOps.** 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 SingleOps password, and no visit is scheduled until you approve it. ## How to connect SingleOps to your AI agent 1. **Sign in to SingleOps in a Cloud Browser.** Create a Cotlet account, open SingleOps in its Cloud Browser, sign in with your SingleOps 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. SingleOps shares the address `https://cotlet.dev/mcp/v1` with every other app you enable, so one connector covers them all. Turned SingleOps on after connecting? Refresh the connector and the 6 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: singleops_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: singleops_write ``` ## All 6 SingleOps MCP tools ### Clients and leads Search by name, address and phone. New leads reach no one, so they run at once. - **List clients** (`list_clients`, read): Clients, searchable by name, address or phone. - **Create lead** (`create_lead`, write): Creates a lead for a new or existing client. ### Proposals and jobs Open proposals by age, accepted jobs with work left to schedule. Scheduling a visit waits for your OK. - **List proposals** (`list_proposals`, read): Proposals by status, with total and age. - **List jobs** (`list_jobs`, read): Accepted jobs with visits scheduled or still to schedule. - **Schedule visit** (`schedule_visit`, write, asks first): Schedules a visit for a job with a crew. ### Invoices Unpaid invoices by days past due. Payments stay in SingleOps. - **List unpaid invoices** (`list_unpaid_invoices`, read): Invoices with a balance, oldest first. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/singleops-api-mcp-server#tools ## Who can see my SingleOps session, and how do I revoke it? - **What we store.** Your signed-in SingleOps profile, AES-256-GCM encrypted, in Finland. No password. - **What your agent gets.** The 6 SingleOps tools, never the session cookie. - **What the session sees.** What your login sees: clients, leads, proposals, jobs, invoices. - **What no tool touches.** Payments, route optimization, timesheets, pricing, deletes. - **If SingleOps 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 SingleOps 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 SingleOps changes? - **12 h** between tests of the SingleOps reads - **24 h** between tests of sends a customer would notice - **$0** for a call to a SingleOps tool paused for repair When SingleOps moves a button on a job or renames a page, 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. **Finds jobs to schedule.** Accepted, nothing booked yet. 2. **Checks the crew's day.** On the date you name. 3. **Proposes the visit.** With crew and date. 4. **Waits, then schedules.** The visit shows up in your Cotlet console first. | Action | Undo | |---|---| | Create a lead | Yes, reject or edit it in SingleOps | | Schedule a visit | Yes, move or remove it in Scheduling | 1 of 6 tools ask first: schedule_visit. New leads reach no customer, so they run at once. You can turn the wait off per tool once you trust a routine. MCP call: ``` { "name": "create_lead", "arguments": { "name": "Dr. Alan Pierce", "address": "88 Lake Boone Trail, Raleigh, NC", "request": "Remove dead oak by driveway" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/singleops/leads \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"name":"Dr. Alan Pierce","address":"88 Lake Boone Trail, Raleigh, NC","request":"Remove dead oak by driveway"}' ``` Response: ``` { "lead_id": "LD-8812", "client": "Dr. Alan Pierce", "request": "Remove dead oak by driveway", "status": "New" } ``` A cron job or n8n flow can call the same tools over REST at `/api/v1/singleops` with the same key and price, in JSON. Failed calls are free. Each tool row above shows its REST path. ## How much does the SingleOps MCP server cost? **About $25 a month** for a tree care company with 3 crews, 4,380 credits. Your SingleOps plan stays as it is. | Job | Calls | Credits | |---|---|---| | Lead logged from a call | 2 × 60 | 1,200 | | Proposals followed up, weekly | 1 × 4 | 40 | | Visit scheduled | 2 × 50 | 1,000 | | Unpaid invoices, weekly | 1 × 4 | 40 | | Property looked up | 3 × 20 | 600 | | Cloud Browser, 30 days | | 1,500 | | Total | | 4,380 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - Works on any SingleOps plan SingleOps publishes no job counts, so the month is our example. Dollars at the $29 pack rate. ## SingleOps MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | Lead Entry API | Web form leads straight into SingleOps. | Leads only; token from support; a developer wires it up. | | Third-party MCP servers | Community servers on GitHub. | Built on the same lead-only API; you run them yourself. | | By hand | Every screen of SingleOps, one job at a time. | Your office's time. | If you only need web form leads in SingleOps, the Lead Entry API does that. To follow up proposals, schedule crews and chase invoices from ChatGPT or Claude this week, Cotlet works in the SingleOps 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 SingleOps tools go to contact@cotlet.dev. ## SingleOps MCP server: questions ### How do I get access? Sign up free at https://cotlet.dev, open SingleOps under Integrations in the console and sign in to SingleOps in its Cloud Browser. The trial starts with your first app and asks for no card. ### How do I connect SingleOps to ChatGPT or Claude? Sign up at cotlet.dev, log in to SingleOps 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 SingleOps account through Cotlet, in their phone apps too. ### What can ChatGPT do in SingleOps? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in SingleOps: log calls as leads; follow up proposals; fill next week. 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 SingleOps? No. SingleOps has no ChatGPT or Claude connector of its own and SingleOps has no official MCP server (checked 9 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 leads in SingleOps? Yes, with Cotlet. ChatGPT logs calls and emails as SingleOps leads with the property and request, ready for your estimator. ### Can ChatGPT follow up proposals in SingleOps? Yes, with Cotlet. ChatGPT lists proposals sent a while ago that are still open, with their totals, so your office knows whom to call. ### Can ChatGPT schedule visits in SingleOps? Yes, with Cotlet. ChatGPT finds accepted jobs with nothing scheduled and books visits with the crew you name, after your OK. ### Is this the same SingleOps now under Granum? Yes. SingleOps is now SingleOps by Granum, with the same app at app.singleops.com. Cotlet works in that app with your own login. ### Is the MCP server different from the REST API? Only in how it is called. Both carry the same 6 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST. ### Is Cotlet affiliated with SingleOps? No. Cotlet is independent and not affiliated with SingleOps or its owner Granum. --- 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.