Summary

The standard is in context before the code is written, not in review after.

Style arguments in code review are expensive; putting the guide where the model reads it is cheaper. The five tools cover three stacks, and because the content is plain Markdown returned by the server, swapping in your own house standards is a content change rather than a rewrite.

What it is

An MCP server that hands an assistant the coding standards for a language on request, so generated code follows the conventions your team writes down rather than whatever the model defaults to.

What you get

`java_style_guide` — clean code practices, naming conventions and code organisation, returned as Markdown
`java_best_practices` — project structure, architecture, testing and security
`python_style_guide` — PEP 8 based guidelines and Pythonic practices
`python_best_practices` — project layout, dependency management and testing practices
`react_best_practices` — component patterns, state management and performance optimisation

Requirements

Python 3.8 or higher and the MCP package (`pip install mcp`); the UV package manager is recommended. Install into a client with `mcp install server.py`, or run `mcp dev server.py` to inspect it — the MCP inspector starts on port 3000. Registering it manually means adding a `uv run --with mcp[cli] mcp run /absolute/path/to/coding-standards-mcp/server.py` command to your client's config. No account or key. Package version 0.1.0. MIT.

Setup effort

One command — mcp install server.py

Coding Standards