{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_ahmaxdev-gitrama-mcp","slug":"ahmaxdev-gitrama-mcp","name":"gitrama-mcp","type":"mcp","url":"https://gitrama.ai","page_url":"https://unfragile.ai/ahmaxdev-gitrama-mcp","categories":["mcp-servers","app-builders","automation"],"tags":["mcp","model-context-protocol","smithery:ahmaxdev/gitrama-mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_ahmaxdev-gitrama-mcp__cap_0","uri":"capability://code.generation.editing.conventional.commit.message.generation","name":"conventional-commit-message-generation","description":"Analyzes staged git changes and generates semantically-correct conventional commit messages following the Conventional Commits specification (feat:, fix:, docs:, etc.). Integrates with git diff output to understand change scope and automatically categorizes commits by type, enabling consistent commit history that can be parsed by automated changelog and versioning tools.","intents":["Generate a conventional commit message from my staged changes without manually typing the format","Ensure all commits follow our team's conventional commits standard for automated changelog generation","Quickly categorize whether a change is a feature, fix, breaking change, or documentation update"],"best_for":["development teams using semantic versioning and automated changelog generation","solo developers wanting consistent commit history without manual formatting","projects integrating with CI/CD pipelines that parse conventional commits"],"limitations":["Requires staged changes in git — cannot generate commits from unstaged or untracked files","Accuracy depends on code diff clarity — large, mixed-purpose commits may produce generic messages","No support for custom commit types beyond standard Conventional Commits spec without configuration"],"requires":["Git repository initialized with staged changes","MCP server integration (Cursor, Claude Desktop, Claude Code, Windsurf, or VS Code)","Access to git diff output via MCP protocol"],"input_types":["git diff output","staged file changes","repository context"],"output_types":["conventional commit message string","commit type classification (feat, fix, docs, etc.)","structured commit metadata"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_ahmaxdev-gitrama-mcp__cap_1","uri":"capability://code.generation.editing.git.branch.name.generation","name":"git-branch-name-generation","description":"Generates semantically meaningful git branch names based on commit intent, issue context, or feature descriptions. Follows common branch naming conventions (feature/, bugfix/, hotfix/, etc.) and can incorporate issue tracker IDs or ticket numbers. Integrates with the MCP protocol to receive context about planned work and output formatted branch names ready for immediate use.","intents":["Create a properly-formatted branch name that reflects the feature or fix I'm about to work on","Generate branch names that include ticket/issue IDs for traceability","Ensure branch naming consistency across the team without manual style guides"],"best_for":["teams with strict branch naming conventions for CI/CD integration","projects tracking work via issue trackers (Jira, GitHub Issues, Linear)","developers wanting to avoid manual branch name formatting"],"limitations":["Cannot automatically detect issue/ticket IDs — requires explicit context or manual input","Generated names may exceed git's practical length limits for deeply nested conventions","No validation against existing branches — risk of duplicate or conflicting names without additional tooling"],"requires":["Git repository initialized","MCP server integration with editor","Optional: issue tracker context or ticket ID"],"input_types":["feature description or commit intent","issue/ticket ID (optional)","branch type context (feature, bugfix, hotfix, etc.)"],"output_types":["formatted branch name string","branch naming convention metadata"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_ahmaxdev-gitrama-mcp__cap_2","uri":"capability://text.generation.language.pull.request.description.generation","name":"pull-request-description-generation","description":"Automatically generates comprehensive PR descriptions by analyzing the commits, branch name, and code changes between source and target branches. Structures descriptions with sections for summary, changes, testing notes, and breaking changes. Integrates with git metadata and MCP protocol to fetch branch diffs and produce markdown-formatted descriptions ready for GitHub, GitLab, or Bitbucket.","intents":["Generate a detailed PR description from my commits without manually writing the summary","Ensure PR descriptions include testing instructions and breaking change warnings automatically","Create consistent PR documentation format across the team"],"best_for":["teams requiring detailed PR documentation for code review and audit trails","projects with automated PR validation that parses description sections","developers wanting to reduce PR creation friction"],"limitations":["Quality depends on commit message quality — poor commits produce generic descriptions","Cannot automatically detect breaking changes without explicit markers in commits or code","No integration with external issue trackers for automatic linking without manual configuration","Markdown formatting may require adjustment for platform-specific PR templates"],"requires":["Git repository with commits on feature branch","Target branch specified (main, develop, etc.)","MCP server integration with editor","Access to git diff and commit history"],"input_types":["source branch name","target branch name","commit history between branches","code diff output"],"output_types":["markdown-formatted PR description","structured PR metadata (summary, changes, testing, breaking changes)"],"categories":["text-generation-language","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_ahmaxdev-gitrama-mcp__cap_3","uri":"capability://memory.knowledge.work.stream.context.management","name":"work-stream-context-management","description":"Maintains and manages contextual information about ongoing work streams, including related branches, commits, issues, and PR history. Stores work stream metadata via MCP protocol to provide consistent context across multiple git operations (commits, branches, PRs). Enables the system to generate more coherent messages and branch names by understanding the broader work context rather than treating each operation in isolation.","intents":["Keep track of related commits and branches for a feature across multiple work sessions","Provide context to commit/branch/PR generation so they reference the same work stream","Maintain a coherent narrative across multiple git operations for a single feature or fix"],"best_for":["developers working on multi-commit features or complex fixes","teams needing traceability across related git operations","projects with long-running features spanning multiple branches"],"limitations":["No persistent storage — work stream context is session-based and lost on editor restart without external persistence","Cannot automatically detect work stream boundaries — requires explicit user indication of related work","No integration with external project management tools for automatic work stream detection","Context size is limited by MCP message constraints and LLM context window"],"requires":["MCP server integration with editor","Git repository with multiple commits/branches","Optional: external state store for persistence across sessions"],"input_types":["branch names","commit messages","issue/ticket IDs","user-provided work stream metadata"],"output_types":["work stream context object","related commits and branches list","work stream metadata"],"categories":["memory-knowledge","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_ahmaxdev-gitrama-mcp__cap_4","uri":"capability://tool.use.integration.multi.editor.mcp.integration","name":"multi-editor-mcp-integration","description":"Provides MCP server implementation compatible with multiple editor environments including Cursor, Claude Desktop, Claude Code, Windsurf, and VS Code. Implements the Model Context Protocol specification to expose git workflow capabilities as standardized tools that editors can invoke. Handles MCP message serialization, tool registration, and context passing across different editor implementations.","intents":["Use gitrama capabilities in my preferred editor without installing separate tools","Integrate gitrama into my existing Claude Desktop or Cursor workflow","Access git workflow generation from multiple editor environments with consistent behavior"],"best_for":["developers using Cursor, Claude Desktop, Claude Code, Windsurf, or VS Code","teams standardizing on MCP-compatible tools for AI integration","organizations wanting editor-agnostic AI git workflow tooling"],"limitations":["Requires MCP-compatible editor version — older editor versions may not support MCP protocol","Editor-specific configuration required for each environment (separate setup per editor)","MCP message size limits may constrain context size for very large diffs or commit histories","No built-in authentication — relies on editor's credential management"],"requires":["Cursor 0.42+, Claude Desktop 0.1+, Claude Code, Windsurf, or VS Code 1.80+","MCP server running locally or accessible via network","Git repository initialized in workspace"],"input_types":["MCP tool invocation requests","git repository context","editor workspace metadata"],"output_types":["MCP tool response objects","generated text/code","structured metadata"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_ahmaxdev-gitrama-mcp__cap_5","uri":"capability://data.processing.analysis.git.diff.analysis.for.context","name":"git-diff-analysis-for-context","description":"Analyzes git diff output to extract semantic information about code changes, including files modified, change magnitude, affected functions/classes, and change type (addition, deletion, modification). Parses diff format to understand structural changes and provides this analysis as context for commit message, branch name, and PR description generation. Enables LLM-based generation to understand not just what changed, but why and how significant the change is.","intents":["Understand what files and functions were changed to generate accurate commit messages","Determine change scope and magnitude to categorize commits correctly (feat vs fix vs refactor)","Provide detailed context about code changes to PR description generation"],"best_for":["projects with large or complex diffs requiring semantic understanding","teams needing accurate change categorization for semantic versioning","developers wanting commit messages that reflect actual code structure changes"],"limitations":["Diff analysis is limited to text-based diffs — binary files are not analyzed","Large diffs (>10,000 lines) may be truncated or summarized, losing detail","Cannot understand semantic intent from diff alone — requires commit messages or branch context for full understanding","Language-specific analysis (e.g., function-level changes) requires language-aware parsing not included in base implementation"],"requires":["Git repository with staged or committed changes","Access to git diff output","MCP server integration"],"input_types":["git diff output (unified diff format)","file paths and change types","commit range or branch comparison"],"output_types":["structured change analysis","file and function-level change metadata","change magnitude and scope metrics"],"categories":["data-processing-analysis","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_ahmaxdev-gitrama-mcp__cap_6","uri":"capability://code.generation.editing.conventional.commits.spec.compliance","name":"conventional-commits-spec-compliance","description":"Enforces and validates adherence to the Conventional Commits specification (https://www.conventionalcommits.org/) including proper formatting of commit type, scope, subject, and body. Generates commits that are parseable by automated tools for changelog generation, semantic versioning, and CI/CD pipelines. Supports optional configuration for custom commit types and scope validation.","intents":["Ensure all generated commits follow the Conventional Commits standard for automated tooling","Generate commits that can be parsed by semantic-release or similar automation tools","Validate that commits include breaking change indicators when appropriate"],"best_for":["projects using semantic-release, commitlint, or similar conventional commits tooling","teams with automated changelog generation from commits","organizations standardizing on conventional commits for all repositories"],"limitations":["Requires understanding of Conventional Commits spec — may be unfamiliar to new team members","Custom commit types require explicit configuration — defaults to standard types only","Scope validation is optional and not enforced without configuration","Breaking change detection relies on commit message markers, not code analysis"],"requires":["Understanding of Conventional Commits specification","Optional: commitlint or similar validation tool for CI/CD integration","MCP server integration"],"input_types":["commit type (feat, fix, docs, etc.)","commit scope (optional)","commit subject and body","breaking change indicators"],"output_types":["conventional commit message string","validation status and errors","structured commit metadata"],"categories":["code-generation-editing","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_ahmaxdev-gitrama-mcp__cap_7","uri":"capability://tool.use.integration.issue.tracker.context.integration","name":"issue-tracker-context-integration","description":"Accepts issue/ticket IDs and context from external issue trackers (Jira, GitHub Issues, Linear, etc.) and incorporates this information into generated commits, branch names, and PR descriptions. Enables linking of git operations to external work tracking systems without manual copy-paste. Stores issue context within work stream metadata for consistent referencing across multiple git operations.","intents":["Automatically include issue/ticket IDs in commits and branch names for traceability","Link generated PRs to external issue trackers without manual linking","Maintain connection between git operations and external work tracking"],"best_for":["teams using external issue trackers (Jira, GitHub Issues, Linear, etc.)","projects requiring traceability between code changes and tracked work","organizations with automated issue closing from commits/PRs"],"limitations":["Requires manual input of issue/ticket ID — cannot automatically detect from editor context","No direct API integration with issue trackers — only accepts IDs and context, doesn't fetch from trackers","Issue context must be provided explicitly — cannot infer from branch names or commit messages","No validation that issue IDs are valid in the external tracker"],"requires":["Issue/ticket ID from external tracker","Optional: issue context or description","MCP server integration"],"input_types":["issue/ticket ID string","issue title or description","issue type or status"],"output_types":["commits with issue ID references","branch names including issue ID","PR descriptions with issue links"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_ahmaxdev-gitrama-mcp__cap_8","uri":"capability://data.processing.analysis.breaking.change.detection.and.documentation","name":"breaking-change-detection-and-documentation","description":"Analyzes code diffs to detect potential breaking changes (API signature changes, removed functions, database schema changes, dependency version bumps) and flags them for documentation in commit messages and PR descriptions. Uses heuristics and pattern matching to identify common breaking change patterns, then generates BREAKING CHANGE footer entries in conventional commit format. Can be configured to require explicit breaking change documentation before committing.","intents":["Automatically detect breaking changes in my code and ensure they're documented","Prevent accidental breaking changes from being committed without proper documentation","Generate BREAKING CHANGE footers in conventional commit format for automated changelog generation","Identify which changes are breaking vs non-breaking for release planning"],"best_for":["teams maintaining libraries or APIs with semantic versioning","organizations with strict breaking change policies","projects using automated changelog generation that depends on BREAKING CHANGE footers"],"limitations":["Detection is heuristic-based — cannot reliably identify all breaking changes without language-specific analysis","False positives are common (e.g., renaming a private function flagged as breaking)","Cannot detect runtime breaking changes (e.g., behavior changes that don't affect API signatures)","Requires language-specific knowledge to accurately detect breaking changes — currently limited to common patterns","No integration with semantic versioning tools to enforce version bumps based on breaking changes"],"requires":["Git diff with code changes","Optional: language-specific configuration for accurate detection","Optional: API schema or type definitions for validation"],"input_types":["git diff","file types and language information","optional: API schema or type definitions"],"output_types":["list of detected breaking changes","BREAKING CHANGE footer text for commit messages","severity classification (major, minor, patch)"],"categories":["data-processing-analysis","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":33,"verified":false,"data_access_risk":"high","permissions":["Git repository initialized with staged changes","MCP server integration (Cursor, Claude Desktop, Claude Code, Windsurf, or VS Code)","Access to git diff output via MCP protocol","Git repository initialized","MCP server integration with editor","Optional: issue tracker context or ticket ID","Git repository with commits on feature branch","Target branch specified (main, develop, etc.)","Access to git diff and commit history","Git repository with multiple commits/branches"],"failure_modes":["Requires staged changes in git — cannot generate commits from unstaged or untracked files","Accuracy depends on code diff clarity — large, mixed-purpose commits may produce generic messages","No support for custom commit types beyond standard Conventional Commits spec without configuration","Cannot automatically detect issue/ticket IDs — requires explicit context or manual input","Generated names may exceed git's practical length limits for deeply nested conventions","No validation against existing branches — risk of duplicate or conflicting names without additional tooling","Quality depends on commit message quality — poor commits produce generic descriptions","Cannot automatically detect breaking changes without explicit markers in commits or code","No integration with external issue trackers for automatic linking without manual configuration","Markdown formatting may require adjustment for platform-specific PR templates","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.43,"ecosystem":0.5900000000000001,"match_graph":0.25,"freshness":0.5,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:25.062Z","last_scraped_at":"2026-05-03T15:19:44.684Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=ahmaxdev-gitrama-mcp","compare_url":"https://unfragile.ai/compare?artifact=ahmaxdev-gitrama-mcp"}},"signature":"oDLC+dBaDKn12ReA5cgz5c6LTDl7V8i4vmfkEBH4pB7q3GJDOv8jKtBorc/MQa0iv+Qd/52+i+3pgavrvA5oBg==","signedAt":"2026-06-21T06:17:34.862Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/ahmaxdev-gitrama-mcp","artifact":"https://unfragile.ai/ahmaxdev-gitrama-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=ahmaxdev-gitrama-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}