Skip to main content
Glama

Related Servers

Alternatives to zapier-dev-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that wraps Spectral to lint OpenAPI specifications, enabling LLMs to validate and fix API definitions.
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that provides code validation rules and analysis for various stacks/frameworks, enabling automated code reviews and reporting directly from VS Code and other editors.
      -
    • A
      license
      A
      quality
      A
      maintenance
      MCP server that provides audit and safety-check tools for enterprise SDLC code integrity, enabling AI agents to scan workspaces for lifecycle gaps, mock-theater tests, DRY violations, and language-specific issues in shell, JavaScript/HTML, and Python.
      4
      14 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server for in-loop design review of web previews. It enables agents to submit a preview URL, receive structured findings with suggested fixes, and recheck after applying changes, while never editing code itself.
      5
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a clear primary purpose: generating fixtures, inspecting, linting, and validating. However, lint_integration and validate_integration are both quality checks, and an agent might need to read descriptions carefully to pick the right one.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: generate_test_fixtures, inspect_integration, lint_integration, validate_integration. The verbs clearly indicate actions and nouns uniformly refer to integration artifacts.

    Tool Count5/5

    Four tools is a well-scoped set for a Zapier development helper. Each tool covers a distinct phase (generate, inspect, lint, validate) without redundant utilities, fitting the recommended 3-15 range.

    Completeness4/5

    The set covers the core lifecycle for integration quality: generating test fixtures, inspecting structure, linting for blockers, and running official validation. A notable gap is the lack of a tool to execute tests or apply fixes, but the surface is reasonably complete for analysis tasks.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues