Pull requests, issues, and repo activity in the channel. 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. GitHub replies in the thread so the whole team sees the result.
These are examples of the kind of request to try. What GitHub can do depends on your GitHub account and permissions.
Direct channel app. GitHub also has a direct connection. Open a channel, choose Apps and Agents from the header menu, then Add app (direct connection), and GitHub events land in that channel as they happen.
Read more in the help centre: talk to an installed app, the MCP catalog and installing a channel app.
FabricLoop connects to the GitHub MCP server for you, so there is nothing to paste. The endpoint is published here for reference and for debugging.
https://api.githubcopilot.com/mcp/
The GitHub MCP server is at https://api.githubcopilot.com/mcp/. FabricLoop connects to it for you when an admin enables GitHub, so you do not paste the URL anywhere.
An admin enables GitHub from the Apps tab under MCP and each person connects their own GitHub account. Then select GitHub in the left nav or in Messages to chat with it in its own channel, or type @ in any channel, pick GitHub and ask in plain language. In a channel it replies in the thread.
GitHub replies in the channel thread, so everyone in that channel sees the answer. It uses the connecting person's GitHub 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