SoftProbe MCP Server

An MCP server for managing API test data and resources.

A Model Context Protocol (MCP) server implementation for managing API test data and resources.

This server implements the MCP protocol to provide a structured way to access and manage API test data. It uses a hierarchical organization model where resources are scoped under organizations and applications.

This server currently implements MCP using Tools (as Resources and Roots are not yet supported by Cursor). The server provides the following tools:
- list-APIs: Lists all recorded APIs available in Softprobe
- list-api-record-ids: Lists all recorded API records for a specific operation
- getApiSamples: Retrieves recorded API interaction samples in JSON format

The server can be configured using environment variables or through themcp.jsonconfiguration file:

{ "mcpServers": { "mcp-server-softprobe": { "command": "npx", "args": [ "-y", "@softprobe/mcp-server" ], "env": { "SOFTPROBE_API_URL": "https://api-onpremise-gcp.softprobe.ai", "SOFTPROBE_ACCESS_TOKEN": "<your-access-token>" } } } }

- SOFTPROBE_API_URL: Base URL for the Softprobe API
- SOFTPROBE_ACCESS_TOKEN: Authentication token for API access

softprobe://orgs/{orgId} └── softprobe://orgs/{orgId}/apps/{appId} └── API Samples (resources)

- Organization Root: Represents a top-level organization
- Application Root: Represents an application within an organization
- API Samples: Test data resources scoped to specific applications

- softprobe://apiSamples/{orgId}/{appId}/{apiPath}: Access API test samples

// Client calls roots/list // Server returns: { roots: [ { uri: 'softprobe://orgs/{orgId}', name: 'Organization Root' }, { uri: 'softprobe://orgs/{orgId}/apps/{appId}', name: 'Application Root' } ] }

// Client calls roots/resolve with: // uri: softprobe://orgs/123 // Server returns: { root: { uri: 'softprobe://orgs/123', name: 'Organization Root' } }

// Client calls resources/list // Server returns resources under org/123 // Client calls softprobe/apiSamples/123/456/users // Server returns API samples for the users endpoint

// Client calls roots/resolve with: // uri: softprobe://orgs/123/apps/456 // Server returns: { root: { uri: 'softprobe://orgs/123/apps/456', name: 'Application Root' } } // Now all resource access is scoped to app/456

{ samples: [ { name: "test_case_name", request: { method: "POST", body: { / request body / } }, response: { status: 200, body: { / response body / } } } ] }

- Keep test data separate from production
- Organize tests by application/feature
- Maintain test data versioning

- Retrieve test cases for validation
- Compare actual responses with expected
- Generate test reports

- Use different roots for different environments
- Maintain environment-specific test data
- Safe testing without affecting production

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

An MCP server for interacting with the Postman API, requiring an API key.

Adds possibility to work with testing management via MCP

An enhanced Apifox MCP service providing comprehensive API management capabilities for Claude Desktop and Cursor.

This MCP Server accepts swagger/postman documents as input. It then generates API & Load test scenarios, executes the tests and generates the execution report.

A Model Context Protocol (MCP) server for creating, managing, and executing Bruno API testing collections. Supports both .bru and .yml (opencollection) formats with built-in security hardening.

Execute Bruno collections using the Bruno CLI, with support for environment files and detailed test results.

An MCP server exposing Hoverfly as a programmable API simulation tool for AI assistants.

A free public REST API for testing and prototyping, powered by JSONPlaceholder.

Postman for MCP — search 156 servers, inspect tools with schema visualizer, test live

An AI-native API testing platform for generating scenarios, executing tests, and analyzing results.