Skip to main content
Glama

@kongyo2/mcpdevmcp

LLMエージェントが他のMCPサーバーを開発、デバッグ、検査するためのMCPサーバーです。

MCP Inspector CLIの機能をラップし、エージェントが自身の環境から直接プログラム的に他のMCPサーバーの挙動(ツールの確認、リソースの読み取り、プロンプトのテスト)を検証できるようにします。

特徴

  • プログラムによる検査: ターゲットとなるMCPサーバーのツール一覧・実行、リソース一覧・読み取り、プロンプト一覧・取得が可能。

  • エージェントフレンドリー: LLMエージェントが自律的にMCPサーバーを開発・検証するために設計。

  • 柔軟なトランスポート: stdio(ローカルコマンド実行)と sse/http(リモートURL接続)の両方に対応。

Related MCP server: MCP Inspector as MCP Server

クイックスタート設定

MCPクライアント(例: claude_desktop_config.json)の設定に追加してください:

{
  "mcpServers": {
    "mcpdev": {
      "command": "npx",
      "args": ["-y", "@kongyo2/mcpdevmcp"]
    }
  }
}

利用可能なツール

すべてのツールは target 引数を受け取ります。これにはローカルの実行コマンドまたはリモートURLを指定できます。

1. mcpdev_inspector_list_tools

ターゲットMCPサーバーで利用可能なすべてのツールを一覧表示します。

// 例: リモートサーバーを検査
{
  "target": "https://mcp.deepwiki.com/sse",
  "transport": "sse"
}

2. mcpdev_inspector_call_tool

ターゲットMCPサーバー上の特定のツールを実行します。

// 例: ローカルサーバーのツールを実行
{
  "target": "node ./my-server/dist/index.js",
  "transport": "stdio",
  "tool_name": "calculator",
  "tool_args": { "a": 1, "b": 2, "op": "add" }
}

3. mcpdev_inspector_list_resources

ターゲットMCPサーバーのリソース一覧を取得します。

4. mcpdev_inspector_read_resource

特定のリソースの内容を読み取ります。

5. mcpdev_inspector_list_prompts

ターゲットMCPサーバーのプロンプト一覧を取得します。

6. mcpdev_inspector_get_prompt

特定のプロンプトテンプレートを取得します。

開発について

このプロジェクトは、高品質かつモダンなTypeScriptのベストプラクティスに基づいて構築されています:

  • TypeScript: Strictモード, ES2022

  • エラーハンドリング: neverthrow を使用したResult型(ビジネスロジック内での例外スロー禁止)

  • Linting: oxlint による高速なLint

ビルド

npm install
npm run build

テスト

# Inspectorを使用して、このサーバー自身のツール一覧を取得
npx @modelcontextprotocol/inspector --cli --method tools/list node dist/index.js

ライセンス

MIT

Available Tools

6 tools
mcpdev_inspector_call_toolCall MCP Server ToolA
Destructive

Execute a tool on a target MCP server.

Use this to invoke a specific tool on the target server with provided arguments.

Args:

  • target (string): Target MCP server - command or URL

  • transport ('stdio' | 'sse' | 'http'): Transport type

  • timeout_ms (number): Timeout in milliseconds (default: 60000)

  • tool_name (string): Name of the tool to call

  • tool_args (object): Arguments to pass to the tool

Returns: The tool's response content.

Examples:

  • { target: "node server.js", tool_name: "get_weather", tool_args: { city: "Tokyo" } }

Inputs: target (required), tool_name (required), transport, timeout_ms, +1 more.

mcpdev_inspector_get_promptGet MCP Server PromptA
Read-onlyIdempotent

Get a specific prompt from a target MCP server.

Use this to retrieve and render a prompt template with provided arguments.

Args:

  • target (string): Target MCP server - command or URL

  • transport ('stdio' | 'sse' | 'http'): Transport type

  • timeout_ms (number): Timeout in milliseconds (default: 60000)

  • prompt_name (string): Name of the prompt to get

  • prompt_args (object): Arguments to pass to the prompt template

Returns: The rendered prompt messages.

Inputs: target (required), prompt_name (required), transport, timeout_ms, +1 more.

mcpdev_inspector_list_promptsList MCP Server PromptsA
Read-onlyIdempotent

List all available prompts from a target MCP server.

Use this to discover what prompt templates a target MCP server provides.

Args:

  • target (string): Target MCP server - command or URL

  • transport ('stdio' | 'sse' | 'http'): Transport type

  • timeout_ms (number): Timeout in milliseconds (default: 60000)

Returns: JSON object with 'prompts' array containing prompt definitions.

Inputs: target (required), transport, timeout_ms.

mcpdev_inspector_list_resourcesList MCP Server ResourcesA
Read-onlyIdempotent

List all available resources from a target MCP server.

Use this to discover what resources (data/content) a target MCP server exposes.

Args:

  • target (string): Target MCP server - command or URL

  • transport ('stdio' | 'sse' | 'http'): Transport type

  • timeout_ms (number): Timeout in milliseconds (default: 60000)

Returns: JSON object with 'resources' array containing resource URIs and metadata.

Inputs: target (required), transport, timeout_ms.

mcpdev_inspector_list_toolsList MCP Server ToolsA
Read-onlyIdempotent

List all available tools from a target MCP server.

Use this to discover what tools a target MCP server provides. Returns tool names, descriptions, and input schemas.

Args:

  • target (string): Target MCP server - command (e.g., 'node server.js') or URL

  • transport ('stdio' | 'sse' | 'http'): Transport type (auto-detected if not specified)

  • timeout_ms (number): Timeout in milliseconds (default: 60000)

Returns: JSON object with 'tools' array containing tool definitions.

Examples:

  • Local server: { target: "node dist/index.js", transport: "stdio" }

  • Remote SSE: { target: "https://mcp.example.com/sse", transport: "sse" }

Inputs: target (required), transport, timeout_ms.

mcpdev_inspector_read_resourceRead MCP Server ResourceA
Read-onlyIdempotent

Read a specific resource from a target MCP server.

Use this to fetch the content of a resource by its URI.

Args:

  • target (string): Target MCP server - command or URL

  • transport ('stdio' | 'sse' | 'http'): Transport type

  • timeout_ms (number): Timeout in milliseconds (default: 60000)

  • uri (string): Resource URI to read

Returns: The resource content (text or base64-encoded blob).

Inputs: target (required), uri (required), transport, timeout_ms.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: call_tool executes tools, get_prompt retrieves prompts, list_prompts lists prompts, list_resources lists resources, list_tools lists tools, and read_resource reads resources. The descriptions clearly differentiate their functions, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern with the prefix 'mcpdev_inspector_' followed by a verb_noun structure (e.g., call_tool, get_prompt, list_prompts). This predictability makes the tool set easy to navigate and understand.

    Tool Count5/5

    With 6 tools, this server is well-scoped for its purpose of inspecting and interacting with MCP servers. Each tool serves a specific role in discovery and execution, with no redundancy, making the count appropriate and efficient.

    Completeness5/5

    The tool set provides complete coverage for the MCP server inspection domain, including listing tools, prompts, and resources, reading resources, getting prompts, and calling tools. There are no obvious gaps, enabling agents to perform all essential inspection and interaction tasks.

    Related MCP Connectors

    Related MCP Servers

    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides programmatic access to MCP server testing, debugging, and validation capabilities by wrapping the official MCP Inspector. Enables users to test tools, validate protocol compliance, discover server capabilities, and debug MCP servers through natural language interactions.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLMs to inspect and test other MCP servers by listing and calling their tools, reading resources, and getting prompts. Supports stdio, SSE, and HTTP transports for both local and remote MCP server inspection.
      7
      4 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to programmatically inspect, test, and validate other MCP servers by exposing MCP Workbench capabilities as structured tools. It supports automated test spec generation, execution, and detailed failure analysis to ensure server reliability.
      4
      7 npm
      Apache 2.0