Keploy MCP server

Which servers in the official MCP registry are Keploy's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-08

← Back to Keploy

Whose server it is

Registry nameio.github.keploy/mcppublished by keploy on GitHub

Published under the GitHub organisation keploy, the same one keploy.io links from its homepage. The registry ties that namespace to a GitHub sign-in.

When we asked itchecked 2026-10-08

Stateanswerschecked 2026-10-08
Tools7
Server calls itselfkeploy-atg
Server version1.0.0
Protocol version2025-06-18

On 2026-10-08 the server answered initialize and tools/list without a sign-in. First answer in 94 ms.

Tools it offers7 tools · read 2026-10-08

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 a…
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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "keploy": {
      "type": "http",
      "url": "https://api.keploy.io/client/v1/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.