Gitmoji Commit MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| git_format_messageA | Format a commit message according to the git-emoji-commit convention. Takes commit parameters and returns a properly formatted message with emoji. |
| git_validate_messageA | Validate a commit message against the git-emoji-commit convention. Returns validation results with any issues or warnings. |
| git_suggest_typeA | Analyze staged git changes and suggest an appropriate commit type. Returns suggested type with reasoning. |
| git_commitA | Create a git commit following the emoji-commit convention. Validates staged changes exist, formats the message, and creates the commit. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct role: formatting, validating, suggesting type, and committing. There is no overlap in their primary purposes, making selection unambiguous.
All tool names follow the same `git_<verb>_<object>` pattern (e.g., git_format_message, git_validate_message). The naming is consistent and predictable.
With only 4 tools, the set is tightly focused on the gitmoji commit workflow. Each tool serves a necessary step without redundancy, making the count appropriate.
The tools cover the entire commit workflow: suggesting a type, formatting a message, validating it, and creating the commit. No obvious missing operation within the stated domain.