mcp

This MCP server provides a standard MCP interface to the Dev Proxy tools. It exposes three primary operations that an MCP client can invoke: GetBestPractices, FindDocs, and GetVersion. GetBestPractices returns a stable set of best practices for configuring and using Dev Proxy, useful for guiding automation and code generation. FindDocs accepts a query payload and returns relevant Dev Proxy documentation to help users understand capabilities or troubleshooting steps. GetVersion reports the currently installed Dev Proxy version to ensure compatibility with generated configurations. Use these tools through your MCP client by sending the appropriate requests to the server and consuming the responses to drive your automation workflows.

Prerequisites:

• Node.js LTS installed on your machine
• Optional: Dev Proxy installed globally or available via npm registry

Installation steps:

1. Ensure Node.js is installed. Verify with: node --version
2. Install the MCP server package via NPX or npm:
   • NPX (recommended for quick run): npx -y @devproxy/mcp
   • Global install (alternative): npm install -g @devproxy/mcp
3. Start the MCP server using the recommended command: For NPX usage, configure your MCP host to run: npx -y @devproxy/mcp If you installed globally: mcp start (or the specific startup script provided by the package)
4. Verify the server is reachable by connecting an MCP client or using the included GetVersion tool to confirm the installed version.

Tip: You can also test the preview version using @devproxy/mcp@next when needed.

Notes and tips:

• This MCP server uses the standard NPX invocation: command npx with arguments -y and @devproxy/mcp. No extra environment variables are required by default.
• If you want to test a preview version, you can reference @devproxy/mcp@next in your MCP client configuration.
• The server exposes three tools via MCP: GetBestPractices, FindDocs, and GetVersion. Use FindDocs with a query payload to retrieve relevant documentation, and GetVersion to ensure compatibility with your Dev Proxy installation.
• If you encounter issues starting the server, confirm Node.js compatibility with your Dev Proxy version and verify network access for NPX package retrieval.