Hoppscotch MCP Server

A Model Context Protocol (MCP) server that enables AI agents like Claude to interact with Hoppscotch: managing collections, environments, teams, and API workflows programmatically.

Features

• 53 MCP tools for comprehensive API workflow management
• Collection management: create, update, delete, import/export, duplicate, and move collections. The one search tool, search_team_requests, searches a team's requests by title, not collections
• Environment management: manage environment variables across deployment stages
• Team collaboration: full team workspace support including member management
• Request execution: execute HTTP requests with authentication and environment variable substitution
• Response validation: validate API responses against expected criteria (status, headers, body, response time)
• Code generation: generate code snippets in curl, JavaScript, Python, Go, and Rust
• Documentation generation: auto-generate API documentation in Markdown
• REST and GraphQL collections: personal collections and requests carry a REST/GraphQL type; team collections are untyped
• Cloud and self-hosted targeting: Cloud (hoppscotch.io) is supported. Self-hosted instances use <server URL>/backend by default. Set HOPPSCOTCH_API_URL for a different backend URL. See Cloud / self-hosted compatibility for the verification boundary
• Browser-based login: no token setup required for interactive use. Sign in through Hoppscotch's device-login page and the session is cached

Installation

Via npx (recommended, no install needed)

npx @hoppscotch/mcp-server

From npm

npm install -g @hoppscotch/mcp-server

This also installs the hoppscotch-mcp binary, which the client configs below can use in place of npx.

From source

This project uses pnpm (corepack enable picks up the pinned version):

git clone https://github.com/hoppscotch/hoppscotch-mcp-server.git
cd hoppscotch-mcp-server
pnpm install
pnpm run build

Released builds carry the Firebase Web API key needed for Cloud sign-in; a build from source does not. To use Cloud from a source build, provide HOPPSCOTCH_FIREBASE_API_KEY either at build time (it gets baked into the bundle) or at runtime in your MCP client's env block. The runtime value takes precedence, so no rebuild is needed. Without it, Cloud sign-in fails with a clear error. Self-hosted instances don't use Firebase and need nothing extra.

Quick Start

1. Configure your MCP client

Claude Code / Codex: register the server once at user scope. For a self-hosted instance, pass HOPPSCOTCH_SERVER_URL through the host's env flag (-e for Claude Code, --env for Codex). If the backend is not available at <server URL>/backend, also set HOPPSCOTCH_API_URL to the backend API base URL.

claude mcp add -s user hoppscotch -- npx -y @hoppscotch/mcp-server
codex mcp add hoppscotch -- npx -y @hoppscotch/mcp-server

Claude Desktop: edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

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

For a self-hosted instance:

{
  "mcpServers": {
    "hoppscotch": {
      "command": "npx",
      "args": ["-y", "@hoppscotch/mcp-server"],
      "env": {
        "HOPPSCOTCH_SERVER_URL": "https://your-hoppscotch.example.com"
      }
    }
  }
}

For a self-hosted instance with a separate backend URL:

{
  "mcpServers": {

... [View full README on GitHub](https://github.com/hoppscotch/hoppscotch-mcp-server#readme)