feat: Add Model Context Protocol (MCP) client support
Author: rahulbswCreated Mar 9, 2026Updated Sep 16, 2026
Feature Description
Add Model Context Protocol (MCP) client support to Hoppscotch, similar to Postman's implementation. This would enable users to connect to MCP servers, discover capabilities (tools, prompts, resources), and invoke methods.
Use Case
MCP (Model Context Protocol) is Anthropic's protocol for enabling AI assistants to interact with external tools and data sources. Adding MCP support to Hoppscotch would allow developers to:
- Test and debug MCP server implementations
- Explore MCP server capabilities interactively
- Invoke tools, prompts, and resources with custom arguments
- Save MCP requests in collections for reuse
- Track MCP invocation history
Proposed Implementation
Transport Support:
- HTTP transport with JSON-RPC 2.0 over Server-Sent Events
- STDIO transport (requires Hoppscotch Agent or Desktop App)
Authentication:
- None (open servers)
- Basic Auth
- Bearer Token
- API Key
Core Features:
- Automatic capability discovery
- Tool/prompt/resource invocation with JSON argument editor
- Real-time event logging
- Connection status monitoring
- Collections support for saving MCP requests
- History tracking for method invocations
- Search/filter across capabilities
UI Integration:
- New tab in /realtime section alongside WebSocket, SSE, Socket.io, MQTT
- Configuration panel for transport and auth settings
- Tabbed interface for Tools, Prompts, Resources, Logs, Response
- Modal dialogs for collections and history management
Reference
Additional Context
I've already implemented this feature and created PR #5965. Opening this issue for tracking and discussion per the contribution guidelines.
Source: hoppscotch/hoppscotch