Skip to main content
Glama

clone_group_repositories

Clone all repositories from a GitLab group by providing the group ID and optional base path.

Instructions

Clone all repositories from a GitLab group.

Args:
    group_id: GitLab group ID
    base_path: Base directory for cloned repos (default: ./repos)
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYes
base_pathNo./repos
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `clone_group_repositories` tool handler function. It fetches all projects from a GitLab group via the GitLab API, then clones each repository using `git clone` via subprocess. Returns a summary of successful and failed clones.
    @mcp.tool()
    async def clone_group_repositories(group_id: int, base_path: str = "./repos", token: str = None, ctx=None) -> str:
        """Clone all repositories from a GitLab group.
        
        Args:
            group_id: GitLab group ID
            base_path: Base directory for cloned repos (default: ./repos)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        import subprocess
        import os as os_module
        
        # Get group projects
        projects_data = await make_gitlab_request(f"/groups/{group_id}/projects?per_page=100", ctx=ctx, token=token)
        
        if isinstance(projects_data, dict) and "error" in projects_data:
            return f"Error getting group projects: {projects_data['error']}"
        
        if not projects_data:
            return "No projects found in group"
        
        # Create base directory
        try:
            os_module.makedirs(base_path, exist_ok=True)
        except Exception as e:
            return f"Error creating base directory: {str(e)}"
        
        cloned = []
        failed = []
        # Use the provided token or fall back to environment variable
        clone_token = token or os_module.getenv("GITLAB_TOKEN")
        
        for project in projects_data:
            try:
                clone_url = project['http_url_to_repo']
                if clone_token:
                    clone_url = clone_url.replace("https://", f"https://gitlab-ci-token:{clone_token}@")
                
                local_path = f"{base_path}/{project['name']}"
                
                result = subprocess.run(
                    ["git", "clone", clone_url, local_path],
                    capture_output=True,
                    text=True,
                    timeout=300
                )
                
                if result.returncode == 0:
                    cloned.append(project['name'])
                else:
                    failed.append(f"{project['name']}: {result.stderr.strip()}")
                    
            except Exception as e:
                failed.append(f"{project['name']}: {str(e)}")
        
        result_msg = f"Cloned {len(cloned)} repositories to {base_path}\n"
        if cloned:
            result_msg += f"\nSuccessful: {', '.join(cloned)}"
        if failed:
            result_msg += f"\nFailed: {'; '.join(failed)}"
        
        return result_msg
  • Registration of the tool via @mcp.tool() decorator on line 1032.
    @mcp.tool()
    async def clone_group_repositories(group_id: int, base_path: str = "./repos", token: str = None, ctx=None) -> str:
  • The `make_gitlab_request` helper function that is used by `clone_group_repositories` to call the GitLab API for fetching group projects.
    async def make_gitlab_request(endpoint: str, method: str = "GET", data: dict = None, ctx=None, token: str = None) -> dict[str, Any] | None:
        """Make a request to GitLab API with proper error handling."""
        # Priority: 1. Explicit token parameter, 2. Context headers, 3. Environment variable
        
        # If no explicit token provided, try to get from context
        if not token and ctx and hasattr(ctx, 'request_context') and ctx.request_context:
            # Try to get from request headers
            if hasattr(ctx.request_context, 'headers'):
                token = ctx.request_context.headers.get('GITLAB_TOKEN')
        
        # Fallback to environment variable
        if not token:
            token = os.getenv("GITLAB_TOKEN")
        
        if not token:
            return {"error": "GitLab token not provided. Please provide a token parameter, GITLAB_TOKEN in the request headers, or set the environment variable."}
        
        # Get GitLab URL (from context or environment)
        gitlab_url = os.getenv("GITLAB_URL", "https://gitlab.com")
        
        headers = {
            "PRIVATE-TOKEN": token,
            "Content-Type": "application/json"
        }
        
        url = f"{gitlab_url}/api/v4{endpoint}"
        
        async with httpx.AsyncClient() as client:
            try:
                if method == "GET":
                    response = await client.get(url, headers=headers, timeout=30.0)
                elif method == "POST":
                    response = await client.post(url, headers=headers, json=data, timeout=30.0)
                elif method == "PUT":
                    response = await client.put(url, headers=headers, json=data, timeout=30.0)
                elif method == "DELETE":
                    response = await client.delete(url, headers=headers, timeout=30.0)
                
                response.raise_for_status()
                return response.json() if response.content else {"success": True}
            except Exception as e:
                return {"error": str(e)}
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description must fully disclose behaviors. It fails to mention side effects like directory creation, overwriting, error handling for invalid group IDs, or authentication fallback when token is omitted. The description is overly simplistic for a cloning tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise: one sentence for purpose, then a succinct parameter list. No unnecessary words. Front-loads the main action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema (so return values are handled), the tool has side effects (cloning to disk) that are not addressed. No mention of expected behavior for missing groups, permission issues, or large groups. Context signals show no annotations, increasing the burden on description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so description must compensate. It adds some value: explains that token is optional, includes default for base_path, and clarifies ctx is auto-injected. However, group_id explanation is minimal ('GitLab group ID') and adds little beyond the parameter name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'clone' and the resource 'all repositories from a GitLab group'. It distinguishes from sibling 'clone_repository' by specifying 'all', making the scope unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The purpose implies when to use: for cloning a group's repositories. However, there is no explicit guidance on alternatives or when not to use, such as for single repositories (use clone_repository) or for non-GitLab groups.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/skmprb/gitlab-clone-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server