```

mcp-git-commit-generator with SSE transport

```sh mcp-git-commit-generator --transport sse ```

Using uv

```sh uv run -m mcp_git_commit_generator --transport sse ```

Using Python directly

```sh python -m mcp_git_commit_generator --transport sse ```

You can specify other options, for example: ```sh python -m mcp_git_commit_generator --transport sse --host 0.0.0.0 --port 3001 -v ``` > The server listens on `0.0.0.0:3001` by default when using SSE, or as specified by the options above. **Note:** - If you want to use the CLI entrypoint, ensure the package is installed and your environment is activated. - Do not use positional arguments (e.g., `python -m mcp_git_commit_generator sse`); always use options like `--transport sse`. - Available arguments with their values are: - `--transport`: Transport type (e.g., `stdio` (default), `sse`). - `--host`: Host to bind the server (default: `0.0.0.0`). - `--port`: Port to bind the server (default: `3001`). - `-v`, `--verbose`: Verbosity level (e.g., `-v`, `-vv`). ### 🔎 Start the Inspector UI From the `inspector` directory: ```sh npm run dev:inspector ``` > The Inspector UI will be available at `http://localhost:5173`. ### 🗂️ Project Structure ```sh . ├── .github/ # GitHub workflows and issue templates ├── .gitignore ├── .markdownlint.jsonc ├── .python-version ├── .vscode/ # VSCode configuration ├── LICENSE ├── README.md ├── pyproject.toml # Python project configuration ├── requirements-dev.txt # Development dependencies ├── uv.lock # Python dependencies lock file ├── Dockerfile # Docker build file ├── build/ # Build artifacts ├── src/ # Python source code │ └── mcp_git_commit_generator/ │ ├── __init__.py # Main entry point │ ├── __main__.py # CLI entry point │ └── server.py # Main server implementation └── inspector/ # Inspector related files ├── package.json # Node.js dependencies └── package-lock.json ``` ### ⚙️ Advanced MCP Server Configuration for Development The `.vscode/mcp.json` file configures how VS Code and related tools connect to your MCP Git Commit Generator server. This file defines available server transports and their connection details, making it easy to switch between different modes (stdio is default, SSE is optional) for development and debugging. #### Example Development `mcp.json` ```jsonc { "servers": { "mcp-git-commit-generator": { "command": "docker", "args": [ "run", "-i", "--rm", "--mount", "type=bind,src=${userHome},dst=${userHome}", "ghcr.io/theoklitosbam7/mcp-git-commit-generator:latest" ] }, "sse-mcp-git-commit-generator": { "type": "sse", "url": "http://localhost:3001/sse" }, "stdio-mcp-git-commit-generator": { "type": "stdio", "command": "${command:python.interpreterPath}", "args": ["-m", "mcp_git_commit_generator", "--transport", "stdio"] }, "uvx-mcp-git-commit-generator": { "command": "uvx", "args": ["mcp-git-commit-generator"] } } } ``` - **mcp-git-commit-generator**: Runs the server in a Docker container (default: stdio transport), using the published image. - **sse-mcp-git-commit-generator**: Connects to the MCP server using Server-Sent Events (SSE) at `http://localhost:3001/sse`. Only useful if you run the server with `--transport sse`. - **stdio-mcp-git-commit-generator**: Connects using standard input/output (stdio), running the server as a subprocess. This is the default and recommended for local development and debugging. - **uvx-mcp-git-commit-generator**: Use

#commit-generator

Mcp Git Commit Generator