Rest MCP Server

Rest API tester. Exposed over MCP by the rest mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

1. Create a test cases file named __scenarios__/test_something.json json { "create_something": { "url": "/something", "method": "POST", "status": 200, "request": { "name": "something" }, "response": { "id": 1, "name": "something" } } }

rest-api-tester makes it easy to create REST API tests for your APIs. Though this tool is written in Python, your APIs need not be. This library provides a consistent way to write API tests and perform the necessary validation. It is primarily built to handle traditional, JSON-based APIs, although it has the ability to handle other API formats. Also... rest-api-tester can auto-update your scenario files for you when tests fail!

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at rest-api-tester on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by Alex Schimpf; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Rest's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the rest mcp server does with a few real requests.