Skip to main content
Glama
italoseara

mcc-fleet

by italoseara
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcc-fleet

No user-submitted related servers found.

    Related Servers

    • mcpelauncher-agent

      bedrock-mc
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables controlling a real Minecraft Bedrock client by injecting input and reading frames through the launcher's agent socket, including launching, stopping, screenshotting, sending chat, and managing multiple bot instances.
      3
      -

    • Minecraft AI Companion MCP

      SomExE
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-capable AI clients to control a Minecraft bot in a Java world, providing tools for movement, observation, inventory, chat, crafting, mining, and placing.
      2
      MIT

    • Renge Bot

      QDcvd
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables controlling a semi-autonomous Minecraft bot via MCP, supporting tasks like movement, combat, farming, and chatting.
      -

    • haksnbot-tools

      haksndot
      A
      license
      Not graded
      quality
      F
      maintenance
      An MCP server that lets Claude control a Minecraft bot with 40+ actions including movement, combat, crafting, and inventory management. Built on Mineflayer, it supports Microsoft authentication, pathfinding, and auto-reconnect.
      3
      MIT

    • claude-octopus

      xiaolai
      A
      license
      A
      quality
      C
      maintenance
      Wraps the Claude Agent SDK as MCP servers, letting you spawn multiple specialized Claude Code agents — each with its own model, tools, system prompt, and personality — from any MCP client.
      5
      81 npm
      21
      ISC
    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

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing bots, listing their tools, spawning, stopping, and invoking tools. No ambiguity between tools.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern (e.g., spawn_bot, stop_bot, bot_call), using snake_case throughout.

    Tool Count5/5

    With 6 tools covering fleet management operations, the count is well within the ideal range and feels appropriately scoped for the domain.

    Completeness4/5

    The toolset covers essential lifecycle operations (spawn, list, stop, call) but lacks a dedicated tool for inspecting a single bot's detailed status or logs, which is a minor gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources