Claude, ChatGPT, Copilot or Gemini inside bagai, with your permissions
They connect to your account via MCP, with OAuth consent. They read tasks, hours, absences and the calendar, write when you ask them to, and do only what you can do.
Off by default: an administrator turns it on, instance by instance, and it needs a permission that no role has to begin with.
What is MCP?
MCP (Model Context Protocol) is an open standard that lets an AI assistant connect to an application and use its features. bagai supports it: to the assistant, bagai becomes a tool, like a calendar or a document store.
- You don’t have to copy and paste data: the assistant reads it from bagai when it needs it.
- You don’t have to learn commands: just ask the way you’d ask a colleague.
Which assistants can connect
Assistants that support MCP and connect with OAuth consent.
Each assistant has its own rules for external connectors: check that your plan lets you add one.
- Claude
- ChatGPT
- Copilot
- Gemini
- Le Chat
- Cursor
- Command-line assistants
How to connect
Four steps; the first one is done by your administrator.
-
Your administrator turns the feature on
AI assistants start switched off. They’re turned on for your instance, and the administrator gives the ai.connect permission to the roles that need it.
-
Add bagai to your assistant
In the assistant’s connector settings, add bagai with your instance’s address.
-
Give your consent
A bagai page opens: you sign in with your account and authorise the connection. It’s OAuth consent: the assistant never sees your password.
-
Ask
From then on, the assistant works as you: it sees what you see and does what you can do.
It acts as you
The assistant doesn’t have an account of its own: it acts as the person who connected it, with their permissions. If you can’t see your colleagues’ hours, neither can it. If you can’t delete a client, it can’t either.
- It needs the ai.connect permission, which no role has to begin with: your administrator grants it.
- Your role’s visibility applies: if you only see your own tasks, the assistant only sees those.
- The same rules as the forms apply: it won’t close a task with open subtasks, or start a task that’s waiting on a dependency.
- If your account is deactivated, the assistant’s connection stops working too.
What it reads
What it needs to answer a question about your work:
- tasks and task details;
- projects and clients;
- logged hours;
- statistics;
- absences and balance;
- calendar;
- pick lists: people, tags, companies, activity types.
What it writes
The same set of commands as voice, deletions included: tasks, checklists, comments, time and timers, clients, projects, companies, tags, people, absences.
- It writes using names, not internal IDs: “the client Cattaneo Costruzioni”, “the IT support project”, “Giulia Rezzonico”.
- A name that doesn’t match exactly one entry writes nothing. The assistant gets an error explaining what to correct.
- Tasks are referred to by their code (T-142), absence requests by theirs (A-57).
- Before anything that can’t be undone (deleting, approving or rejecting an absence, deactivating a person), bagai tells the assistant to ask you for confirmation.
Example requests
Questions and requests, written the way you’d write to a colleague.
«Which Cattaneo Costruzioni tasks are overdue? Sort them by due date.»
Reads the client’s tasks and sorts them.
«How many hours have we logged on the IT support project this month, against the estimate?»
Reads the logged hours and the project’s estimate.
«Who’s off next week?»
Reads the absence calendar, with your permissions.
«Log 1h 30m on T-142, done yesterday afternoon, and set the task to Done.»
Logs the time and changes the status.
«Here’s the client’s email: open a task for each request, in the Systems maintenance project, due at the end of the month.»
Reads the text you give it and creates the tasks.
«Put together this week’s summary: tasks closed, hours per project, what’s still open.»
Reads tasks, hours and statistics, and writes a summary.
«Request annual leave for me from 21 to 24 December.»
Creates your leave request.
Under control
You always know which assistants are connected, and you can disconnect them whenever you like.
- You see them under Settings → AI assistants, and disconnect them from there.
- After 90 days without use, an assistant disconnects itself.
- A deactivated account also closes its assistants’ connections.
Good to know before you connect one
Two things that depend on the assistant, not on bagai.
- Whatever the assistant reads from bagai becomes part of your conversation with it, and is processed by its provider under the terms of your account with them. Choose your assistant and plan with that in mind.
- An assistant can misunderstand a request. Read what it proposes to do before you confirm, especially when it’s writing.
What it can’t do yet
In development, not yet available:
- correcting an already saved time entry from the assistant;
- reliably recognising the connected person, so tasks can be assigned to them;
- including the task’s project and company in the hours the assistant reads.