home / mcp / protolint mcp server
Provides a fast, configurable MCP-enabled linter for Protocol Buffer files with optional automatic fixes and plugin support for custom rules.
Configuration
View docs{
"mcpServers": {
"yoheimuta-protolint": {
"command": "protolint",
"args": [
"--mcp"
]
}
}
}You can enable the Model Context Protocol (MCP) server capability in protolint to interact with AI models directly for linting Protocol Buffer files. This integration lets you query lint results, request fixes, and automate style enforcement within your MCP-enabled workflow.
You can connect an MCP client to protolint to lint and fix Protocol Buffer files. Start the MCP server mode and then interact with it through your MCP client to run lint checks, apply fixes, and manage disable rules via comments in your .proto files.
Prerequisites: you need a working environment where you can install binaries or run containerized tooling. The following options show common installation methods.
# Option 1: Install via Homebrew (macOS/Linux)
brew tap yoheimuta/protolint
brew install protolint
# Option 2: Install from GitHub releases (pre-built binaries)
# Download the appropriate binary for your platform from the releases page and place it in your PATH
```
```
```bash
# Option 3: Build from source (Go is required)
# Install the latest binary for your platform
go install github.com/yoheimuta/protolint/cmd/protolint@latest
```
```
# After installation, run this to start MCP mode
protolint --mcpConfiguration and usage tips for the MCP server are centered around running protolint in MCP mode and then connecting with an MCP client. There are multiple pathways to integrate, depending on your build and deployment workflow.
From development to production, you can compose workflows that lint and fix your Protocol Buffer files through your MCP client, enabling automated style enforcement and compatibility management.
Exposes the MCP endpoint to enable AI model interactions for linting and fixing Protocol Buffer files.
Integrations for editors (VS Code, JetBrains IDEs, Vim/ALE, Vim/Syntastic) to run protolint in MCP mode within your development environment.
GitHub Actions, pre-commit hooks, and CI-friendly reporters to run protolint in MCP workflows.