Install
npm i -g @hoppscotch/cliShowcase


Verified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Ci scripting — stories about ci scripting in this arenaCi scriptingevidence →
Stories about ci scripting in this arena
Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaborationevidence →
Working as a team — sharing, comments, roles, simultaneous editing
Collections workspaces — stories about collections workspaces in this arenaCollections workspacesevidence →
Stories about collections workspaces in this arena
Environments secrets — stories about environments secrets in this arenaEnvironments secretsevidence →
Stories about environments secrets in this arena
Gateway traffic — stories about gateway traffic in this arenaGateway trafficevidence →
Stories about gateway traffic in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Spec design — stories about spec design in this arenaSpec designevidence →
Stories about spec design in this arena
Testing mocking — stories about testing mocking in this arenaTesting mockingevidence →
Stories about testing mocking in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 5 free · 0 paid · 0 enterprise · 26 not stated in evidence
Follow the green: where the map greys out is where Hoppscotch stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Webhooks · Official SDKs · Scoped API keys · Machine-readable spec · Versioning policy
Subscribe to events via webhooks
—0/10
Build against official SDKs
—–
Issue scoped/least-privilege API credentials for an agent
—0/10
Connect an agent via an official MCP server
✓7/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
~3/10
Explore an interactive API reference with runnable examples
~5/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~5/10
unlocks → MCP client
Operate the product with natural-language commands
~6/10
Plug MCP servers into this product so it can use their tools
—0/10
Get AI-generated insights and suggestions from my data inside the product
~5/10
Set up automations that run autonomously in the background
~4/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Ci scripting — stories about ci scripting in this arenaCi scripting
Stories about ci scripting in this arena
Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration
Working as a team — sharing, comments, roles, simultaneous editing
Collections workspaces — stories about collections workspaces in this arenaCollections workspaces
Stories about collections workspaces in this arena
Environments secrets — stories about environments secrets in this arenaEnvironments secrets
Stories about environments secrets in this arena
Gateway traffic — stories about gateway traffic in this arenaGateway traffic
Stories about gateway traffic in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Spec design — stories about spec design in this arenaSpec design
Stories about spec design in this arena
Testing mocking — stories about testing mocking in this arenaTesting mocking
Stories about testing mocking in this arena
Sorted by importance (agentic first) (high → low) · 57/57 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 7/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 5/10 | Cclaimed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Tprobed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Tprobed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 3/10 | Tprobed | |
Organize API requests into collections and folders and rerun them anytime C Collections | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 3 | full | 9/10 | Xcommunity | |
Run an entire collection as an automated test suite with a pass/fail report C Testing | developer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 3 | full | 8/10 | Tprobed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | fullfree | 8/10 | Xcommunity | |
Run my API test collections in CI with a CLI and fail the build on regressions C Ci | developer | Ci scripting — stories about ci scripting in this arenaCi scripting | 3 | partial | 7/10 | Tprobed | |
Import an OpenAPI spec to generate requests and collections C Spec import export | developer | Spec design — stories about spec design in this arenaSpec design | 3 | partial | 6/10 | Cclaimed | |
Share collections with my team in a synced shared workspace C Team workspaces | developer | Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration | 3 | partial | 6/10 | Xcommunity | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partialfree | 5/10 | Cclaimed | |
Switch requests between dev, staging, and prod using environment variable sets C Environments | developer | Environments secrets — stories about environments secrets in this arenaEnvironments secrets | 3 | partial | 5/10 | Cclaimed | |
Write test assertions against response status, body, and headers C Testing | developer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 3 | partial | 5/10 | Cclaimed | |
Store collections as plain text files in my repo and version them with git C Collections | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 3 | none | 0/10 | ||
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | none | untested | none yet | |
Enforce authentication (API keys, OAuth2, JWT, mTLS) on upstream APIs via gateway plugins or policies C Traffic management | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 3 | n/a | untested | none yet | |
Enforce rate limits on API traffic per consumer or route C Traffic management | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 3 | n/a | untested | none yet | |
Lint API specs against configurable style and governance rules C Governance | platform-engineer | Spec design — stories about spec design in this arenaSpec design | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Spin up a mock server from saved examples or a spec so consumers can build before the API exists C Mocking | developer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 3 | n/a | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | fullfree | 8/10 | Xcommunity | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partialfree | 6/10 | Cclaimed | |
Keep credentials out of shared files with masked secrets or an external vault integration C Secrets | platform-engineer | Environments secrets — stories about environments secrets in this arenaEnvironments secrets | 2 | partial | 6/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 6/10 | Cclaimed | |
Script pre-request and post-response logic to chain requests and massage data C Scripting | developer | Ci scripting — stories about ci scripting in this arenaCi scripting | 2 | partial | 6/10 | Cclaimed | |
Send GraphQL, gRPC, WebSocket, and SSE requests, not just REST C Protocols | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 2 | partial | 6/10 | Cclaimed | |
Work fully offline in a local workspace without a cloud account G Offline | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 2 | partial | 6/10 | Xcommunity | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 5/10 | Tprobed | |
Have AI generate test cases or assertions for an endpoint from its spec or responses C Ai assist | ai-native user | Testing mocking — stories about testing mocking in this arenaTesting mocking | 2 | partial | 5/10 | Cclaimed | |
Import and export collections in portable formats to move between tools C Collections | developer | Collections workspaces — stories about collections workspaces in this arenaCollections workspaces | 2 | partial | 5/10 | Xcommunity | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partialfree | 4/10 | Cclaimed | |
Control who can view or edit APIs and collections with roles and permissions G Access control | platform-engineer | Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration | 2 | partial | 4/10 | Cclaimed | |
Publish an internal catalog or portal where teams discover and consume our APIs C Api catalog | platform-engineer | Collaboration — working as a team — sharing, comments, roles, simultaneous editingCollaboration | 2 | partial | 4/10 | Cclaimed | |
Schedule collection runs as monitors that alert me when an API breaks C Monitors | developer | Ci scripting — stories about ci scripting in this arenaCi scripting | 2 | partial | 4/10 | Cclaimed | |
Design an API spec-first and export it as OpenAPI C Spec import export | developer | Spec design — stories about spec design in this arenaSpec design | 2 | none | 0/10 | ||
Generate and publish API documentation from my collections or specs C Docs generation | developer | Spec design — stories about spec design in this arenaSpec design | 2 | none | 0/10 | ||
Manage API infrastructure as declarative config and sync it from CI (GitOps/APIOps) C Gateway ops | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 2 | none | 0/10 | ||
Monitor API traffic with metrics, logging, and tracing integrations C Monitoring | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 2 | none | 0/10 | ||
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Proxy and govern LLM/MCP traffic (token limits, prompt guards, provider routing) through the platform C Ai gateway | ai-native user | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 2 | n/a | untested | none yet | |
Route, load-balance, and transform requests between consumers and upstream services C Traffic management | platform-engineer | Gateway traffic — stories about gateway traffic in this arenaGateway traffic | 2 | n/a | untested | none yet | |
Validate live responses against the API contract to catch drift C Contract testing | platform-engineer | Testing mocking — stories about testing mocking in this arenaTesting mocking | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | none | 0/10 |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 43 stories with headroom
What would move Hoppscotch’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
Evidence only shows Hoppscotch exposing itself AS an MCP server (agents can connect to Hoppscotch to read/change collections, requests, etc.), which is the reverse of the story — Hoppscotch acting as an MCP client that consumes other servers' tools.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
Hoppscotch offers pre-request/test scripts (gh-5) and a CLI for scheduled/automated test runs (docs-8, docs-21), but there is no evidence of a rules engine or event-triggered automation (e.g., 'when X happens, do Y') as described in the story.
Collections workspaces — stories about collections workspaces in this arenaStore collections as plain text files in my repo and version them with git
nonemoves PA Scoreimpact 30
There is no evidence Hoppscotch stores collections as plain-text files suitable for git version control; instead, community evidence explicitly shows this is a requested-but-unimplemented feature (an open GitHub issue asking Hoppscotch to make storage git-friendly) and a comparison noting Bruno supports directory-based storage while Hoppscotch does not let you point a workspace to a specific directory.
Spec design — stories about spec design in this arenaLint API specs against configurable style and governance rules
nonemoves PA Scoreimpact 30
Hoppscotch is an API client/testing tool with request building, collections, CLI test runner, and MCP server, but there is no evidence of spec linting against configurable style/governance rules (e.g., no Spectral-like ruleset engine or OpenAPI governance checks) in any doc, changelog, or CLI feature listed.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
No evidence in the pack addresses AI-training data usage, opt-out settings, or a privacy policy statement about model training; self-hosting for data ownership is documented but does not speak to whether cloud/AI features use data for training.
Agenticness — how well agents can access and operate the productIssue scoped/least-privilege API credentials for an agent
nonemoves agent-readyimpact 30
Hoppscotch's MCP server docs describe granting an agent full read/write access to all collections, requests, environments, and teams, with no mention of scoped, least-privileged, or permission-limited credentials for agents.
Agenticness — how well agents can access and operate the productBuild against official SDKs
nonemoves agent-readyimpact 30
Evidence shows Hoppscotch offers a CLI, an MCP server, and AI-assisted scripting features, but there is no mention of official client SDKs (e.g., language libraries for programmatically building or extending Hoppscotch) anywhere in the docs or GitHub feature list.
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
Hoppscotch is an API client/testing tool; nothing in the evidence shows any webhook subscription or event-notification mechanism for AI agents—the closest agentic features (MCP server, CLI) let an agent send requests and manage collections but do not provide a way to subscribe to incoming events.
Showing the top 8 of 43 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map6 surfaces · 34 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Documentation docs30 stories
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Use an official CLI
- Drive the product through a documented public API
- Get AI-generated insights and suggestions from my data inside the product
- Set up automations that run autonomously in the background
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Explore an interactive API reference with runnable examples
- Test against a sandbox environment without touching production data
- Perform bulk operations across many items at once
- Run my API test collections in CI with a CLI and fail the build on regressions
- Schedule collection runs as monitors that alert me when an API breaks
- Script pre-request and post-response logic to chain requests and massage data
- Control who can view or edit APIs and collections with roles and permissions
- Publish an internal catalog or portal where teams discover and consume our APIs
- Share collections with my team in a synced shared workspace
- Organize API requests into collections and folders and rerun them anytime
- Work fully offline in a local workspace without a cloud account
- Keep credentials out of shared files with masked secrets or an external vault integration
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Read the product's source under an open license
- Self-host the core product
- Choose where my data is stored (region/residency)
- Control data retention and deletion
- Have AI generate test cases or assertions for an endpoint from its spec or responses
- Run an entire collection as an automated test suite with a pass/fail report
- Write test assertions against response status, body, and headers
GitHub README11 stories
- Script pre-request and post-response logic to chain requests and massage data
- Control who can view or edit APIs and collections with roles and permissions
- Publish an internal catalog or portal where teams discover and consume our APIs
- Share collections with my team in a synced shared workspace
- Import and export collections in portable formats to move between tools
- Organize API requests into collections and folders and rerun them anytime
- Send GraphQL, gRPC, WebSocket, and SSE requests, not just REST
- Export all of my data in open formats and leave
- Read the product's source under an open license
- Import an OpenAPI spec to generate requests and collections
- Write test assertions against response status, body, and headers
Changelog docs11 stories
- Explore an interactive API reference with runnable examples
- Test against a sandbox environment without touching production data
- Control who can view or edit APIs and collections with roles and permissions
- Publish an internal catalog or portal where teams discover and consume our APIs
- Share collections with my team in a synced shared workspace
- Import and export collections in portable formats to move between tools
- Organize API requests into collections and folders and rerun them anytime
- Switch requests between dev, staging, and prod using environment variable sets
- Keep credentials out of shared files with masked secrets or an external vault integration
- Self-host the core product
- Import an OpenAPI spec to generate requests and collections
Hacker News6 stories
- Share collections with my team in a synced shared workspace
- Import and export collections in portable formats to move between tools
- Organize API requests into collections and folders and rerun them anytime
- Work fully offline in a local workspace without a cloud account
- Read the product's source under an open license
- Self-host the core product
OpenAPI spec2 stories
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
8 of 12 testable claims verified · 0 contradicted → integrity 67/100
18 distinct capability claims found in Hoppscotch’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
8
Verified
4
Unverified
0
Contradicted
22
Undersold
Verified (10)
“Collection-level headers/auth are inherited by all requests in that collection”
Organize API requests into collections and folders and rerun them anytimefullproof ↗
“Self-host admin dashboard lets you manage server configuration directly”
“Official CLI can run API tests and manage collections from the terminal”
“Official CLI can run API tests and manage collections from the terminal”
Run my API test collections in CI with a CLI and fail the build on regressionspartialproof ↗
“CLI test command can generate a JUnit report for collection runs”
Run my API test collections in CI with a CLI and fail the build on regressionspartialproof ↗
“Exposes collections, requests, environments and teams so an external agent can read and modify them”
“Community Edition is free, open-source, and MIT licensed”
“Enterprise edition offers on-prem deployment (plus SAML SSO and audit logs)”
“Can import requests directly from a cURL command”
Import and export collections in portable formats to move between toolspartialproof ↗
“Enables teams to collaborate on designing, developing and testing APIs together”
Share collections with my team in a synced shared workspacepartialproof ↗
Unverified (4)
“Environments support secret (masked) variables to keep credentials hidden”
Keep credentials out of shared files with masked secrets or an external vault integrationpartialproof ↗
“CLI can automate monitoring of collections”
Schedule collection runs as monitors that alert me when an API breakspartialproof ↗
“Supports full-duplex WebSocket communication over a single TCP connection”
Send GraphQL, gRPC, WebSocket, and SSE requests, not just RESTpartialproof ↗
“Supports pre-request and post-response scripts attached to a request”
Script pre-request and post-response logic to chain requests and massage datapartialproof ↗
Undersold (22)
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationfullproof ↗
Drive the product through a documented public APIfullproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
Operate the product with natural-language commandspartialproof ↗
Explore an interactive API reference with runnable examplespartialproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Control who can view or edit APIs and collections with roles and permissionspartialproof ↗
Publish an internal catalog or portal where teams discover and consume our APIspartialproof ↗
Work fully offline in a local workspace without a cloud accountpartialproof ↗
Switch requests between dev, staging, and prod using environment variable setspartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
Choose where my data is stored (region/residency)partialproof ↗
Import an OpenAPI spec to generate requests and collectionspartialproof ↗
Have AI generate test cases or assertions for an endpoint from its spec or responsespartialproof ↗
Run an entire collection as an automated test suite with a pass/fail reportfullproof ↗
Write test assertions against response status, body, and headerspartialproof ↗
Claims outside our story set (5)
Real capability claims found in Hoppscotch’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Supports request-scoped variables you can reference in a request”
source ↗“Revamped OAuth 2.0 support with multiple grant types”
source ↗“Supports OIDC-based single sign-on”
source ↗“Can embed a mini version of Hoppscotch in an HTML page for audience interaction”
source ↗“Can generate and copy request code snippets for 10+ languages/frameworks”
source ↗
Business model
Open-source core with a free self-hosted community edition and free cloud tier; paid Cloud per-user plans and custom Enterprise add team workspaces, SSO, and support.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% (30d, checked every 6h since Sep 8 '26)
