MCP.so
Sign In

GitLab MCP Server Extension for Zed

@akbxr

Repository

About GitLab MCP Server Extension for Zed

Gitlab MCP Server for Zed

#mcp#mcp-server

Basic information

Category

Version Control

Runtime

rust

Transports

stdio

Publisher

akbxr

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is GitLab MCP Server Extension for Zed?

It integrates the Model Context Protocol (MCP) server for GitLab into the Zed editor, enabling project management and file operations through the GitLab API. Designed for Zed users who want to interact with GitLab directly within their editor.

How to use GitLab MCP Server Extension for Zed?

Install via Zed’s extension system (Zed > Extensions or command palette). Configure your personal access token in settings.json under context_server > mcp-server-gitlab > settings. For self-hosted GitLab, add a gitlab_api_url. To use in agent mode, enable the server in agent settings and in the assistant profile under tools.

Key features of GitLab MCP Server Extension for Zed

  • Seamless integration with GitLab API for project management and file operations.
  • Support for both gitlab.com and self-hosted GitLab instances via optional API URL.
  • Automatic authentication using GitLab personal access tokens.
  • Agent mode support for AI-assisted interactions within Zed.

Use cases of GitLab MCP Server Extension for Zed

  • Manage GitLab projects and repositories from within the Zed editor.
  • Perform file operations (read/write) on GitLab-hosted repositories.
  • Use with Zed’s agent mode for context-aware AI assistance in GitLab tasks.

FAQ from GitLab MCP Server Extension for Zed

How do I authenticate with GitLab?

You need to provide a GitLab Personal Access Token in your settings.json under gitlab_personal_access_token. The token must have appropriate scopes (e.g., api for full access, read_api for read-only).

Can I use a self-hosted GitLab instance?

Yes. Set the optional gitlab_api_url setting to the API URL of your self-hosted instance (e.g., https://your-gitlab-instance.com/api/v4).

How do I enable this server in agent mode?

Open Zed’s Agent settings, enable the GitLab MCP server (ensure the status shows a green dot; if red, check your token). Then in the chat section, click Write|Ask > tools, and enable the GitLab MCP server.

What scopes does my personal access token need?

The README recommends selecting scopes: api (full API access), read_api (read-only), and optionally read_repository and write_repository for repository operations.

How can I build from source?

Ensure Rust and Cargo are installed, clone the repository, and run cargo build --release.

Comments

More Version Control MCP servers

Atlassian Data Center MCP

b1ff

MCP servers for the Atlassian products (Bitbucket, Confluence, JIRA) of the Data Center version

81

Bitbucket MCP

MatanYemini

Bitbucket MCP - A Model Context Protocol (MCP) server for integrating with Bitbucket Cloud and Server APIs

149

Jira MCP

nguyenvanduocit

A Go-based MCP (Model Control Protocol) connector for Jira that enables AI assistants like Claude to interact with Atlassian Jira. This tool provides a seamless interface for AI models to perform common Jira operations including issue management, sprint planning, and workflow tra

92

GitLab

modelcontextprotocol

Model Context Protocol Servers

88.1K

Atlassian Jira MCP Server

aashari

Node.js/TypeScript MCP server for Atlassian Jira. Equips AI systems (LLMs) with tools to list/get projects, search/get issues (using JQL/ID), and view dev info (commits, PRs). Connects AI capabilities directly into Jira project management and issue tracking workflows.

72