Connect your AI assistant

An assistant connected to ChecklistSquad does what you would do on your phone, from a sentence. "Start the Friday close from the Bar Close template and give the till count to Sam." "Who still has open steps on Room 12?" "Jordan is out today, move everything he holds to Priya." The checklist, the assignment and the activity are the same ones the app shows, and the people you assign see the work on their phones as usual.

It works through MCP, the open protocol that Claude, ChatGPT and Claude Code use to connect to tools. ChecklistSquad is the server. There is nothing to install and no extra plan: connecting is free on every plan.

What you need

• A ChecklistSquad account in an organization. The assistant acts as you, so it can start checklists if you can, and it cannot if you cannot.
• One of these clients: Claude (web or desktop), Claude Code, or ChatGPT with connectors turned on.
• The server address: https://api.checklistsquad.com/mcp.

Connect

Claude

1. Open Settings, then Connectors, and choose Add custom connector.
2. Paste https://api.checklistsquad.com/mcp as the server address and save.
3. Claude opens a ChecklistSquad sign-in. Sign in with your email code, and allow the connection on the consent screen. The screen names what the assistant may do: read your checklists, and change them.
4. Back in Claude, the ChecklistSquad tools are on. Ask it "who am I in ChecklistSquad?" to see it answer with your name and organization.

Claude Code

Run this once in a terminal, then complete the sign-in it opens in your browser:

claude mcp add checklistsquad --transport http https://api.checklistsquad.com/mcp

ChatGPT

In Settings, open Connectors and add a custom connector with the same address. ChatGPT registers itself with ChecklistSquad the first time, then opens the same sign-in and consent screen as Claude.

What it can do

Each of these is one tool the assistant calls. The tools reference lists all of them.

• Start a checklist from a template and hand it out in one go. Sections and steps go to a named person, a squad, everyone in the organization, or an email address. An email that is not a member yet gets an invitation, and the section waits for them.
• Assign and reassign. Give a whole checklist, a section or a step to someone, or move everything one person holds to another, on one checklist or on every open one.
• Look things up. Your templates, your people and squads, a checklist's sections and who holds each, the open steps assigned to you, and the checklists matching words, a status, a holder or a date.
• Do a step. Tick it with the answers its fields need, or mark it open, blocked or skipped with a reason.
• Finish a checklist at any point, and hear which steps were still open.
• Read the history of a checklist: who did what, when, and through which assistant, when you ask for it.
• Draft a template. Describe the procedure and the assistant composes sections, steps and fields, which ChecklistSquad checks with the same rules the app uses before saving it to your library.

What it will not do

• Delete anything. There is no tool for it.
• Invite people without giving them work, form squads, or change who is a member. Those stay in the app's admin screens.
• Take photos or capture signatures. Steps that need them are done on the phone; the assistant says so.
• Guess. If "Priya" could be two people, it comes back with both and asks. If it cannot find a section, it says which sections exist. Nothing is created until every name resolves.

How it stays safe

• Your access, no more. The assistant signs in as you with a token issued by ChecklistSquad. Every action is checked against your own permissions on the exact checklist, section or step, the same check the app runs. An assistant cannot see a checklist you cannot see.
• Preview before it acts. The assistant can ask ChecklistSquad for the plan without saving: which section would go to whom, who would be invited. Ask it to "show me the plan first" and it will.
• Read-only connections. When you connect, you may allow reading only. The assistant can then answer questions but every change is refused with "This connection is read-only."
• It shows in the activity. Everything done through an assistant is recorded as you, via that assistant: "Alex via Claude assigned Bar breakdown to Priya." Your team sees it the same way they see anything else.
• Disconnect any time from the client's settings. ChecklistSquad keeps nothing the client needs to reconnect; the next connection signs in again.

Things to say

• "Start the event close checklist for Saturday's gala. Bar to Priya, load-out to the stage crew, I will do the final walk."
• "What is open on Room 12, and who has it?"
• "Give everything Jordan holds this week to Sam."
• "Mark the walk-in temperature step done on tonight's close. It was 36 degrees."
• "Did anyone take the fridge photo on the Friday close?"
• "Make me a template for opening the café: unlock, lights, espresso machine warm-up with a temperature, pastry delivery count, float count."