Dev Proxy Tools

io.github.dev-proxy-toolsPublished by GitHub account dev-proxy-toolsv0.3.1Updated Oct 24, 2026

MCP server for Dev Proxy that enables AI assistants to interact with Dev Proxy.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local MCP server for Dev Proxy that lets an assistant look up Dev Proxy docs, best practices and the installed version to help write configurations.

What you can do
  • Find Dev Proxy documentation matching a natural-language query
  • Retrieve best practices for configuring and using Dev Proxy
  • Read the installed Dev Proxy version to keep generated configurations compatible
When to use it
Useful when you work with Dev Proxy, the API simulator for testing error handling, rate limits, slow responses and mock APIs, and want an assistant to draft configurations or answer questions grounded in its documentation.
Requirements
Runs locally over stdio via npx, so Node.js LTS is needed, plus Dev Proxy installed globally on the machine. No environment variables or authentication are declared.
Before you install
The server only reads documentation, best practices and version information; it does not appear to change your Dev Proxy setup. It requires a global Dev Proxy installation, and the README notes a preview build is available under a separate npm tag.

Installation

In SourceWeft

  1. Open Dev Proxy Tools in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Dev Proxy MCP Server

[Install with NPX in VS Code] [Install with NPX in VS Code Insiders]

A Model Context Protocol (MCP) server for Dev Proxy that enables AI assistants to interact with Dev Proxy capabilities using the MCP standard. Use this server to:

  1. Create Dev Proxy configurations using natural language
  2. Get contextual help for working with Dev Proxy
  3. Discover Dev Proxy features and capabilities

[Screenshot of Visual Studio Code with GitHub Copilot chat pane open. GitHub Copilot works in assistant mode and uses the Dev Proxy MCP server to retrieve relevant information and create Dev Proxy configuration that matches the specified prompt.]

What is Dev Proxy?

Dev Proxy is an API simulator that helps you effortlessly test your app beyond the happy path. It allows you to:

  • Test API error handling: See how your app responds to API errors without changing your code
  • Verify rate limit handling: Simulate API rate limits to improve user experience
  • Test slow API responses: See how your app handles slow APIs to implement necessary affordances
  • Create mock APIs: Quickly stand up mock APIs without writing code you won't ship

Dev Proxy works with any type of app and tech stack as it intercepts network requests at the proxy level.

What This Package Does

This package provides a Model Context Protocol (MCP) server interface to Dev Proxy. It allows AI assistants and other MCP-compatible clients to:

  1. Find Dev Proxy documentation using natural language queries
  2. Get the installed Dev Proxy version

Prerequisites

Usage

To set up and use the MCP server, refer to the instructions for your MCP host, such as Visual Studio Code. The Dev Proxy MCP server is published on npm under @devproxy/mcp.

Use the following values:

  • Type: stdio
  • Command: npx
  • Arguments:
    • -y
    • @devproxy/mcp
  • Environment: none

[!TIP] If you want to test the preview version of the server using @devproxy/mcp@next.

Connect with an MCP Client

This MCP server exposes the following tools:

GetBestPractices

Gets a list of best practices for configuring and using Dev Proxy. Call it for any code generation or operation involving Dev Proxy. These best practices do not change so once it has been called during the current session, you do not need to invoke it again.

markdown
_Best practices in markdown_
FindDocs

Finds relevant Dev Proxy documentation related to a specific query.

json
{  "query": "How to simulate API errors"}
GetVersion

Gets the currently installed Dev Proxy version. This is useful to ensure that the generated configuration is compatible with the installed version of Dev Proxy.

json
{}

Development

bash
# Clone the repositorygit clone https://github.com/waldekmastykarz/dev-proxy-mcp.gitcd dev-proxy-mcp
# Install dependenciesnpm install
# Build the projectnpm run build
# Run the servernpm start
# Run with MCP inspector for debuggingnpm run inspect

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

License

This project is licensed under the MIT License - see the LICENSE file for details.

Related Projects

Source: README.md at commit 4352a45

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts