Skip to main content
Glama

Related Servers

Alternatives to pyfmcp

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      B
      quality
      A
      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
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that exposes Pyright language server functionality for Python, providing tools for type checking, code completions, and finding definitions. It enables AI models to perform static analysis and code formatting through the Model Context Protocol.
      7
      24 PyPI
      MIT
    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables automated maintenance and code analysis for Python/pytest repositories in isolated Docker environments. It supports read-only investigations, fix-and-verify tasks, and provides full audit trails with SQLite event history and artifact exports.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server providing automated code linting, rule explanations, and configuration templates for wemake-python-styleguide, with structured violation reports and offline rule database.
      5
      MIT

    TDQS

    B3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Python development: type checking (basedpyright), testing (pytest), and linting (ruff_lint). There is no functional overlap between them, making selection unambiguous.

    Naming Consistency4/5

    Two tools use the bare command name (basedpyright, pytest) while ruff_lint appends a descriptor. This is a minor deviation, but the naming is still predictable since each tool is recognizable by its underlying tool name.

    Tool Count5/5

    Three tools is well-scoped for a Python development server covering static analysis, linting, and testing. Each tool has a clear purpose and the count is appropriate for the domain.

    Completeness4/5

    The set covers the core development loop of type checking, linting, and testing. A formatter or build tool could be added, but the current coverage is typical and workable for most Python projects.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues