hoppscotch/hoppscotch-mcp-server

本页由 AI 翻译，技术细节请以原文为准。查看原文

14 stars 5 forks 质量 84 趋势 34MIT

The Hoppscotch MCP Server implements the Model Context Protocol (MCP) to connect AI agents and coding assistants including Claude Code, Cursor, VS Code Copilot, GitHub Copilot CLI, and Gemini CLI...

概览

A Model Context Protocol (MCP) server that enables AI agents like Claude to interact with Hoppscotch: managing collections, environments, teams, and API workflows programmatically. - for comprehensive API workflow management - : create, update, delete, import/export, duplicate, and move collections. The one search tool, search_team_requests, searches a team's by title, not collections - : manage environment variables across deployment stages - : full team workspace support including member management - : execute HTTP requests with authentication and environment variable substitution - : validate API responses against expected criteria (status, headers, body, response time) - : generate code snippets in curl, JavaScript, Python, Go, and Rust - : auto-generate API documentation in Markdown - : personal collections and requests carry a REST/GraphQL type; team collections are untyped - : Cloud (hoppscotch.io) is supported. Self-hosted instances use /backend by default.

README

以下为原文 README 节选，完整内容请查看原文。

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 /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

在 GitHub 查看完整 README

安装

npx -y @hoppscotch/mcp-server

新手？先看 mcpskill.org 教程 →

配置

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