Use GitLab in Slack and Email
GitLab hosts your code: projects, issues, merge requests and CI/CD. Connect the GitLab MCP server to Maito once, and everyone on your team can use GitLab from Slack, by email, or from Claude, ChatGPT, Cursor, Codex, Grok or Muse. Nobody else has to sign in.
- Connects in one click
- Sign in with GitLab
- One connection for the whole team
- Server by GitLab
Updated
What you can ask with GitLab
Dana in Slack
Sam by email
Maito uses GitLab to do the work and replies where you asked.
How to connect GitLab
Open Connections in your workspace and choose Connect next to GitLab. You sign in to GitLab in a new tab, and that's the whole setup. Name the account and choose Workspace under who can use it. That's the only time anyone signs in: your whole team, shared chats and Loops can use GitLab from then on. Or skip ahead and ask for the work: Maito sends you a link if GitLab isn't connected yet.
Connect GitLab
Sign in to GitLab in a new tab to give your agents access.
Connection name
Company GitLab
Who can use this integration?
Workspace
Workspace members and Loops can use this integration’s enabled tools.
Then turn off any tools you don't need. Everything else is on.
Questions
GitLab publishes it at https://gitlab.com/api/v4/mcp, and it signs in with OAuth, so there's no key to copy.
Yes. Connect it to Maito once, then mention Maito in any Slack channel or send it a direct message. The same connection works by email and from Claude, ChatGPT, Cursor, Codex, Grok or Muse.
No. One person connects it once and chooses Workspace. Then everyone in the workspace, shared chats and Loops can use GitLab, without signing in themselves. Choose Only me instead to keep it to your own chats.
No. If a request needs GitLab and it isn't connected yet, your agent sends you a link. Connect it, and the work picks up where it stopped.
Yes. After you connect, turn off any GitLab tools you don't want Maito to use, such as the ones that change data. Tools GitLab adds later stay off until you turn them on.
