git-remote-mcp

git_push_new_branch

Push a new branch to a git remote via a configured HTTP API. Optionally creates the local branch and sets upstream tracking.

Instructions

Ask the configured HTTP API to push a new branch to a git remote.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "branch": "<branch>"
    },
    "name": "git_push_new_branch"
  }
}

Input Schema

Name	Required	Description	Default
`cwd`	No	Optional local working directory or repository path.
`branch`	Yes	New branch name to push.
`remote`	No	Git remote name.	origin
`startPoint`	No	Optional start point used when creating the branch.
`createLocal`	No	Create and switch to the local branch before publishing.
`setUpstream`	No	Ask the API to set upstream tracking for the new branch.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It notes the operation goes through a configured HTTP API and pushes a branch (a remote mutation), but says nothing about permissions, what happens if the branch already exists, whether the remote is modified destructively, or how createLocal/setUpstream side effects manifest. For a write tool with zero annotation coverage this is a substantial gap.

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?

A single efficient sentence with the core action front-loaded; there is no padding. It is appropriately sized, though the 'Ask the configured HTTP API' framing is a minor distraction rather than added value.

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 too thin. It omits prerequisites, side effects, and how the branch creation/publishing combination behaves, leaving the agent under-informed about an operation that alters remote state.

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 all six parameters are already documented in the schema with their defaults and semantics. The description adds no syntax, format, or behavioral detail beyond what the schema states, so baseline 3 is correct.

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

Purpose4/5

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

States a specific verb (push) and resource (a new branch to a git remote), and the word 'new' meaningfully distinguishes it from the sibling git_push, which presumably pushes existing work on the current branch. The 'Ask the configured HTTP API' preamble is slightly noisy but does not obscure the action. Differentiation from siblings is implied rather than explicit.

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

Usage Guidelines2/5

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

No guidance on when to use this versus git_push or git_branch/git_switch. The description never names an alternative or a selection condition, leaving the agent to infer the 'new branch' case on its own.

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