Use SquadBear from ChatGPT — the MCP integration
Connect ChatGPT to SquadBear over MCP and handle leave, time, team health and core HR in plain language, within your own permissions.
SquadBear's MCP server is client-agnostic: it's the same endpoint whether you connect Claude, ChatGPT or any other MCP-capable assistant. Point ChatGPT at it, sign in, approve the scopes, and your team can run SquadBear by simply asking.
What you can do with SquadBear in ChatGPT
Everything you could do in the app, ChatGPT can do on your behalf: check and book leave, log time and pull reports, run team-health checks, manage employee records, onboard after you've hired someone, chase a policy acknowledgment. The connector exposes over 100 tools across leave, time tracking, team health and core HR — all bounded by your own permissions, so answers come from your real data rather than a guess.
What it does not do: emotion or mood inference, candidate screening, ranking people for hire/fire/promote, or automatic people decisions off a score. ChatGPT is the assistant; SquadBear is the system of record and the permission boundary.
Ask it to run whoami first. It should reply with your role, manager, teams and holiday calendar — confirmation the connection resolved to you.
How to connect ChatGPT to SquadBear
The mechanics are the same for every MCP client; only the menu names differ:
- Your MCP endpoint is
https://app.squadbear.com/mcp— also shown on the in-app Agents page. - In ChatGPT, add SquadBear as a custom MCP connector (available on plans that support custom connectors) and paste the endpoint.
- Sign in to SquadBear when prompted, then approve the scopes the connection may use — for example
leave:read,time:write,health:write. - Enable the SquadBear connector in your conversation and start asking.
Because the connector protocol is shared, the Connect Claude to SquadBear guide is the canonical reference for the endpoint, the scope list and how permissions resolve — the same details apply to ChatGPT.
Permissions and audit
A connected assistant acts as you, with your role's permissions and no more. The scopes you approve are frozen into the connection; widen them by disconnecting and reconnecting. Every action is recorded in the same audit trail as the web app and REST API — one permission and audit path for the UI, the API and the assistant alike.
Prompts to try
Related
- Connect an agent to SquadBear — the shared MCP setup guide
- The developer API — for code, not chat
- Use SquadBear from Claude
Frequently asked questions
Does SquadBear work with ChatGPT?
Yes. SquadBear exposes a standard MCP server, so any MCP-capable client — including ChatGPT on plans that support custom connectors — can operate the product. It's the same server Claude connects to.
Is it a different integration from the Claude one?
No. There's one MCP endpoint and one permission model. Whichever assistant you connect, it acts as you, with the scopes you approve, and every action is audited the same way.
Can ChatGPT see data I can't?
No. The connection resolves to your account and carries your role's permissions. An assistant can only ever do what you could do yourself in the web app.
Does ChatGPT decide employment outcomes?
No. It operates SquadBear tools under your permissions — draft, fetch and file. No candidate screening, no performance scoring for promotion or termination, no emotion inference. Humans stay in command of people decisions.
Do I need to write any code?
No. Connecting an assistant over MCP is a chat-based setup, no code required. For scripts and backend jobs, use the REST API with an sbk_ API key instead.
Start free in minutes
The full product on every plan, including free for up to 5 people. Connect your assistant and try it on your own data.
Start free