biome

Biome MCP Server exposes Biome's linting and formatting capabilities as MCP tools, enabling AI agents to analyze and automatically fix JavaScript/TypeScript code. The server provides two primary tools: biome-lint and biome-format. biome-lint runs Biome's lint checks across provided file paths and returns diagnostic information (errors, warnings, and suggestions) suitable for AI-driven remediation. biome-format applies Biome's formatting rules to the specified files, returning the reformatted code. Both tools can be configured with a custom Biome configuration file via the configPath parameter to tailor linting and formatting rules for different projects. The MCP client can connect to the biome server through the provided MCP configuration and issue tool invocations with the required paths and optional configuration paths. This setup enables automated code quality workflows within AI-driven agents and copilots, leveraging Biome's analysis and formatting capabilities seamlessly through MCP.

Typical usage involves configuring the MCP client with the biome server, then invoking:

• biome-lint with a list of target file paths (and an optional configPath) to obtain diagnostics for lint issues.
• biome-format with a list of target file paths (and an optional configPath) to obtain and apply formatting changes. This architecture makes it straightforward to integrate code quality tooling into automated tasks, pull requests, or agent workflows that operate on JavaScript/TypeScript projects.

Prerequisites:

• Node.js 22 or higher
• npm (comes with Node.js) or pnpm/yarn if you prefer other package managers

Installation steps:

1. Clone the repository: git clone https://github.com/RyuzakiShinji/biome-mcp-server.git cd biome-mcp-server

2. Install dependencies: npm install

3. Configure your MCP client: Use the provided example configuration to connect the biome MCP server. The example shows using npx to run the server script located in the cloned repo. You may adjust the path to point to your local biome-mcp-server.ts if you prefer a local TypeScript execution path.

4. Run and test: Ensure your environment has the required Node versions and that npm install completed successfully. Start your MCP client tooling with the configured biome server entry to verify linting and formatting capabilities are exposed through MCP.

Tips and common issues:

• Ensure Node.js 22+ is installed, as Biome-based tooling may rely on newer Node features.
• When using the MCP configuration, replace the placeholder path /path/to/the/cloned/repo/biome-mcp-server/biome-mcp-server.ts with the actual path to your local biome-mcp-server.ts file.
• If you encounter issues with Biome configuration, you can pass a custom configPath to both biome-lint and biome-format to enforce project-specific rules.
• The tools return textual diagnostics/formatting results rather than applying changes directly unless the MCP workflow is designed to apply edits; verify the output and integrate with your agent’s file write steps as needed.
• Keep Biome and its dependencies up to date to benefit from the latest lint rules and formatting capabilities.