biome-mcp
Related Servers
Alternatives to biome-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceExposes TypeScript Language Server Protocol functionality to AI agents, enabling them to query types at specific positions, find definitions and references, get diagnostics, run type tests, and type-check inline code just like in an IDE.9242 npm3MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to invoke common developer tools — git, GitHub, npm, Python, cargo, Docker, Kubernetes, linters, and test runners — and receive schema-validated structured JSON instead of raw terminal text. This removes brittle string parsing and cuts token usage dramatically on verbose commands like builds, installs, and test runs.5 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to work with developer tools such as git, npm, Docker, and test runners through structured, schema-validated JSON outputs. Reduces token usage and eliminates fragile terminal text parsing for reliable cross-platform workflows.5 npmMIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to interact with TypeScript projects through compiler-level code intelligence, providing tools for navigation, type information, diagnostics, refactoring, and semantic search.29722 npm4Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to interact with common developer tools such as Git, npm, Docker, and test runners by returning schema-validated JSON instead of raw terminal text. This reduces brittle parsing errors and token usage while providing typed data agents can act on directly.5 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to invoke common developer tools such as git, npm, Docker, and test runners and receive clean, schema-validated JSON instead of fragile terminal text, reducing token usage and parsing errors.5 npmMIT
TDQS
Scored across 5 tools
Tools are mostly distinct: biome_check runs all checks, biome_lint and biome_format focus on specific aspects. The hierarchical overlap (check includes lint/format) is clear from descriptions, so misselection is unlikely. No two tools appear to do the same thing.
Three tools use a biome_ prefix (biome_check, biome_lint, biome_format) while two do not (update_cache, search_documentation). The actions follow a readable verb_noun pattern, but the mixed prefix usage creates inconsistency.
Five tools is well-scoped for a Biome utility server. Each tool serves a clear purpose: three for running checks and two for documentation cache management. No unnecessary bloat or thin coverage.
The server covers the main Biome check categories (format, lint, assist via biome_check) and documentation needs (update and search). Minor gaps exist: no separate assist-only tool or ability to write/fix files, but the read-only design makes this acceptable.