Skip to main content
Glama
api-testing-mcp

api-testing-mcp

API Testing Using MCP Server (End User Guide)

A ready-to-use Model Context Protocol (MCP) server for HTTP API testing, powered by Playwright. This guide helps you install, configure, and run the MCP server locally as an npm package.

๐Ÿ“‹ Table of Contents

Related MCP server: Playwright MCP Server

๐ŸŒŸ Overview

The Playwright API MCP Server enables API testing via the Model Context Protocol. It supports GET, POST, PUT, and DELETE requests.

๐Ÿ“‹ Prerequisites

๐Ÿš€ Setup

  1. Create a Node.js Project in VS Code:

    • Create a new folder with a meaningful name (e.g. my-project).

    • Open the folder in Visual Studio Code.

    • Launch the integrated terminal (via View > Terminal).

    • Choose your preferred shell (e.g. Git Bash, Command Prompt, or PowerShell).

    • Run the following command to initialise the project:

      npm init -y
    • This will generate a package.json file with default settings

  2. Install the MCP Server Package

    • Now, run the below command to install the mcp server package.

      npm i @automate-io/api-testing-mcp@latest

โš™๏ธ Configurations

  1. Open your project folder in VS Code

  2. If the mcp.json file does not already exist, create it inside the root/.vscode/ directory. If the file is already present, you can skip this step

  3. Add the api-testing-mcp configuration under the servers key in the mcp.json file, as shown below

    {
      "servers": {
        "api-testing-mcp": {
          "type": "stdio",
          "command": "node",
          "args": ["node_modules/@automate-io/api-testing-mcp/dist/server.js"],
          "cwd": "${workspaceFolder}"
        }
      },
      "inputs": []
    }
  • โ—Important Note:If you are working in a monorepo, ensure the args field in your mcp.json file is correctly configured. Refer to the Monorepo MCP Configuration guide for detailed instructions. If your test code resides in a standalone repository, no changes are needed, you are good to go.

๐Ÿ“– Getting started with MCP testing

  1. Start the MCP Server

  • Click the highlighted start button in the mcp.json file as shown below to start the MCP server.

  1. Input the prompt

  • Open GitHub Copilot chat window in VS Code with Agent mode selected.

  • Enter a prompt that outlines the API you wish to test.

โœ… Example scenarios and prompts for MCP server usage

โญ๏ธ Upcoming enhancements

  • Implement schema validations for response payloads

  • Add reusable resources to support API testing workflows

  • Introduce predefined prompts to streamline common scenarios

  • Provide a sample HTML test report template to guide LLm about the layout and formatting

  • Refactor existing logic and implement robust error handling to improve reliability and maintainability

๐Ÿ”ง Troubleshooting

  • Server not running?
    Double-check your MCP client configuration.

  • Module not found?
    Reinstall the package:

    npm i @automate-io/api-testing-mcp@latest

๐Ÿ†˜ Support


๐Ÿ‘ Enjoy exploring and validating your APIs !

Available Tools

4 tools
send-delete-requestD
Destructive

send the delete request

Inputs: url (required), headers, pathParams, queryParams, +1 more.

send-get-requestC
Read-onlyIdempotent

send the get request

Inputs: url (required), headers, pathParams, queryParams, +1 more.

send-post-requestD

send the post request

Inputs: url (required), data, headers, timeout.

send-put-requestD
Idempotent

send the put request

Inputs: url (required), data, headers, pathParams, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelogโ€ฆ

    TDQS

    C2.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool corresponds to a distinct HTTP method (DELETE, GET, POST, PUT) with no overlap, making it trivial for an agent to select the correct one.

    Naming Consistency5/5

    All tools follow a consistent pattern: 'send-{method}-request' with lowercase and hyphens, ensuring predictability.

    Tool Count5/5

    With 4 tools covering the main HTTP methods (CRUD), the count is well-suited for an API testing serverโ€”neither too few nor too many.

    Completeness4/5

    The set covers the most common HTTP methods, but omits PATCH and other less common ones. For basic testing, it is sufficiently complete.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.
      32
      13,875 npm
      5,682
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides browser automation capabilities using Playwright, enabling LLMs to interact with web pages, take screenshots, generate test code, scrape web content, and execute JavaScript in a real browser environment.
      32
      13,875 npm
      MIT