home / mcp / mcp rest api tester mcp server

MCP REST API Tester MCP Server

Provides REST API testing capabilities with multiple authentication methods, detailed responses, and configurable headers via an MCP workflow.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "dkmaker-mcp-rest-api": {
      "command": "node",
      "args": [
        "C:/Users/<YourUsername>/AppData/Roaming/npm/node_modules/dkmaker-mcp-rest-api/build/index.js"
      ],
      "env": {
        "AUTH_BEARER": "your-token",
        "HEADER_Accept": "application/json",
        "REST_BASE_URL": "https://api.example.com",
        "AUTH_APIKEY_VALUE": "your-api-key",
        "AUTH_BASIC_PASSWORD": "your-password",
        "AUTH_BASIC_USERNAME": "your-username",
        "HEADER_Custom-Client": "my-client",
        "HEADER_X-API-Version": "2.0",
        "REST_ENABLE_SSL_VERIFY": "false",
        "AUTH_APIKEY_HEADER_NAME": "X-API-Key",
        "REST_RESPONSE_SIZE_LIMIT": "10000"
      }
    }
  }
}

You can test and interact with REST API endpoints directly from your development environment by using an MCP server designed for REST API testing. This server enables you to validate endpoints, authentication methods, response formats, and performance while integrating with MCP clients like Claude and Cline for streamlined workflows.

How to use

Install the MCP REST API Tester and configure it in your MCP client to begin testing REST endpoints. Use the provided environment variables to set the base URL, authentication method, SSL behavior, and optional headers. The tool supports GET, POST, PUT, DELETE, and PATCH requests, returns detailed response information, and allows you to manage request bodies and response sizes.

How to install

Prerequisites: Node.js and npm must be installed on your machine.

Install the MCP REST API Tester globally with npm.

npm install -g dkmaker-mcp-rest-api

Additional sections

Configuration overview: You can configure authentication, base URL, SSL verification, response size limits, and custom headers via environment variables. Choose one authentication method at a time: Basic Authentication (username/password), Bearer Token, or API Key.

Security considerations: Disable SSL verification only for development or testing against self-signed certificates. Keep sensitive credentials secure and avoid exposing API keys or credentials in shared environments.

Usage examples that you can apply through your MCP client include testing specific endpoints, validating responses, and checking error handling or response times.

Troubleshooting notes: Ensure the REST base URL is correct, verify that authentication details are valid, and confirm that any required headers are being sent with requests. Restart the MCP server after configuration changes.

Available tools

test_request

Test REST API endpoints using GET, POST, PUT, DELETE, and PATCH with detailed response information and support for various authentication methods.