Skip to content

Feedback on experimental MCP Support in GitLab Duo Agentic Chat

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Overview

This issue is to track feedback on the experimental release of Model Context Protocol (MCP) support in GitLab Duo Agentic Chat for IDE extensions. The general feedback issue for IDE Agentic Chat can be found here: Feedback on experimental GitLab Duo Agentic Chat (#542198).

Since this is an experimental feature, your feedback is valuable in helping us improve it.

What is MCP?

The Model Context Protocol is an open standard that enables our AI assistant to securely connect with external tools and data sources. This means Duo can now interact with databases, APIs, and other services to provide you with more contextual and actionable assistance.

With this release, Duo Agentic Chat acts as an MCP client, enabling it to connect and run tools from MCP servers.

Please, provide feedback ...

Please, feel free to share anything regarding your experiences, suggestions, or issues. We are particularly interested in these aspects:

  • How intuitive is the tool approval workflow? Does it give you enough information to make informed decisions?
  • What types of MCP tools/integrations would be most valuable for your workflow?
  • How does MCP integration improve (or complicate) your experience with Duo Agentic Chat?
  • Are there any security or privacy concerns with the tool approval process?
  • Performance: Do tool executions feel responsive enough?
  • Any bugs - other than the known issues below?
  • Share your successful and unsuccessful use cases with MCP tools.
  • Anything else that you want to tell us?

Known issues:

  • All identified pain points for Agentic Chat in IDE: https://gitlab.com/groups/gitlab-org/-/epics/18173+
  • All the known issues listed for IDE Agentic Chat: #542198
  • Tool approval is required for each execution (no "remember my choice" option yet)
  • Limited documentation on available MCP servers and tools

How to Get Started

  1. Update your VSCode extension to the latest version
  2. Add tools to your
  3. When Duo suggests using a tool, you'll see the new approval dialog
  4. Review the tool and its parameters
  5. Click approve to execute or deny to skip

Tool Approval Workflow

When Duo wants to call a tool:

  • Tool information and arguments can be inspected by the user
  • The user is prompted to review and approve or deny tool executions before they run
  • This ensures you maintain control over what external actions Duo performs on your behalf

Ideas for MCP Tools & Integrations

If you have feedback or ideas for MCP tools to try or integrations to support, please share them here!

Related Issues

Edited by 🤖 GitLab Bot 🤖