OfficialVerified

Hoppscotch MCP Server

Manage API workflows, collections, and team environments through 53 distinct MCP tools.

Data last scanned today · Reviewed today

36 9 dangerous tools53 tools★ 4TypeScriptMIT

Overview

The Hoppscotch MCP Server provides a bridge for AI agents to interface directly with Hoppscotch API development workflows. It supports a comprehensive range of administrative tasks including collection management, environment variable configuration, and team workspace coordination. By leveraging 53 distinct tools, agents can automate complex tasks like API documentation generation, code snippet creation, and request validation. Designed for both cloud and self-hosted deployments, the server handles authentication via a browser-based device-login process. It is built with TypeScript and remains actively maintained, with recent commits ensuring compatibility with modern MCP standards.

Our verdict

With a security score of 38/100, this server is currently classified as high-risk. This rating reflects the fact that it is a community-maintained project rather than an official vendor release, and critical aspects such as read-only mode behavior and authentication handling have not yet been editorially reviewed. Given the high-risk designation and the scope of access required for API management, it should be restricted to trusted, private environments until more robust security audits are conducted.

Supports 53 distinct tools for extensive API workflow management
Active development with commits within the last day
Uses a small set of 7 direct dependencies
Licensed under the permissive MIT open-source license

High-risk status due to lack of editorial security review
Authentication and read-only mode safety have not been assessed
Maintained by the community rather than the official Hoppscotch organization

Setup

Claude Desktop

{
  "mcpServers": {
    "hoppscotch-mcp-server": {
      "args": [
        "-y",
        "@hoppscotch/mcp-server"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

Tool	Description	Risk
list_teams	List all teams you are a member of, with each team's members	low
get_team_info	Get team details including members and roles	low
create_team	Create a new team	medium
rename_team	Rename a team	medium
delete_team	Delete a team (irreversible)	high
leave_team	Leave a team	medium
invite_team_member	Invite a member to a team by email	medium
revoke_team_invitation	Revoke a pending team invitation	medium
remove_team_member	Remove a member from a team	medium
update_team_member_role	Update a team member's role (OWNER/EDITOR/VIEWER)	medium

Compatibility

Client	Local	Docker	Remote	Read-only
ChatGPT
Claude Desktop
Cursor
VS Code
Windsurf

Frequently asked questions

›How do I authenticate with this server?

On your first tool call, the server automatically opens a browser-based device-login page. Once you sign in, the session is cached to skip the browser step for subsequent calls.

›Does this server support self-hosted Hoppscotch instances?

Yes, you can target a self-hosted instance by setting the HOPPSCOTCH_SERVER_URL environment variable to your instance's URL. The backend must be accessible at the <server URL>/backend path.

›Can I use this server in a headless or CI environment?

Yes, you can bypass the browser login flow by providing a Hoppscotch JWT via the HOPPSCOTCH_ACCESS_TOKEN environment variable. Note that standard Personal Access Tokens (PATs) are not supported for this purpose.

›How can I customize the number of tools available?

You can set the HOPPSCOTCH_TOOL_PROFILE environment variable to select between different tool counts, ranging from 22 (minimal) to 53 (full). If no value is provided, it defaults to the 'core' profile with 39 tools.

›Do I need to rebuild the project to add a Firebase API key for Cloud authentication?

No, you can provide the HOPPSCOTCH_FIREBASE_API_KEY at runtime in your MCP client's environment block. Runtime values take precedence over any baked-in build-time keys.

›Are sessions against the self-hosted Community Edition refreshed automatically?

No, Community Edition sessions are not automatically refreshed by this server because it relies on cookie-based authentication. You will need to perform a new browser sign-in when your token expires.