home / mcp / kongyo mcp devmcp server
Provides programmatic inspection of MCP servers via tools, resources, and prompts for testing and development.
Configuration
View docs{
"mcpServers": {
"kongyo2-mcpdevmcp": {
"command": "npx",
"args": [
"-y",
"@kongyo2/mcpdevmcp"
]
}
}
}You can use this MCP server to programmatically inspect and validate other MCP servers from your own environment. It wraps the Inspector CLI capabilities so an LLM agent or automation can list tools, read resources, and test prompts on target MCP servers through flexible transports like local commands or remote URLs.
You connect your MCP client to the mcpdev MCP server to perform inspections from your own environment. The server supports two transport methods: stdio for local command execution and http/sse for remote MCP URLs. You can run a sequence of actions to explore a target MCP server: list all available tools, execute a specific tool, enumerate resources, read a resource, list prompts, and retrieve a prompt template. Use these steps to validate behavior, compare results across targets, and verify prompt responses without leaving your development workflow.
To start, configure your MCP client to include the mcpdev server. The quick start configuration shows how to add the server so your client can invoke it locally with a single command. Then you can run inspector-like commands against a target to confirm it exposes the expected tools, resources, and prompts.
Prerequisites: ensure you have Node.js and npm installed on your system. You should be able to run npm commands from your shell.
Install dependencies for the MCP development server and build the project.
npm install
npm run buildAdd the MCP server to your MCP client configuration so you can invoke it from your environment.
{
"mcpServers": {
"mcpdev": {
"command": "npx",
"args": ["-y", "@kongyo2/mcpdevmcp"]
}
}
}This MCP server enables programmatic inspection of target MCP servers. It supports both local execution and remote connections, letting you validate tools, resources, and prompts directly from your development environment. When you write automation or agents, you can rely on the same capabilities you would manually invoke through the Inspector.
Lists all tools available on the target MCP server.
Executes a specific tool on the target MCP server with provided arguments.
Retrieves the list of resources exposed by the target MCP server.
Reads the content of a specified resource from the target MCP server.
Gets the list of prompt templates available on the target MCP server.
Fetches a specific prompt template from the target MCP server.