Kurlo
Related Servers
Alternatives to Kurlo
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAPI client for coding agents. Sends saved HTTP, GraphQL and gRPC requests, runs collections with their checks, and creates or edits requests over stdio or loopback HTTP, with secret values redacted and calls limited to an allowlist of hosts.1656MIT
- AlicenseNot gradedqualityDmaintenanceA keyboard-first API client that stores requests and environments as plain files, and exposes its workspace over MCP so agents can browse, send, and create requests with vault access.304 npmMIT
- AlicenseBqualityCmaintenanceStateful interactive HTTP REPL and Agentic MCP engine for API navigation and testing.417 PyPIMIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with Istek API Client for managing workspaces, collections, environments, variables, and request history. Allows natural language control of API development workflows including creating collections, adding requests, and managing environment configurations.-

@klappay/mcpofficial
AlicenseNot gradedqualityAmaintenanceLets an AI assistant run locally over stdio to inspect and test the Klap Core API — looking up charges and timelines, listing webhooks and deliveries, checking accepted token/network pairs, querying metrics, and, in test mode, creating charges, re-checking them on-chain, retrying deliveries and driving sandbox payments. Live environments are read-only unless writes are explicitly opted into, and money-moving or endpoint-management operations are never exposed.0MIT- AlicenseNot gradedqualityAmaintenanceAPI client with an MCP server. Your agent builds collections from your codebase, runs requests, writes e2e flows, and exports them to GitHub Actions CI automatically. Category: Developer Tools04ISC
TDQS
Scored across 15 tools
Most tools have clearly distinct purposes, and the saved-vs-one-off split between run_request and send_request is explicit. However, generate_tests overlaps with save_example (both save a response as an example), and diagnose_last_failure shares some surface with get_history_entry, creating minor ambiguity.
All tools use a consistent snake_case verb_noun pattern (save_request, list_history, run_collection, etc.). The verbs vary appropriately by action while the structure remains predictable throughout.
15 tools is at the upper end of the ideal range but appropriate for a Postman-like API client covering requests, collections, environments, history, and testing. Each tool earns its place without obvious redundancy.
Request lifecycle is well covered (save, delete, list, get, run, send), but collection management is incomplete: only create_collection exists, with no list, update, or delete. Environment and example lifecycles also lack delete operations, leaving notable gaps for an agent to manage the workspace fully.