{"id":"clm_D131273D4C75","entity":"gitlab","predicate":"released","value":"GitLab MCP server","value_json":{"feed":"gitlab-blog","item":"https://about.gitlab.com/blog/mcp-server-ga/","tags":{"v":2,"ai":true,"by":"claude-haiku-5-5","on":"2026-11-06","themes":["connectors","agents","coding"],"release_kind":"developer_tool"},"check":{"on":"2026-11-06","url":"https://about.gitlab.com/blog/mcp-server-ga/","pages":1,"quote":"The GitLab MCP server, now generally available with GitLab 19.5 , connects your team’s external agents to your entire software lifecycle — from planning through production.","outcome":"checked"},"evidence":"Agents are working across your team's software development lifecycle, but most still operate as separate tools, leaving the context, handoffs, and permissions for your team to stitch together. When your agents use APIs for these disparate tools, they often guess at endpoints and use up their context","extracted_by":"claude-haiku-5-5","primary_source":true},"valid_from":"2026-10-15","valid_to":null,"published":"2026-10-15","recorded":"2026-11-06","citation":{"plain":"AsOf. \"GitLab released: GitLab MCP server\", as of 2026-10-15. Claim clm_D131273D4C75, https://asof.is/claim/clm_D131273D4C75, accessed 2026-11-08. Source: https://about.gitlab.com/blog/mcp-server-ga/.","url":"https://asof.is/claim/clm_D131273D4C75","accessed":"2026-11-08"},"confidence":0.7,"status":"valid","assertable":true,"superseded_by":null,"supersedes":[],"first_seen_at":"2026-11-06T09:43:43.034301+00:00","updated_at":"2026-11-06T13:17:00.53671+00:00","sources":[{"url":"https://about.gitlab.com/blog/mcp-server-ga/","tier":"primary","publisher":"GitLab","published_at":"2026-10-15T00:00:00+00:00"}],"evidence":{"by":"page-read","on":"2026-11-06","quote":"The GitLab MCP server, now generally available with GitLab 19.5 , connects your team’s external agents to your entire software lifecycle — from planning through production.","url":"https://about.gitlab.com/blog/mcp-server-ga/","excerpt":"Agents are working across your team's software development lifecycle, but most still operate as separate tools, leaving the context, handoffs, and permissions for your team to stitch together. When your agents use APIs for these disparate tools, they often guess at endpoints and use up their context"},"legend":{"dates":"valid_from: when the claim took effect (a period figure: the day its period closed). published: the earliest day a source on the record published it (a filing's filing date, a post's date; null when no source carries one). recorded: the day AsOf first held it. A figure can take effect weeks before it is published.","citation":"citation: how to cite the row (plain: one sentence with the value, its as-of date, the claim id and URL, the day answered and the primary source; url: the claim page; accessed: the day answered). APA and BibTeX forms are on the claim page.","why_not":{},"checked_by":{"page-read":"its source page states the value and the date"}}}