gitlab -zed

This MCP server extension integrates GitLab functionality into Zed by exposing a Model Context Protocol (MCP) server that can manage GitLab projects and perform file operations through the editor. It supports both GitLab.com and self-hosted instances via a configurable API URL. Authentication is handled using a personal access token, so you can securely authorize the extension to access your GitLab resources and perform actions such as listing projects, reading and writing repository files, and executing repository operations within Zed. Once running, you can leverage Zed's MCP toolset to discover and invoke the GitLab MCP server's capabilities, including tools for project management and file operations, directly from the chat or commands pane. The optional api URL setting lets you point the server at a self-hosted GitLab instance if needed.

Prerequisites:

• Rust and Cargo installed on your machine
• Git installed
• Access to a Unix-like shell (Linux/macOS) or a compatible environment on Windows

Steps:

1. Clone the repository: git clone https://github.com/your-org/akbxr-gitlab-mcp-zed.git cd akbxr-gitlab-mcp-zed

2. Build in release mode: cargo build --release

3. Run the MCP server: cargo run --release --bin gitlab-mcp-zed

4. Configure the server in your Zed settings to point to this MCP server instance if needed. For example, ensure your agent or extension settings reference the server name defined in the MCP configuration (gitlab-mcp-zed).

Notes:

• The token for GitLab authentication must be provided in Zed's settings under context_servers > mcp-server-gitlab > settings > gitlab_personal_access_token (as described in the README).
• If using a self-hosted GitLab instance, set gitlab_api_url to your instance's API endpoint (e.g., https://your-gitlab-instance.com/api/v4).

Tips and common issues:

• Ensure your GitLab token has the required scopes (api, read_api, read_repository, write_repository) per your needs.
• If you encounter authentication errors, double-check that the token is correctly saved in Zed's settings and that the server has started without runtime errors.
• For self-hosted instances, verify that CORS or network restrictions allow the MCP server to reach the GitLab API.
• The RUST_LOG environment variable can be adjusted to control log verbosity (e.g., info, debug) during troubleshooting.
• If you update the extension from source, rebuild and restart the MCP server to apply changes.