What it does
The tool lowercases the issue title and reduces it to a slug of a-z and 0-9, replacing each run of other characters with a single hyphen and removing leading and trailing hyphens. Slugs longer than max_slug_length (default 40, minimum 8) are cut to that length, and any hyphen left at the end is removed. The slug is then combined under one of four conventions: type-issue-slug (the default), type-slug, issue-slug or slug. The type prefix must be one of feat, fix, chore, docs, refactor or test.
A team might use it when it wants every branch for an issue named the same way, rather than relying on each contributor's habit. The MCP tool make_branch_name returns the branch, the final slug and the convention used. The command-line tool reads a JSON arguments file and prints its result as JSON.
The MCP server needs an MCP client configuration. The command-line tool takes an args.json file and exits with 0 on success, 1 on a runtime or input error, and 2 on a usage error. The computation is local and pure: it makes no network calls, needs no configuration, and does not read or change any repository.
Limitations and requirements
The title must be a non-empty string that contains at least one character that can be slugified; a title that produces an empty slug is an error. issue_number must be an integer of at least 1. type must be one of the six listed values. max_slug_length must be an integer of at least 8. Choosing a convention that needs type or issue_number without supplying it is an error. Malformed input returns a validation error naming the field, with no partial result. The MCP server requires an MCP client configuration.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/branchname
Build a branch name from an issue title and number, in the repo's naming convention.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it