[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) # Squire API and MCP server: Let your AI agent run the chair schedule. > Squire has no MCP server, no public API and no developer docs (checked 28 Oct 2026). Its help center covers Mailchimp, QuickBooks and Google bookings, and has no article for developers. Cotlet runs 11 Squire tools hosted, over MCP for agents and REST for scripts. Appointments, barbers, clients, waitlist and reports for your barbershop. 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/squire-api-mcp-server.md#connect) [REST API guide](https://cotlet.dev/integrations/squire-api-mcp-server.md#rest-api) - Free 7-day trial, no card - Unofficial, not affiliated with Squire - Page: https://cotlet.dev/integrations/squire-api-mcp-server ## What can you automate in Squire? - Brief each barber's day at 7 am - Book waitlist clients into gaps - Move bookings when a barber is out - Block time off on the calendar - Monday revenue by barber - Find clients who stopped coming ## Does Squire have an MCP server or an API? - Zapier, n8n and Pipedream have no Squire app. No Zap can book, move or cancel a Squire appointment. - Clients can be exported by hand from Commander, a snapshot that is out of date by the next booking. - getsquire.com answers scripts with a security check page, so even reading Squire's own pages from code fails. | What you need | Commander by hand | Built-in integrations | Cotlet | |---|---|---|---| | Read every barber's day | Yes, one barber at a time | No | Any date range, whole shop | | Book, move and cancel | Yes, by tapping | Clients book via Google | Yes, after your OK | | Work the waitlist | Yes, by hand | No | Reads it, books the match | | Revenue by barber | Reports screen | Sales to QuickBooks | By date range | | Your own AI agent can use it | No | No | Yes, any MCP client | | What it costs on top | Your time | Included | Credits per call | Checked 28 Oct 2026. Sources: [Squire Help Center](https://help.getsquire.com/s/?language=en_US), [Squire: Mailchimp Integration](https://help.getsquire.com/s/article/Mailchimp-Integration?language=en_US), [Squire: Exporting Client Lists](https://help.getsquire.com/s/article/ExportingClientListsShopBarber6239f73d94261?language=en_US), [Squire: Pricing and plans](https://getsquire.com/pricing) ## How does Cotlet connect to Squire? 1. **Sign in to Squire.** 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 Squire password, and no booking, move or cancellation is saved before you approve it. ## Connect Squire 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 Commander yourself.** Make a Cotlet account, open Squire in its Cloud Browser, log in to Commander with your own shop login, then press Enable for agents. 2. **Add the Cotlet address.** Paste https://cotlet.dev/mcp/v1 into your agent as an MCP server or connector. 3. **Approve the connection.** Chat apps send you to a Cotlet sign-in. Code editors, n8n and scripts take an API key from the console. Squire shares one address, `https://cotlet.dev/mcp/v1`, with every other app on your Cotlet account. If you enable Squire after connecting the agent, refresh the connector so the Squire 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: squire_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: squire_write ``` ## How to use the Squire REST API ### Create your Cotlet API key Create a Cotlet API key with access to Squire and its read operations. Store it as `COTLET_API_KEY` in your environment or automation platform's credential store. Connect Squire in Cotlet and enable it for agents. Account access: Your own Squire account (shop owner for shop-wide schedules, clients and reports). ### Make your first Squire API request REST: ``` curl https://cotlet.dev/api/v1/squire/barbers \ -H "Authorization: Bearer $COTLET_API_KEY" ``` ### Read barbers 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": "squire", "tool": "list_barbers", "result": { "barbers": [ { "barber_id": "b_1042", "name": "Marcus Hill" }, { "barber_id": "b_1043", "name": "Luis Ortega" }, { "barber_id": "b_1044", "name": "Dev Patel" } ] } } ``` Returns each barber with id and name. Use the ids in the appointment tools. Reads the team as your signed-in account sees it in Commander. Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination. ### Squire workflows for agents and automations | Tool | Connect through | Example workflow | |---|---|---| | n8n | HTTP Request | List appointments for a day or a date range, optionally for one barber. Use `list_appointments` in your configured business report. | | Make | HTTP > Make a request | List clients on the shop's waitlist. Use `list_waitlist` in your configured business report. | | Python or Node.js | REST API | Read revenue and client retention from the Reporting Dashboard for a date range. Use `get_revenue_report` in your configured business report. | Send `Authorization: Bearer ` in request headers. You configure the schedule, destination and record comparisons. Cotlet reads Squire; 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/squire-api-mcp-server.md#tools) lists operations and inputs. The [REST API guide](https://cotlet.dev/docs/api.md) explains authentication, errors and approvals. ## Squire API endpoints and MCP tools ### Barbers and service menu Barber and service ids feed every booking tool. A barber who offers only part of the menu gets only those services. - **List barbers** (`list_barbers`, read): List the barbers on your shop's team. - **List services** (`list_services`, read): List the services on your shop's service menu. ### Appointments Times are in the shop's time zone. A slot that is booked or blocked fails with SLOT_TAKEN and nothing changes. - **List appointments** (`list_appointments`, read): List appointments for a day or a date range, optionally for one barber. - **Book appointment** (`create_appointment`, write, asks first): Book an appointment for a client with a barber. - **Reschedule appointment** (`reschedule_appointment`, write, asks first): Move an appointment to a new time or another barber. - **Cancel appointment** (`cancel_appointment`, write, asks first): Cancel a client's appointment. ### Blocked time A block keeps clients from booking the window but leaves bookings already in it alone. - **Block time** (`block_time`, write): Block a barber's calendar for a time window. - **Remove block** (`remove_block`, write): Remove a blocked time window from a barber's calendar. ### Wait List Squire lists the Wait List under its PRO plan; on other plans the list comes back empty. Squire tells the waiting client about an opening itself. - **List the waitlist** (`list_waitlist`, read): List clients on the shop's waitlist. ### Clients and reports Phone and email come back only when you ask for them. Revenue is in the shop's currency. - **List clients** (`list_clients`, read): List or search your shop's clients. - **Get revenue report** (`get_revenue_report`, read): Read revenue and client retention from the Reporting Dashboard for a date range. Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/squire-api-mcp-server#tools ## Who can see my Squire session, and how do I revoke it? - **What we store.** Your logged-in Commander profile, AES-256-GCM encrypted, in Finland. Never the password. - **What your agent gets.** 11 Squire tools. No cookie, no login. - **What the session sees.** What your Commander login sees: the whole shop for an owner, one chair for a barber. - **What no tool touches.** Checkout, cards on file, tips, deposits, booth rent and payouts. - **If Squire asks for a code.** You type it in yourself. We never do. - **How to cut access.** Disable for agents, reset the browser or delete the key. The next call fails. Client phone numbers and emails sit in the same Commander login, so give the agent a Squire user that sees only what it needs. The Cotlet site has 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 Squire's terms? Account safety We could not quote Squire's terms: on 28 Oct 2026 getsquire.com, its terms page included, answered our reader with a security check page meant to stop bots. A company that screens bots on its own site may also watch for them in Commander. Open the terms in your own browser and look for rules on bots, automated access and shared logins before you connect. Many booking apps we checked this month ban exactly that, and losing the account would cost you the booking history your shop runs on. You decide whether that risk is worth it. Cotlet keeps the Squire tools to the work a front desk does by hand. How we keep your account looking like you: - Your own Commander login, typed in by you, never shared - One Cloud Browser with a steady IP and cookies, like the shop iPad - Bookings, moves and cancellations wait for your OK - No tool touches checkout, tips, deposits or payouts - If Squire objects, we pause the Squire tools for everyone within 24 h > When a whole day moves, let the agent go one booking at a time, so each client hears about a single change. ## What happens when Squire changes? - **12 h** between tests of the Squire schedule, waitlist and report reads - **24 h** between tests of bookings and moves a client would notice - **$0** for a call to a Squire tool paused for a fix Squire keeps moving Commander: a new Commander app for phones, SQUIRE Flex, and dozens of help articles updated on 5 Oct 2026. When a screen moves, we repair the tool and its name stays the same. [status.cotlet.dev](https://status.cotlet.dev) checks the site, console and API every 3 minutes. ## Approvals, undo and mistakes 1. **Reads the sick barber's day.** Every booking with client, services, start and end. 2. **Finds a free chair.** Another barber with the same time open and the same services on the menu. 3. **Waits for your OK.** Each move waits in your Cotlet console, old and new barber side by side. 4. **Reports what is left.** Moved bookings with their new barber, and the ones no chair could take. | Action | Undo | |---|---| | Book an appointment | Cancel it; Squire may already have sent the confirmation | | Reschedule an appointment | Move it back; the client may hear about both changes | | Cancel an appointment | Book it again; a no-show or late fee is never charged by a tool | | Block time | Remove the block | | Remove a block | Block the window again | 3 of the 5 write tools ask first. block_time and remove_block run at once, because a block reaches no client and undoes in one call. Reads run at once too. For a scheduled run you can switch the wait off per tool. > A block does not clear the bookings already in its window. Ask the agent to list them first. MCP call: ``` { "name": "block_time", "arguments": { "barber_id": "b_1044", "start": "2026-11-06T13:00:00", "end": "2026-11-06T17:00:00" } } ``` REST: ``` curl -X POST https://cotlet.dev/api/v1/squire/barbers/b_1044/time/block \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"start":"2026-11-06T13:00:00","end":"2026-11-06T17:00:00"}' ``` Response: ``` { "block_id": "k_771", "barber": "Dev Patel", "start": "2026-11-06T13:00:00", "end": "2026-11-06T17:00:00" } ``` A shop script, a sheet or a nightly job can call the same tools over REST at `/api/v1/squire`, with one key and one price. A barber login that cannot open reports gets an error from get_revenue_report, and a failed call costs nothing. Each tool row above shows its REST path. ## How much does the Squire MCP server cost? **About $18 a month** for one shop with 4 barbers, 3,080 credits. Your Squire plan is billed by Squire as before. | Job | Calls | Credits | |---|---|---| | Morning brief, every barber's day | 2 × 26 | 520 | | Waitlist clients into open slots | 3 × 20 | 600 | | A barber out sick, 8 clients moved | 10 × 2 | 200 | | Time off blocked on the calendar | 2 × 6 | 120 | | Monday revenue by barber | 1 × 4 | 40 | | Clients gone 60 days, a few pages | 5 × 2 | 100 | | Cloud Browser, 30 days | | 1,500 | | Total | | 3,080 | - Free 7-day trial, no card - 10 credits per successful call, MCP or REST - 50 credits a day for the Cloud Browser - One price for every barber in the shop The month is our example: 4 barbers, 26 open days, a brief each morning, 20 waitlist days, two sick days and four Monday reports. A full-time barber cuts 8 to 12 heads a day, so the shop sees about 1,000 bookings a month; credits count calls, not bookings. Dollars at the $29 pack rate. ## Squire MCP server on GitHub, Zapier or hosted: which to use | Option | What it does | Where it stops | |---|---|---| | GitHub | No server for Squire barbershops. Repos named squire-mcp are coding tools of the same name, with 0 stars. | Nothing to install. | | Zapier, n8n, Pipedream | No Squire app on any of the three. | No trigger or action to build on. | | Google bookings in Squire | Clients book your barbers from Google search and Maps. | Client side only; your agent cannot use it. | | Exporting client lists | A client file from Commander, by hand. | A snapshot; no booking, no schedule. | If clients only need to find you, Google bookings and the Book Now buttons are free in Squire. If your own agent should read the chairs, work the waitlist, move bookings and send the revenue, Cotlet does that hosted. ## Who runs Cotlet Cotlet belongs to Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273) and working since 2019. Its founders are Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Squire tools go to contact@cotlet.dev. ## Squire API and MCP: questions ### How do I get access? Sign up free at https://cotlet.dev, open Squire under Integrations in the console and log in to Commander in its Cloud Browser. The trial starts with your first app and asks for no card. ### How do I connect Squire to ChatGPT or Claude? Sign up at cotlet.dev, log in to Squire 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 Squire account through Cotlet, in their phone apps too. ### What can ChatGPT do in Squire? With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Squire: morning schedule brief; move a barber\; block time off for a barber. You ask in plain words, and anything that reaches other people waits for your OK first. ### Which Squire plan do I need? Cotlet works in your own Squire account, so it can only do what your plan shows in Commander. Squire's pricing page lists the waitlist and multiple barber accounts under its PRO plan and the Reporting Dashboard from the first plan (checked 28 Oct 2026). Prices differ by region. ### Can it take payments or issue refunds? No. Payments, payouts, rent collection and card processing stay in Squire. The tools book, move and cancel appointments and read reports. ### Does it work for an independent barber? Yes. Squire has accounts for independent barbers, and the tools then see your own chair: your bookings, blocks, clients and revenue. ### Is the MCP server different from the REST API? Only the way in differs. Both carry the same 11 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and sheets use REST. ### Is Cotlet affiliated with Squire? No. Cotlet is independent and not affiliated with Squire. ### Can I use the Squire 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.