@runehand/mcp-server
Related Servers
Alternatives to @runehand/mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseCqualityCmaintenanceAn MCP server that exposes Discord bot actions as tools for LLM clients.291-
- FlicenseNot gradedqualityCmaintenanceMCP server that exposes Discord API as tools, enabling users to manage servers, channels, messages, and roles through natural language.-
- FlicenseNot gradedqualityCmaintenanceMCP server for the Runn API, enabling resource management and reporting through natural language.-
- AlicenseNot gradedqualityDmaintenanceA production-ready MCP server that gives an LLM agent standalone-equivalent control over a Mineflayer Minecraft bot — movement, mining, crafting, inventory, combat, containers, chat, and much more — exposed as 110 strongly-typed tools across 23 groups, with full bot lifecycle management and dual (poll + push) event streaming.68 npm3MIT

fluidattacks-mcpofficial
FlicenseNot gradedqualityDmaintenanceMCP server that provides tools for interacting with the Fluidattacks API-- AlicenseCqualityCmaintenanceAn MCP server that exposes Eduframe resources as tools, allowing users to manage lead records through the Eduframe API. It enables listing, creating, updating, and deleting leads using natural language commands.100MIT
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: bots, flows, conversations, analytics, messaging, and leads. The list/get pairs follow a clear resource-detail distinction, so an agent can reliably select the intended tool.
All tools use lowercase snake_case verb_noun naming: list_*, get_*, send_message, create_lead. The pattern is consistent and predictable across the entire surface.
Nine tools is well-scoped for a workspace/bot/conversation/lead management server. Each tool corresponds to a meaningful operation, and there is no redundant bloat.
Read/query coverage is strong across bots, flows, conversations, leads, and analytics, with messaging and lead creation included. Minor gaps exist—no lead status update, conversation creation/closure, or flow editing—but these are likely handled outside this server's read-and-engage scope.