Shellagent MCP Server
Related Servers
Alternatives to Shellagent MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that supports STDIO, SSE and Streamable HTTP protocols for AI model interactions.5 npm1MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables seamless integration between Claude AI and development tools like VSCode, Augment, Vercel, Airtable, and Square.7MIT
- AlicenseBqualityCmaintenanceA model context protocol server that enables applications to use stackzero-labs/ui components through the MCP protocol, supporting both standalone operation and integration with Claude Desktop and Cursor.1226 npm5MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects multiple AI models into a single workflow, enabling multi-model orchestration, conversation continuity, and tools like code review, planning, and CLI-to-CLI bridging.-
- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server for integrating with various LLM clients like Claude Desktop.1164MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that bridges MCP clients with local LLM services, enabling seamless integration with MCP-compatible applications through standard tools like chat completion, model listing, and health checks.-
TDQS
Scored across 1 tool
With only one tool, there is no possibility for confusion or overlap between tools. The tool 'get_app_info' has a clear, singular purpose that cannot be misselected against other tools.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'get_app_info' follows a clear verb_noun pattern, and there are no other tools to compare it against for inconsistency.
A single tool is too few for a server named 'Shellagent MCP Server', which suggests a broader scope related to shell operations or agent management. This minimal toolset feels thin and incomplete for such a domain, limiting functionality significantly.
The tool surface is severely incomplete. For a shell agent server, obvious gaps include basic operations like executing commands, listing processes, managing files, or interacting with the system. The single tool 'get_app_info' does not cover the expected domain at all, leading to dead ends for agents.