Keploy
io.github.keploy/mcp · v1.0.0 · MCP 2025-06-18
End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.
Reachability
reachable
checked 2026-07-14 04:07 UTC
Registry status active
Tools pinned 7
0de0c9c0de7e
Tools last changed
unchanged since first capture 2026-07-14
Provenance
Registry namespace io.github.keploy
(GitHub-account verified by the official registry)
Repository
github.com/keploy/keploy
Remote endpoints
https://api.keploy.io/client/v1/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-07-14 04:07 | first capture | 7 tools pinned |
Pinned tool definitions (7)
| Tool | Description |
|---|---|
| devloop_begin_oauth_install | Start the Path B agent-walked install for the V1 flow. Returns a playbook the AI walks with the dev to land a kep_* PAT in their editor's MCP config. Current implementation routes through app.keploy.io/settings/api-keys (the existing... |
| devloop_setup_instructions | Return the V1 "user maintains the flow" install guide — covers Path A (clipboard one-liner), Path B (agent-walked OAuth), and the keploy/api-tests/ on-disk layout V1 creates. Safe to call without authentication; call this when the dev... |
| get_auth_status | Check whether the current MCP session has a valid-looking Keploy PAT attached. Returns { authenticated, auth_header_present, hint }. Useful as a first step for an agent to decide whether to call other tools or show setup instructions —... |
| get_setup_instructions | Return step-by-step instructions for connecting this MCP server to Cursor, Windsurf, VS Code, Claude Desktop, Claude Code, or Trae. Safe to call without authentication — use this when the user asks 'how do I set up Keploy MCP?' or when... |
| get_tool_schema | Fetch the exact schema(s) for tool(s) you ALREADY know by name — e.g. names a skill/playbook gave you (getTestReportFull, updateTestCase, listTestReports, getMock, getTestCase, getApp, listApps, ...). Returns ONLY the named tools: no... |
| invoke_tool | Run any Keploy tool by name. Most tools are hidden from the default list. Know the name from a skill? get its schema with get_tool_schema; don't know the name? discover it with search_tools. Then call invoke_tool with that name and an... |
| search_tools | DISCOVER tool names you do NOT already know, by keyword. Most Keploy tools are hidden from the default tool list to save context. If you ALREADY know the exact name (e.g. a skill named it), call get_tool_schema instead — it is exact and... |
Status badge
[](https://toolpin.dev/servers/io.github.keploy/mcp)
Maintain this server? Add the badge to your README — it links your users to this live status page.