## Summary MCP Server is currently Beta with fundamental gaps blocking enterprise adoption. Regulated customers can't enable it without proper controls and compliance capabilities and workflow automation is stymied due to a lack of a robust tooling catalog. Active customer pilots are stalled waiting for missing capabilities. In order to make MCP Server GA, we need to address three critical gaps that prevent enterprises from deploying MCP: 1. **[Tooling Consolidation & Curation](https://gitlab.com/groups/gitlab-org/-/work_items/20222): audit and consolidate existing tools** <br> Rationalizing our sprawling 85+ tool catalog into a curated, high-quality foundation that improves agent effectiveness and eliminates maintenance burden. 2. **[Improved Tool Coverage](https://gitlab.com/groups/gitlab-org/-/work_items/20529): fill tooling gaps** <br> Building the highest-priority tools validated through customer evaluations to enable complete SDLC workflows and unblock active pilots. 3. **[Enterprise Readiness](https://gitlab.com/groups/gitlab-org/-/work_items/21169): add governance** <br> Delivering the controls, visibility, and compliance capabilities that regulated industries require before enabling external AI access to GitLab instances. This plan shifts MCP from Beta to production-ready infrastructure that enterprises can confidently deploy. With robust, comprehensive tooling in place, MCP becomes the foundation powering all GitLab Duo Agent Platform interactions—enabling both external AI integrations and GitLab's native AI capabilities to deliver sophisticated workflow automation.