Use this skill when the user needs TeamDynamix ITSM operations through MCP: ticket triage and updates, KB article maintenance, asset/CI relationships, service catalog lookups, project issue/risk workflows, or time entry queries. Always discover IDs first, use read-before-write patterns, and enforce write safety gates.
Use this skill when the user needs to manage Beans work items in a Beans workspace—create, view, update, reopen, archive, query, or bulk-manage beans, edit .beans files/frontmatter, or manage parent/blocking relationships. Use it even when the user says tickets/issues/backlog instead of “beans.” Do not use it for…
Use this skill for repositories managed through the git-mcp server when the task involves Git inspection, staging or committing, branches, remotes, rebase, cherry-pick, stash, bisect, worktrees, Git Flow, LFS, release tagging, PR preparation, or recovery. Prefer git-mcp tools over shell git commands, including when…
Use this skill when a repository may be managed by GitButler. Detect GitButler availability with gitbutcheck, then prefer the but CLI or but mcp server for version control in GitButler-managed repositories. Run but teardown before using git-mcp tools on a GitButler-managed repo so plain-Git writes do not conflict with…
Use this skill when a repository may be managed by Jujutsu (jj). Detect jj availability and management with gitjjcheck, then prefer the jj CLI for all version control operations in jj-managed repositories. git-mcp tools operate on the underlying .git and will not reflect jj's change model (working-copy commit…
A Git MCP server that doesn't suck. Runs locally from the @selfagency/git-mcp npm package.
★not rated 0 2d agoA
tokens not measured
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: