MCP REST API Tester

Created By
dkmakera year ago
A TypeScript-based MCP server that enables testing of REST APIs through Cline. This tool allows you to test and interact with any REST API endpoints directly from your development environment.
Overview

What is MCP REST API Tester?

MCP REST API Tester is a TypeScript-based tool that allows developers to test and interact with REST API endpoints directly from their development environment using Cline.

How to use MCP REST API Tester?

To use the MCP REST API Tester, install it via Smithery or npm, configure Cline with appropriate instructions, and run tests on your API endpoints.

Key features of MCP REST API Tester?

  • Supports various HTTP methods (GET, POST, PUT, DELETE)
  • Handles multiple authentication methods (Basic, Bearer, API Key)
  • Provides detailed response information
  • Configurable SSL verification options
  • Automatic endpoint normalization

Use cases of MCP REST API Tester?

  1. Testing specific API endpoints during development
  2. Debugging API responses to ensure functionality
  3. Validating API request/response formats dynamically

FAQ from MCP REST API Tester?

  • What authentication methods does it support?

The tool supports Basic Authentication, Bearer Token, and API Key.

  • Can I test local APIs?

Yes, you can use it to test local development servers as well.

  • How do I handle sensitive data?

Proper configurations are provided to handle sensitive data securely.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dkmaker
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago