Skip to main content
Glama
aimarket-mcp-packager

aimarket-mcp-packager

Related Servers

Alternatives to aimarket-mcp-packager

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables any stdio-speaking MCP client (Claude Desktop, Claude Code, Cursor, VS Code) to call schema-validated tools such as echo, now, and uuid, read a config://manifest resource, and invoke a review-diff prompt. It ships as a ready-to-extend scaffold with stderr-only logging, graceful shutdown, tests, and a Docker image.
      3
      29 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server built with the mcp-framework for developing and managing custom tools. It provides a structured foundation for building and integrating modular components like data processors and API clients into Claude Desktop.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A production-ready Model Context Protocol server built with Python and FastMCP, featuring modular architecture, centralized tool registration, Docker support, and a suite of utility tools for AI applications.
      3
      -
    • A
      license
      A
      quality
      B
      maintenance
      Local MCP server that wraps the headless Claude Code CLI as MCP tools, providing stateless access to Claude's coding capabilities through prompt-based interactions. It enables users to execute Claude Code commands with various prompt formats and structured outputs directly from MCP clients.
      3
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server built with FastMCP that features dynamic tool loading and modular management via a dedicated tool directory. It supports both stdio and HTTP transport modes, enabling efficient development and deployment of custom MCP tools.
      -

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: package_capability builds the package, generate_dockerfile produces the Dockerfile, and generate_claude_desktop_config outputs the config snippet. There is no overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (package_capability, generate_dockerfile, generate_claude_desktop_config), making them predictable and easy to understand.

    Tool Count4/5

    With 3 tools, the server is slightly small but well-scoped for its packaging purpose. Each tool serves a necessary step, and adding more would risk bloat.

    Completeness4/5

    The tool set covers the core packaging workflow: build the package, generate Dockerfile, and generate config. Minor gaps exist, such as lacking a validation or listing tool, but the main path is complete.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues