apikumo vs Hoppscotch
Two browser-first API clients. Hoppscotch is open source and self-hostable; apikumo publishes what you test.
Hoppscotch is an MIT-licensed, open-source API client with web, desktop, and CLI apps, a free self-hosted edition, and support for realtime protocols like WebSocket, SSE, Socket.IO, and MQTT. apikumo focuses on the path from a tested collection to a published API: hosted docs with an AI assistant, schema-based mocks, test-suite reports, and an MCP endpoint generated from every published collection. If self-hosting or realtime testing matters most, Hoppscotch is the stronger pick.
Docs publishing is a core feature
Publish a collection to its own subdomain with search, try-it, a changelog, and AI chat. Hoppscotch introduced published docs as an experimental public beta in v2025.11.0.
An MCP endpoint per published collection
A hosted, read-only MCP URL for your API. Hoppscotch’s official MCP server (2026.8.0) is an npm package for working with your Hoppscotch workspace.
Test suites with reports
Chain requests into suites with assertions, run history, and flaky-test detection, and export PDF/CSV reports on Pro and Team.
Feature comparison
| Feature | apikumo | Hoppscotch |
|---|---|---|
| Browser API client | ||
| Open source / self-host | MIT · free Community Edition | |
| Desktop app | ||
| Collection runner / test suites | ||
| Mock servers | Schema-based | Since v2025.10.0 |
| Published docs | Own subdomain | Public beta2 |
| MCP | Hosted server per published collection | npm MCP server for your workspace |
| Live protocols | HTTP (incl. GraphQL bodies) | REST, GraphQL, WebSocket, SSE, Socket.IO, MQTT |
| Pricing | Free: up to 3 members · Team $8/seat/mo | Cloud Free $0 · Organization $6–8/user/mo4 |
- 1Hoppscotch license and editions: github.com/hoppscotch/hoppscotch (MIT); Community Edition is free and open source, Enterprise is open-core (docs.hoppscotch.io/documentation/self-host/getting-started).
- 2Hoppscotch v2025.11.0 release notes describe published docs as “an experimental feature currently in public beta” (hoppscotch.com/blog/hoppscotch-v2025-11-0).
- 3Hoppscotch MCP server: github.com/hoppscotch/hoppscotch-mcp-server, introduced in release 2026.8.0.
- 4Hoppscotch pricing: Organization $8/user/month billed monthly or $6 billed annually; self-hosted Enterprise $19/user/month (hoppscotch.com/pricing).
Comparison verified Sep 2026 · competitor features and pricing change
Which one should you pick?
Pick apikumo if…
- You want published API docs with an AI assistant for readers as a core feature of your API client.
- You want AI agents to reach your API through a hosted MCP URL with nothing to install.
- You report on API tests — run history, flaky tests, and exported PDF/CSV reports.
Pick Hoppscotch if…
- You must self-host, or you want open-source software under the MIT license.
- You test realtime APIs over WebSocket, SSE, Socket.IO, or MQTT.
- You want a desktop app, or the lowest per-user price for a large team.
Moving from Hoppscotch
- 1apikumo has no Hoppscotch importer, so start from your API’s OpenAPI spec (3.x or Swagger 2.0, JSON or YAML), a HAR file, or cURL commands.
- 2Import into an apikumo workspace and recreate your environments.
- 3Rebuild the checks you rely on as a test suite, and wire it into CI with the apikumo CLI.
- 4Publish the collection for docs, schema-based mocks, and the MCP endpoint.
Where apikumo falls short
- The platform is not open source and cannot be self-hosted.
- No direct importer for Hoppscotch collections.
- WebSocket support is documentation only today: you can describe a socket’s handshake URL, params, headers, and auth, but not open a live connection and exchange messages.
- No gRPC, MQTT, or Socket.IO clients.
- apikumo runs in the browser and needs a sign-in; there is no offline or local-only mode, and no desktop app yet.
Learn more
From tested collection to published API
Import your OpenAPI spec and publish docs, mocks, and an MCP endpoint in one step.
No card required · Sign in with Google, GitHub, or Discord