Keploy

io.github.keployPublished by GitHub account keployv1.0.0Updated Nov 2, 2026

End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.

VerifiedStreamable HTTPWeb executableDeveloper Tools Security & Monitoring

Server details

Identifier: io.github.keploy/mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account keploy for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.keploy%2Fmcp.svg)](https://sourceweft.com/mcp/io.github.keploy%2Fmcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Keploy's remote MCP endpoint for generating and running end-to-end API tests from OpenAPI specs, curl, Postman or recorded traffic.

What you can do: Generate API tests from OpenAPI schemas, curl commands, Postman collections or real user traffic
Run recorded API and integration flows as replayable tests with data mocks
Expand API coverage using AI to probe boundary values, missing fields, wrong types and out-of-order sequences
Record and replay database, queue and external API interactions so tests run without re-provisioning infrastructure
Report combined API, integration, unit and e2e coverage
When to use it: Useful when you want an assistant to help build or extend automated API and integration test suites for an existing service, especially when you already keep specs or traffic recordings and want coverage of schema and business flows without writing test code.
Requirements: A remote MCP endpoint reached over streamable HTTP; OAuth is required. You need a Keploy API key sent in the Authorization header as a Bearer token, generated from the Keploy account settings. Network access to the Keploy service is required.

Before you install

The Authorization header carries a Keploy API key; treat it as a secret and keep it out of shared logs. The key is shown only once when generated. Test generation and coverage work happens on Keploy's hosted service, so API schemas and traffic-derived data are sent to that third party.

Installation

In SourceWeft

Open Keploy in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.keploy%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

README

[Keploy Logo]

[keploy%2Fkeploy | Trendshift]

⚡️ API tests faster than unit tests, from user traffic ⚡️

🌟 The must-have tool for developers in the AI-Gen era for 90% test coverage 🌟

[Slack] [LinkedIn] [YouTube] [X]

[Keploy CNCF Landscape] [GitHub Stars] [Help us reach 20k stars!]

Keploy is a developer‑centric API and integration testing tool that auto‑generates tests and data‑mocks faster than unit tests.

It records API calls, database queries, and streaming events — then replays them as tests. Under the hood, Keploy uses eBPF to capture traffic at the network layer, but for you it’s completely code‑less and language‑agnostic.

[Convert API calls to API tests test cases and Data Mocks using AI]

🐰 Fun fact: Keploy uses itself for testing! Check out our swanky coverage badge: [Coverage Status]

Key Highlights

🎯 No code changes

Just run your app with keploy record. Real API + integration flows are automatically captured as tests and mocks. (Keploy uses eBPF under the hood to capture traffic, so you don’t need to add any SDKs or modify code.)

📹 Record and Replay complex Flows

Keploy can record and replay complex, distributed API flows as mocks and stubs. It's like having a very light-weight time machine for your tests—saving you tons of time!

👉 Read the docs on record-replay

[Convert API calls to test cases]

🐇 Complete Infra‑Virtualization (beyond HTTP mocks)

Unlike tools that only mock HTTP endpoints, Keploy records databases (Postgres, MySQL, MongoDB), streaming/queues (Kafka, RabbitMQ), external APIs, and more.

It replays them deterministically so you can run tests without re‑provisioning infra.

👉 Read the docs on infra virtualisation

[Convert API calls to test cases]

🧪 Combined Test Coverage

If you’re a developer, you probably care about statement and branch coverage — Keploy calculates that for you.

If you’re a QA, you focus more on API schema and business use‑case coverage — Keploy calculates that too. This way coverage isn’t subjective anymore.

👉 Read the docs on coverage

[ai test gen for api statement schema and branch coverage]

🤖 Expand API Coverage using AI

Keploy uses existing recordings, Swagger/OpenAPI Schema to find: boundary values, missing/extra fields, wrong types, out‑of‑order sequences, retries/timeouts.

This helps expand API Schema, Statement, and Branch Coverage.

👉 Read the docs on coverage

[ai test gen for api statement schema and branch coverage]

Other Capabilities

🌐 CI/CD Integration: Run tests with mocks anywhere you like—locally on the CLI, in your CI pipeline (Jenkins, Github Actions..) , or even across a Kubernetes cluster. Read more
🎭 Multi-Purpose Mocks: You can also use Keploy-generated Mocks, as server Tests!
📊 Reporting: Unified reports for API, integration, unit, and e2e coverage with insights directly in your CI or PRs.
🖥️ Console: A developer-friendly console to view, manage, and debug recorded tests and mocks.
⏱️ Time Freezing: Deterministically replay tests by freezing system time during execution. Read more
📚 Mock Registry: Centralized registry to manage, reuse, and version mocks across teams and environments. Read more

Quick Start

1. Install Keploy Agent

bash

source /dev/stdin <<<"$(curl -fsSL https://keploy.io/install.sh || echo 'echo Keploy installer download failed >&2; return 1')"

source /dev/stdin <<<"$(curl -fsSL https://keploy.io/install.sh || echo 'echo Keploy installer download failed >&2; return 1')"

2. Record Test Cases

Start your app under Keploy to convert real API calls into tests and mocks.

Example for Python:

3. Run Tests

Run tests offline without external dependencies.

Resources

- 📘 Installation

- 🏁 QuickStarts

Languages & Frameworks (Any stack)

Because Keploy intercepts at the network layer (eBPF), it works with any language, framework, or runtime—no SDK required.

Note: Some of the dependencies are not open-source by nature because their protocols and parsings are not open-sourced. It's not supported in Keploy enterprise.

[Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image] [Image]

Questions?

Book a Live Demo / Enterprise Support

Want a guided walkthrough, dedicated support, or help planning enterprise rollout?

[Image] [Image]

Prefer a calendar invite? Mention your availability in the email—we’ll send a calendar invite right away.

Documentation & Community

📘 Documentation — Explore the full docs
💬 Slack Community — Join the conversation
📜 Contribution Guidelines
❤️ Code of Conduct
📢 Blog — Read articles and updates

Contribute & Collaborate

Whether you're new or experienced, your input matters. Help us improve Keploy by contributing code, reporting issues, or sharing feedback.

Together, let's build better testing tools for modern applications.

Source: README.md at commit 558559c

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts