Skip to main content
Glama
PhialsBasement

GitHub MCP Server Plus

fork_repository

Create a copy of a GitHub repository to your personal account or organization for development, testing, or contribution purposes.

Instructions

Fork a GitHub repository to your account or specified organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner (username or organization)
repoYesRepository name
organizationNoOptional: organization to fork to (defaults to your personal account)

Implementation Reference

  • The main handler function that forks a GitHub repository by making a POST request to the GitHub API and parsing the response.
    export async function forkRepository(
      owner: string,
      repo: string,
      organization?: string
    ) {
      const url = organization
        ? `https://api.github.com/repos/${owner}/${repo}/forks?organization=${organization}`
        : `https://api.github.com/repos/${owner}/${repo}/forks`;
    
      const response = await githubRequest(url, { method: "POST" });
      return GitHubRepositorySchema.extend({
        parent: GitHubRepositorySchema,
        source: GitHubRepositorySchema,
      }).parse(response);
    }
  • Zod schema defining the input parameters for the fork_repository tool: owner, repo, and optional organization.
    export const ForkRepositorySchema = z.object({
      owner: z.string().describe("Repository owner (username or organization)"),
      repo: z.string().describe("Repository name"),
      organization: z.string().optional().describe("Optional: organization to fork to (defaults to your personal account)"),
    });
  • index.ts:108-112 (registration)
    Tool registration in the list of tools returned by ListToolsRequest, specifying name, description, and input schema.
    {
      name: "fork_repository",
      description: "Fork a GitHub repository to your account or specified organization",
      inputSchema: zodToJsonSchema(repository.ForkRepositorySchema),
    },
  • index.ts:169-175 (registration)
    Handler case in the CallToolRequest switch statement that parses arguments, calls the forkRepository function, and returns the result.
    case "fork_repository": {
      const args = repository.ForkRepositorySchema.parse(request.params.arguments);
      const fork = await repository.forkRepository(args.owner, args.repo, args.organization);
      return {
        content: [{ type: "text", text: JSON.stringify(fork, null, 2) }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like authentication requirements, rate limits, whether the fork inherits all branches/tags, what happens if the target organization lacks permissions, or what the response contains. For a mutation tool with zero annotation coverage, this is inadequate.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core action and includes essential scope information. Every word earns its place without redundancy.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or important behavioral constraints. Given the complexity of repository forking (permissions, inheritance, etc.), more context is needed beyond the basic action statement.

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 100%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema (e.g., no examples, format details, or edge cases). Baseline 3 is appropriate when schema does the heavy lifting.

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 specific action ('Fork') and resource ('a GitHub repository'), with precise scope ('to your account or specified organization'). It distinguishes from siblings like create_repository (which creates new repos) and other tools that modify existing repos rather than creating forks.

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?

The description implies usage context by specifying the target ('your account or specified organization'), but doesn't explicitly state when to use this vs alternatives like create_repository or when not to use it. No prerequisites or exclusions are mentioned, leaving some guidance gaps.

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/PhialsBasement/mcp-github-server-plus'

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