Git Commit Message Generator MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_API_KEY | No | Groq API key (Required if using Groq LLM provider) | |
| LLM_PROVIDER | No | LLM provider to use (e.g., 'deepseek' or 'groq') | deepseek |
| DEEPSEEK_API_KEY | No | DeepSeek API key (Required if using DeepSeek LLM provider) |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_commit_messageB | Generate a commit message from the git changes in the current project directory. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
The single tool name follows a clear verb_noun pattern (generate_commit_message), which is consistent and predictable. There are no other tools to compare against, so no inconsistency exists.
One tool is too few for a server's purpose, as it limits functionality and suggests a narrow scope that might not support complex workflows. Typically, a well-scoped server would have 3-15 tools to cover a domain adequately.
The server is severely incomplete for generating commit messages, as it only offers generation without supporting operations like customization, validation, history management, or integration with other git tasks. This creates significant gaps for agent workflows.