Skip to main content
Glama

fork_project

Fork a GitLab project by providing its ID. Optionally specify a target namespace.

Instructions

Fork a project.

Args:
    project_id: GitLab project ID to fork
    namespace: Target namespace (optional)
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
namespaceNo
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The fork_project tool handler. Accepts a project_id and optional namespace, sends a POST to GitLab's /projects/{id}/fork API, and returns the forked project's name, ID, and web URL.
    @mcp.tool()
    async def fork_project(project_id: int, namespace: str = None, token: str = None, ctx=None) -> str:
        """Fork a project.
        
        Args:
            project_id: GitLab project ID to fork
            namespace: Target namespace (optional)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        data = {}
        if namespace: data["namespace"] = namespace
        
        result = await make_gitlab_request(f"/projects/{project_id}/fork", "POST", data, ctx=ctx, token=token)
        
        if isinstance(result, dict) and "error" in result:
            return f"Error forking project: {result['error']}"
        
        return f"Project forked: {result['name']} (ID: {result['id']})\nURL: {result['web_url']}"
  • The tool is registered via the @mcp.tool() decorator on the fork_project function (FastMCP pattern).
    @mcp.tool()
    async def fork_project(project_id: int, namespace: str = None, token: str = None, ctx=None) -> str:
  • Helper function used by fork_project to make the actual HTTP POST request to the GitLab API.
    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, and description fails to disclose key behaviors: what happens on fork (creates copy under user/namespace), authentication implications if token omitted, or side effects. Minimal detail.

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

Conciseness4/5

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

Short and to the point, uses structured Args block. No extraneous text, though could be more efficient by omitting obvious ctx detail.

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?

Given 4 parameters and many siblings, the description is too sparse. Lacks info on return format, prerequisites (permissions, token necessity), or behavior if namespace omitted. Output schema exists but description adds little.

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

Parameters4/5

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

Schema has 0% description coverage, but the description adds meaningful context: project_id is GitLab ID, namespace target, token as PAT, ctx auto-injected. This compensates for lack of schema comments.

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?

Clearly states 'Fork a project' with a specific verb and resource. Distinguishes from siblings like clone_project, create_project, transfer_project.

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

Usage Guidelines3/5

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

Mentions required project_id and optional namespace and token, but lacks guidance on when to fork vs alternatives like clone or create. No explicit when-not-to-use.

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