Click on "Deploy 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., "@Commit Conventional Message Court (CCMCP) Rewrite my lazy commit message 'updates' based on the current diff."
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.
Please write better commits with AI.
Give this repo to your AI and ask it to install the MCP for you.
Seriously. That is a valid setup flow.
I take your vague commit messages, drag them into court, point at the diff, and ask the question your teammates are too tired to ask:
"What exactly did you do?"
Add this to ~/.codex/config.toml:
[mcp_servers.commit-message-court]
command = "node"
args = ['C:\Users\chrisdnm\Desktop\commimWizard\dist\index.js']Then restart Codex.
Related MCP server: Cursor Auto-Review MCP Server
On Windows, add it as a local stdio server with:
claude mcp add --transport stdio commit-message-court -- node C:\Users\chrisdnm\Desktop\commimWizard\dist\index.jsIf you want it available everywhere, add --scope user.
claude mcp add --transport stdio --scope user commit-message-court -- node C:\Users\chrisdnm\Desktop\commimWizard\dist\index.jsAdd this to your claude_desktop_config.json:
{
"mcpServers": {
"commit-message-court": {
"type": "stdio",
"command": "node",
"args": ["where code is"],
"env": {}
}
}
}Then restart Claude Desktop.
It sees fix stuff and objects.
It sees final_final_real and requests counsel.
It sees a risky diff and asks for evidence.
It sees your commit history and tries, against all odds, to make it readable.
WTFPL -- Do What The Fuck You Want To Public License.
Put a commit subject and diff on trial and return a structured verdict.
Inputs: subject (required), diff (required), body, pr_body, +2 more.
Render the courtroom opinion for a commit message case.
Inputs: subject (required), diff (required), body, pr_body, +2 more.
Force a better commit subject and provide rewrite suggestions.
Inputs: subject (required), diff (required), body, pr_body, +2 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 3 tools
While each tool has a distinct function, the relationship between prosecute_commit and render_verdict is unclear—agents may not know if they need to call both in sequence or if prosecute_commit alone suffices. require_better_subject also feels like it could be a sub-operation of the prosecution rather than a standalone tool.
All tools follow a consistent court.<verb>_<object> pattern using lowercase snake_case. The 'court.' prefix acts as a namespace, and the verb choices (prosecute, render, require) are thematically appropriate, though 'require' breaks the pure verb_noun pattern slightly with the 'better' modifier.
Three tools is at the lower bound of acceptable for this domain. While the core analysis and suggestion functions are present, the set feels thin—missing configuration, batch processing, or actual commit amendment capabilities that would make this a complete solution.
The set covers analysis (prosecute), presentation (render), and suggestion (require), but lacks obvious lifecycle operations like applying fixes, configuring rules/standards, or handling commit metadata beyond the subject line. The separation between rendering and prosecution creates a potential gap if agents expect a single 'check and report' operation.
A MCP server built for developers enabling Git based project management with project and personal…
The Jam MCP server provides AI tools with instant bug context without manual prompting, enabling a streamlined workflow from bug identification to ticket creation and pull request generation without switching between tools.
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
