genskill-mcp
Related Servers
Alternatives to genskill-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA comprehensive MCP server for generating sophisticated GenLayer Intelligent Contracts with AI-native blockchain capabilities.165 npm7MIT
- FlicenseBqualityDmaintenanceMCP server for AI agents to work with GenLayer projects, providing tools to run GenLayer CLI, lint contracts, and deploy contracts with automatic private key handling.45 npm-
- AlicenseAqualityAmaintenanceA local-first MCP server that gives AI coding agents persistent memory and controlled commands. Features a git-backed markdown knowledge vault with FTS5 search, surgical section edits, token-aware context budgeting, and a sandboxed command engine with human approval gates. Works with Claude Code, Cursor, Copilot, Gemini, and more.458316 npm1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA local MCP server that gives AI coding agents persistent memory and context across sessions.24 npmMIT
- FlicenseNot gradedqualityCmaintenanceA self-extending MCP server that enables AI agents to browse the web, execute shell and Node snippets, automate browser workflows, access files and git, communicate with other agents, and use dozens of domain-specific calculation and research tools.-
- AlicenseAqualityAmaintenanceLocal-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.3712 npm5MIT
TDQS
Scored across 46 tools
Most tools have distinct purposes, but there is some overlap among transaction-related tools (e.g., inspect, status, receipt, explain) and contract state retrieval tools (state, code, snapshot, schema). This could cause an agent to select the wrong tool without careful reading.
All 46 tools follow a consistent 'genlayer_verb_noun' pattern with snake_case. The verb and noun are always clearly separated, making the tool set predictable and easy to navigate.
With 46 tools, the surface is very large. While the scope covers many aspects of GenLayer development, the count exceeds the recommended 25+ threshold for 'too many', potentially overwhelming agents and increasing selection errors.
The tool set thoroughly covers the GenLayer lifecycle: scaffolding, linting, testing, workflow planning, contract deployment/interaction, network diagnostics, documentation retrieval, and transaction analysis. No obvious gaps are present.