Configuring an external MCP server in a teamspace

You can configure an external MCP server in DevOps Loop to connect to external MCP services and make them available to all loops in a teamspace.

You must have completed the following tasks:

  • Ensured that you have administrative privileges in DevOps Loop.
  • Ensured that you must have a valid MCP server endpoint URL.
  1. Navigate to Settings > Installed Integrations.
    The Installed Integrations page is displayed.
  2. Click the MCP tab.
  3. Click Add Server.
    The Add Server pane is displayed.
  4. Enter a name to identify the MCP server in the Name field.
    For example, GitHub MCP Server.
  5. Select the appropriate domain from the Domain list.
    Note: Each MCP server belongs to a Domain. Only one MCP server can be enabled for a Domain at a time. If you are adding a new MCP server to an existing domain, ensure that other MCP servers of the same domain are disabled.
    Note: If you select Others in the Domain list, the MCP server name is used as the domain value for that MCP server.
  6. Enter the MCP server endpoint URL in the Server URL field.
  7. Keep OAuth selected as the Credential Type.
  8. Optional: Enter the client ID in the Client ID field.
  9. Optional: Enter the client secret in the Client Secret field.
  10. Click Save.

    The OAuth authentication window is displayed.

  11. Complete the OAuth authentication process.
    The MCP server is added to DevOps Loop within a teamspace.
  12. Use the toggle switch in the Manage External MCP list to enable the MCP server.
    Note: Newly added MCP servers are disabled, which is the default setting. If AI integration is inactive, the MCP server cannot be enabled.
The MCP server is added to the Manage External MCP list. When the MCP server is enabled, it is available to all loops within the teamspace.
The teamspace members can authenticate and use the MCP server through Loop Genie.