Which integrations are available for this server?

Built on the npm ecosystem, using the official @modelcontextprotocol/inspector package for MCP server inspection and validation capabilities

How do I use MCP Inspector Assistant?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Inspector Assistant start inspector for my weather server in UI mode" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

MCP Inspector Assistant

A powerful MCP server that wraps the official MCP Inspector to provide programmatic access to server testing, debugging, and validation capabilities.

Features

Server Inspection: Start the MCP Inspector UI or CLI for any MCP server
Tool Testing: Test individual tools with specific arguments
Protocol Validation: Verify MCP protocol compliance
Capability Discovery: List all tools, resources, and prompts of a server
Debug Mode: Run servers with debug output and capture logs
Automatic Updates: Uses the official inspector package for latest features

Related MCP server: MCP HTTP Requests

Installation

npm install

Usage

As MCP Server (stdio)

npm start

As HTTP Service

npm run http

The HTTP service runs on port 8206 by default (configurable via MCP_INSPECTOR_PORT).

Available Tools

start_inspector

Start the MCP Inspector UI or CLI for a specific server.

{ "tool": "start_inspector", "arguments": { "serverPath": "/path/to/mcp-server/standalone.js", "port": 5173, "mode": "ui" } }

stop_inspector

Stop any running MCP Inspector instance.

{ "tool": "stop_inspector", "arguments": {} }

test_tool

Test a specific tool on an MCP server.

{ "tool": "test_tool", "arguments": { "serverPath": "/path/to/server.js", "toolName": "myTool", "arguments": { "param1": "value1" } } }

list_server_capabilities

List all capabilities (tools) of an MCP server.

{ "tool": "list_server_capabilities", "arguments": { "serverPath": "/path/to/server.js" } }

validate_protocol

Validate that a server follows MCP protocol correctly.

{ "tool": "validate_protocol", "arguments": { "serverPath": "/path/to/server.js", "checks": ["initialization", "tools"] } }

debug_server

Run a server with debug output and capture logs.

{ "tool": "debug_server", "arguments": { "serverPath": "/path/to/server.js", "duration": 30 } }

Examples

Testing a Gateway Assistant Tool

# Using HTTP API curl -X POST http://localhost:8206/tools/test_tool \ -H "Content-Type: application/json" \ -d '{ "serverPath": "/path/to/mcp-gateway-assistant/standalone.js", "toolName": "check_service_health", "arguments": { "services": ["secrets", "logging"] } }'

Starting Inspector UI

# Start inspector for secrets assistant curl -X POST http://localhost:8206/tools/start_inspector \ -H "Content-Type: application/json" \ -d '{ "serverPath": "/path/to/mcp-secrets-assistant/standalone.js", "mode": "ui" }'

Testing

# Test MCP mode npm test # Test HTTP mode npm run test:http

Integration with Claude Desktop

Add to your claude_desktop_config.json:

{ "mcpServers": { "inspector-assistant": { "command": "node", "args": [ "/path/to/mcp-inspector-assistant/standalone.js" ], "env": {} } } }

Dependencies

This assistant uses the official @modelcontextprotocol/inspector package, ensuring compatibility with the latest MCP Inspector features and updates.

This server cannot be installed

-

security - not tested

-

license - not tested

-

quality - not tested

How are these scores calculated?