postmcp
Related Servers
Alternatives to postmcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA standalone MCP server for API testing and management, allowing AI assistants to interact with RESTful APIs through natural language.9 npm29MIT
- AlicenseBqualityDmaintenanceMCP server for generating, validating, running, and reporting Apache JMeter API performance tests from structured API sources.1364 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for end-to-end API testing with PostgreSQL integration, HTTP requests, Go build automation, and debugging support.1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that automates Playwright-based UI and API testing, supporting test case generation from requirements or API specs, and execution with detailed reports.12 npm1MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that dynamically converts any OpenAPI or REST API into MCP tools, allowing for real-time server switching and schema reloading. It supports variable substitution for headers and bodies, enabling seamless authentication and interaction with multiple API environments.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for making API calls with authentication support. Allows configuring multiple API endpoints and performing GET, POST, PUT, DELETE requests, including form data and file uploads.-
TDQS
Scored across 42 tools
Tools are grouped by clear resource prefixes (project_, env_, ws_, history_, suite_, db_) plus dedicated protocol tools (http_request, graphql_request), so most selections are unambiguous. The main overlap is test_run_suite vs suite_load (which also executes immediately) and env_configure vs env_set_variable, but descriptions distinguish these adequately.
The dominant convention is resource_action (project_create, env_set_variable, ws_connect, history_compare, suite_save), applied consistently across nearly all tools. Minor deviations like mcp_usage_guide and test_run_suite break the pattern slightly but remain readable and predictable.
42 tools is heavy for what is essentially an API-testing client, and the surface exceeds the 25-tool threshold where each tool clearly earns its place. Several clusters (five env variable tools, five ws tools, five history tools, four suite tools) could be consolidated without losing capability.
Coverage is strong across the domain: full project and environment lifecycles, import/export, WebSocket sessions, history audit/compare, and saved suites. The main gap is the absence of standalone named-request CRUD outside suites, so reusable single requests can only live in a suite.