F
licenseNot graded
qualityF
maintenanceCreates, manages, and registers custom MCP servers for Claude Desktop. Enables users to generate and configure new MCP servers through natural language.
11
-
mcp-tool-builder
by hanweg
Related Servers
Alternatives to mcp-tool-builder
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.75 npm-
- AlicenseAqualityDmaintenanceA meta-MCP server that dynamically manages and invokes any MCP server on the fly, enabling runtime addition, removal, and tool invocation without restarting Claude Code.59 npmMIT
- FlicenseCqualityDmaintenanceA server built with mcp-framework that allows users to extend Claude's capabilities by adding custom tools that can be used through the Claude Desktop client.375 npm-
- FlicenseNot gradedqualityCmaintenanceSelf-evolving MCP server that automatically discovers, generates, and registers new tools on demand using AI, enabling dynamic tool expansion without manual intervention.-
- AlicenseCqualityDmaintenanceMCP server for Claude Code self-management, enabling hot restart and context compaction commands.12MIT
TDQS
B3/5.0
Scored across 4 tools
Disambiguation3/5
The tools have distinct purposes (tool creation, Bitcoin price, weather forecast, tool listing), but the domain is unclear—'create_tool' and 'list_available_tools' suggest a tool management server, while the other two are unrelated utilities. This mismatch could confuse agents about the server's scope, though individual tools are not directly overlapping.
Naming Consistency4/5
Three tools follow a consistent verb_noun pattern (create_tool, get_bitcoin_price, get_weather_forecast), but 'list_available_tools' uses 'list' instead of 'get', breaking full consistency. Overall, naming is mostly predictable and readable with only minor deviation.
Tool Count3/5
With 4 tools, the count is reasonable for a small utility set, but it feels thin for a 'tool-builder' server that might imply more comprehensive tool management. The inclusion of unrelated utilities (Bitcoin, weather) makes the scope ambiguous, affecting appropriateness.
Completeness2/5
If the domain is tool management, there are significant gaps: no update, delete, or test tools, and the unrelated utilities don't fit. If it's a general utility server, coverage is sparse and random. In either case, the surface is incomplete for coherent agent workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues