Skip to main content
Glama
ddukbg

GitHub Enterprise MCP Server

merge-pull-request

Merge a GitHub pull request using specified method (merge, squash, or rebase) with customizable commit messages to integrate code changes into the repository.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner (user or organization)
repoYesRepository name
pull_numberYesPull request number
commit_titleNoTitle for the automatic commit message
commit_messageNoExtra detail to append to automatic commit message
merge_methodNoMerge method to usemerge

Implementation Reference

  • Primary MCP tool handler for 'merge-pull-request'. Registers the tool with Zod input schema, performs parameter validation, calls the underlying mergePullRequest helper, and returns formatted success/error response.
    server.tool(
      "merge-pull-request",
      {
        owner: z.string().describe("Repository owner (user or organization)"),
        repo: z.string().describe("Repository name"),
        pull_number: z.number().describe("Pull request number"),
        commit_title: z.string().optional().describe("Title for the automatic commit message"),
        commit_message: z.string().optional().describe("Extra detail to append to automatic commit message"),
        merge_method: z.enum(['merge', 'squash', 'rebase']).default('merge').describe("Merge method to use")
      },
      async ({ owner, repo, pull_number, commit_title, commit_message, merge_method }) => {
        try {
          // Parameter validation
          if (!owner || typeof owner !== 'string' || owner.trim() === '') {
            return {
              content: [
                {
                  type: "text",
                  text: "Error: Repository owner (owner) is required."
                }
              ],
              isError: true
            };
          }
    
          if (!repo || typeof repo !== 'string' || repo.trim() === '') {
            return {
              content: [
                {
                  type: "text",
                  text: "Error: Repository name (repo) is required."
                }
              ],
              isError: true
            };
          }
    
          if (!pull_number || typeof pull_number !== 'number') {
            return {
              content: [
                {
                  type: "text",
                  text: "Error: Pull request number (pull_number) is required."
                }
              ],
              isError: true
            };
          }
    
          const result = await context.pulls.mergePullRequest(context.client, {
            owner,
            repo,
            pull_number,
            commit_title,
            commit_message,
            merge_method
          });
    
          return {
            content: [
              {
                type: "text",
                text: `Successfully merged pull request #${pull_number}.\nResult: ${result.message}\nCommit SHA: ${result.sha}`
              }
            ]
          };
        } catch (error: any) {
          console.error('Error merging pull request:', error);
          return {
            content: [
              {
                type: "text",
                text: `An error occurred while merging pull request: ${error.message}`
              }
            ],
            isError: true
          };
        }
      }
    );
  • Core helper function that executes the GitHub API PUT request to merge the specified pull request.
    export async function mergePullRequest(
      client: GitHubClient,
      params: MergePullRequestParams
    ): Promise<MergePullRequestResponse> {
      const { owner, repo, pull_number, ...data } = params;
      
      return client.put<MergePullRequestResponse>(
        `/repos/${owner}/${repo}/pulls/${pull_number}/merge`,
        data
      );
    } 
  • TypeScript interface defining the input parameters for the merge pull request operation.
    export interface MergePullRequestParams {
      owner: string;
      repo: string;
      pull_number: number;
      commit_title?: string;
      commit_message?: string;
      merge_method?: 'merge' | 'squash' | 'rebase';
    }
  • TypeScript interface defining the response from the merge pull request operation.
    export interface MergePullRequestResponse {
      sha: string;
      merged: boolean;
      message: string;
    } 
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/ddukbg/github-enterprise-mcp'

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