Skip to main content
Glama
guff192

wemake-python-mcp

by guff192
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to wemake-python-mcp

No user-submitted related servers found.

    Related Servers

    • python-mcp

      yriveiro
      A
      license
      A
      quality
      C
      maintenance
      This MCP server provides direct access to ruff linting, formatting checks, and ty type-checking for Python projects, with token-efficient, structured output.
      9
      MIT

    • mcp-server-analyzer

      Anselmoo
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that performs comprehensive Python code analysis using Ruff, ty, and Vulture for linting, type checking, and dead code detection.
      8
      79 PyPI
      11
      MIT

    • mcp-lint-tools

      rog0x
      A
      license
      Not graded
      quality
      D
      maintenance
      Code linting and style checking tools for AI agents, exposed as an MCP server. Supports style checks, naming conventions, complexity analysis, dead code detection, and import analysis.
      29 npm
      MIT

    • ruff-mcp-server

      drewsonne
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that integrates Ruff linting, formatting, and code analysis tools with advanced logging and configuration options for AI coding assistants.
      4
      1
      MIT

    • codetest-mcp

      jihyun0410
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for static code analysis using AST parsing and linters, providing tools to detect syntax errors, type issues, typos, and incorrect variable usage across multiple languages. It supports headless linting with tools like ast_check, lint_check, and health.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct input type or purpose: lint_file, lint_project, and lint_code differ by input source (file, directory, string), while explain_rule and update_rule_db serve separate functions. There is no overlap ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent lowercase snake_case verb_noun pattern (lint_file, lint_project, lint_code, explain_rule, update_rule_db). The naming is uniform and predictable.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose. It covers multiple linting input modes plus auxiliary rule explanation and database update features without unnecessary bloat.

    Completeness4/5

    The tool surface covers the core linting workflows (file, project, code string) and supporting rule utilities. A minor gap is the lack of a direct list-rules tool, but the existing tools handle common use cases effectively.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources