
Search and work with GitLab issues, merge requests, pipelines, and code. Chat with it in its own channel, or @mention it in any channel, and it replies in the thread.
Ask in plain language, with no slash commands. GitLab replies in the thread so the whole team sees the result.
These are examples of the kind of request to try. What GitLab can do depends on your GitLab account and permissions.
Read more in the help center: talk to an installed app, the MCP catalog and installing a channel app.
FabricLoop connects to the GitLab MCP server for you, so there is nothing to paste. The endpoint is published here for reference and for debugging.
https://gitlab.com/api/v4/mcp
The GitLab MCP server is at https://gitlab.com/api/v4/mcp. FabricLoop connects to it for you when an admin enables GitLab, so you do not paste the URL anywhere.
An admin enables GitLab from the Apps tab under MCP and each person connects their own GitLab account. Then select GitLab in the left nav or in Messages to chat with it in its own channel, or type @ in any channel, pick GitLab and ask in plain language. In a channel it replies in the thread.
GitLab replies in the channel thread, so everyone in that channel sees the answer. It uses the connecting person's GitLab permissions, and the connection does not expand anyone's membership in FabricLoop.
Often we can add one within a day. Contact us with what you use.
See all integrations · How apps work in FabricLoop · Need one we don't have? Contact us