MCP Server transfer ownership to AI Teams
Context
In https://gitlab.com/gitlab-org/gitlab/-/issues/540975, unofficial MCP servers were collected to highlight importance of MCP strategy. In https://gitlab.com/gitlab-org/gitlab/-/issues/550760, official MCP server was proposed to highlight urgency of MCP strategy for Enterprise customers. Based on PoC built by AI Leadership and Duo Agent Platform deadlines, newly formed API team was been tasked with designing, implementing, and releasing official MCP server for GitLab by 18.3 to enable the AI roadmap.
This goal was achieved in 18.3, and this issue captures known outstanding tasks and context to enable to transfer of ownership, and future development to take place within the AI teams.
Resources
- Deliver the Experimental phase of an Official G... (&18413 - closed) this epic was created following discussions on approach in https://docs.google.com/document/d/1mryQcmk11x3Zj83hFE-OOdfVv1hk3z8H5YWxxMyzxrA/edit?tab=t.0#heading=h.sat92yr1l3hi
- Discussion about initial tools - #558147 (closed)
- Discussion about current, and possible future architecture - &18759
Outstanding tasks
The 18.3 delivery enabled the Experimental version of MCP Server. Feature Flags are disabled by default.
The following tasks are remaining:
- Update stages.yml to transfer ownership of MCP Server
- Update Docs to transfer ownership !199122 (merged)
- Update https://gitlab.com/gitlab-org/architecture/readiness/-/issues/35 with any new details
- Complete the architectural documents. Due to timelines, we only prepared a draft documentation. Draft availabile
- Work with Product and AppSec to enable by default, and eventually remove the feature flags - https://gitlab.com/gitlab-org/gitlab/-/issues/555942) and https://gitlab.com/gitlab-org/gitlab/-/issues/556448