hop-mcp
Manages parallel Git worktrees, allowing users to work on multiple branches/tickets simultaneously without stashing or switching contexts.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@hop-mcpstart work on ticket PROJ-123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
hop-mcp
An MCP server for managing parallel Git worktrees. Work on multiple tickets simultaneously without stashing, switching branches, or losing context.
The Problem
You're deep in JIRA-456 when a critical bug comes in. Traditional workflow:
git stash
git checkout main
git checkout -b hotfix-789
# fix the bug
git checkout feature/JIRA-456
git stash pop # hope nothing conflictsWith hop:
hop start HOTFIX-789
# fix the bug in isolated directory
hop to JIRA-456
# back to your original work, exactly as you left itEach ticket gets its own directory. No stashing. No branch switching. No context loss.
Related MCP server: MCP Worktree Voting Server
Tools
Tool | Description |
| List all worktrees with path, branch, commit, and dirty status |
| Create a new worktree for a ticket (supports |
| Switch to an existing worktree |
| Get current worktree context (branch, ticket, dirty status) |
| Open a worktree in Cursor IDE |
| Remove a worktree (checks for uncommitted changes, supports |
| Delete scratch files in a worktree |
All tools also available as git_worktree_* aliases.
How It Works
Git worktrees create separate working directories that share the same .git object store:
my-project/ # main worktree (your original clone)
my-project/.worktrees/
├── JIRA-123/ # worktree for ticket JIRA-123
├── JIRA-456/ # worktree for ticket JIRA-456
└── HOTFIX-789/ # worktree for hotfixBenefits:
Low disk usage — only working files are duplicated, git objects are shared
Instant switching — just
cdto another directoryFull isolation — each worktree has its own node_modules, build cache, etc.
No conflicts — uncommitted changes stay exactly where they are
Requirements
Git 2.5+ (for worktree support)
Node.js 20+
Install
npm install
npm run buildSetup
Claude Code
Add to ~/.claude.json under projects.<your-project>.mcpServers:
{
"hop": {
"type": "stdio",
"command": "node",
"args": ["/path/to/hop-mcp/dist/index.js"]
}
}Cursor
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"hop": {
"command": "node",
"args": ["/path/to/hop-mcp/dist/index.js"]
}
}
}Configuration
Config is merged from (highest precedence first):
Per-repo:
.hop-mcp.jsonat repository rootGlobal:
~/.config/hop-mcp/config.json(macOS/Linux) or%APPDATA%\hop-mcp\config.json(Windows)Built-in defaults
Example .hop-mcp.json:
{
"worktreesDir": ".worktrees",
"defaultBaseBranch": "develop",
"defaultBranchTemplate": "feature/<ticket>-<slug>",
"defaultBranchTemplateNoSlug": "feature/<ticket>",
"scratchGlobs": [".cursor/plans/**", "**/*.plan.md"]
}Usage Examples
# See all active worktrees
hop list
# Start work on a new ticket
hop start JIRA-123
# Start with a descriptive slug
hop start JIRA-123 --slug fix-auth-timeout
# Preview what would be created (dry run)
hop start JIRA-123 --dry-run
# Switch to an existing ticket
hop to JIRA-123
# Check where you are
hop current
# Open ticket in Cursor
hop open JIRA-123
# Preview removal (shows dirty status)
hop end JIRA-123 --dry-run
# Remove when done (fails if uncommitted changes)
hop end JIRA-123
# Force remove with uncommitted changes
hop end JIRA-123 --forceLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/maciej-w/hop-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server