SquadBear Is Available in the Gemini App and on the Website
··5 min read
SquadBear is available in the Gemini app and on the Gemini website. Gemini 4 Argon can add it as a custom connector and work in the account you already use at gemini.google.com. It signs in as you. It can see what your role can see, and a write still follows the same rules as the SquadBear web app.
Connect it once
On the Gemini website, or in the Gemini app, open Customize, then Connectors, then + Custom. The server URL is:
https://app.squadbear.com/mcp
Sign in to SquadBear as yourself. The connector comes back as SquadBear, handle @Squadbear, category Custom MCP. Disconnect is on that same page. Add it once. After that it is there on the website and in the app.
Gemini can then ask about leave, time, attendance, team health, and work already assigned to people. Booking leave, logging time, and approving a request follow the same rules as the web app. Erasing someone, publishing a leave policy, changing workspace settings, and starting a process still stop at a review link inside SquadBear. They wait for a browser click. The terminal path is separate and unchanged: Gemini CLI, gemini mcp add, then /mcp auth squadbear.
The three examples below are one Monday on Linden Works, the 38-person workspace on our product screens. The login was Marta Zielińska, admin. Gemini did the reading. Nothing was approved, booked, or changed.
Example: the Friday submitted at 14:17
Four timesheets for 28 September to 4 October were waiting on approval. Three were complete. Marek Ostrowski, Emily Saputra, and Arif Siregar had each logged 2,400 of 2,400 minutes, a full 40 hours.
Karolina Maj, who manages Mobile, had logged 1,920. The gap was a single day. Monday through Thursday she had full days on the iOS release, Android offline mode, and team planning. Friday 2 October was still at zero when she submitted, at 14:17 UTC that same Friday.
Delivery had two sheets that were never submitted. Tomasz Wójcik sat at 1,800 of 2,400 minutes. Filip Kamiński sat at 2,280. The names sort the queue: three approvals, one send-back that cites the empty Friday, and two people who have not signed the week.
The rest of that morning was quiet. No leave request was waiting. No team crossed the coverage line in the next 14 days. One workspace invitation expired the following morning. One attendance exception was open, and it was Marta's own. On 13 October at 18:29 UTC she booked a day of care leave, urlop opiekuńczy, for the 14th. Eleven seconds later she clocked in and never clocked out. The shift was closed after 16 hours, overlapping the leave day, and the review sits with her manager, Magda Król.
A status column would have read "submitted" four times. The conversation named who to approve, who to send back, and who is still logging. Submit is the signature. Close comes later.
Example: the score, the action, and the unbooked days
Delivery, Adam Nowak's team, was the one the health overview flagged. Workload, energy, clarity, and satisfaction had held through the July, August, September, and October runs, at 3.67, 3.67, 4.0, and 3.67. Support moved from 4.57 on 22 September to 3.50 on 6 October, down 1.07 points. Participation moved with it: 7 of 7 through September, then 6 of 8 in October. Adam and Julia Mazur, who joined on 6 October, had not answered that run.
The comments on the run were about the handover. The notes were written. The split of the work was still open. Covering planned leave on top of the mobile work would be too much until that split was agreed. Release preparation had taken two evenings, and someone wanted a quieter week before a holiday.
On 5 October Adam opened a high-priority action from that run: agree cover for Emily Saputra's three days, Tomasz on the customer portal, Arif on mobile questions, due 9 October. On 15 October the action was still open. Emily's profile showed no request, and nothing used.
Read together, that is one Monday sentence. Support dropped, the cover Adam wrote down has not been agreed, and Emily has not booked the days that action was opened to unlock. Whether the comments and the empty balance are the same story is Adam's call. Marta, and Gemini signed in as Marta, see the aggregate and the comments the run already shows an admin. Individual ratings stay hidden. One visible action per run is why the overdue item is the finding, and the score is the reason to open it.
Example: the price of a day, before anyone books it
On-demand leave here, urlop na żądanie, draws on two balances at once. A preview for 15 October, run that afternoon, charged 480 minutes to vacation, leaving 152 hours, and one day to the four-day on-demand cap, leaving three. The workspace cutoff is 08:00 local time, so after that hour the request waits for a manager. This one routed to Magda. The day stayed unbooked.
The same ledger already knew the joiners. Emily, hired in November 2022, holds the full 20 days, 9,600 minutes. Julia, hired on 6 October 2026, received October through December when her profile was created: five days, 2,400 minutes. People on the B2B availability type stay off the employee approval path. A manager granting a contractor's vacation is a record a labour inspector can read as employment. The approve button is the evidence.
A question you can paste
Once SquadBear is connected, this is the Monday question:
Look at timesheets submitted for 28 September to 4 October. Name who submitted a full week, who submitted on Friday with Friday still empty, and who has not submitted. Then read Delivery's latest health run. If Support moved, say whether an open action and an unbooked holiday sit next to that move. Do not approve, book, or change anything.
Start free, then add https://app.squadbear.com/mcp under Customize → Connectors → + Custom. The same URL serves Claude, Grok, Cursor, and Codex. Or ask the demo to walk these three examples on Linden Works before you connect your own workspace.
