mcp-tool-builder
作業中 - 注意して使用してください - Windows
MCP ツールビルダー
Claude Desktop などの MCP クライアントを通じて LLM が新しいツールを動的に作成できるようにする MCP サーバー。
特徴
自然言語で記述して新しいツールを作成する
新しいツールを使用するにはクライアントの再起動が必要です (Claude Desktop)
新しいツールは、...\mcp-tool-builder\tools に Python スクリプトレットとして保存されます。
新しいツール定義は ...\mcp-tool-builder\tools\tools.json に保存されます。
Related MCP server: my-mcp-server
インストール時に含まれるツールの例
get_bitcoin_price: CoinGeckoから現在のビットコイン価格を取得します
get_weather_forecast: 米国の郵便番号の天気を取得します(geopy を使用)
新しいツールの作成
Claude Desktop の create_tool コマンドを使用して(または強く推奨します)新しいツールを動的に作成します。
インストール
このリポジトリをクローンする
依存関係をインストールします:
cd mcp-tool-builder
uv venv
.venv\Scripts\activate
uv pip install -e .Claude Desktopでの使用
claude_desktop_config.jsonに追加:
{
"mcpServers": {
"tool-builder": {
"command": "uv",
"args": [
"--directory",
"PATH_TO\\mcp-tool-builder",
"run",
"tool-builder"
]
}
}
}Available Tools
4 toolscreate_toolC
Create a new Python tool with specified functionality
Inputs: tool_name (required), description (required), code (required).
get_bitcoin_priceA
Gets current Bitcoin price in USD from CoinGecko API
Inputs: no named parameters.
get_weather_forecastC
Retrieves weather forecast for a given ZIP code using NWS API
Inputs: zip_code (required).
list_available_toolsB
List all currently available tools
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
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.
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.
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.
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.
Related MCP Connectors
MCP server for progressive tool usage at any scale (see https://klavis.ai)
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
Related MCP Servers
- 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.3-
- 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.-
- AlicenseNot gradedqualityDmaintenanceCreates, manages, and registers custom MCP servers for Claude Desktop. Enables users to generate and configure new MCP servers through natural language.11MIT
- 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.55 npmMIT