MCP.so
Sign In

MCPStudio: The Postman for Model Context Protocol

@lonexreb

About MCPStudio: The Postman for Model Context Protocol

Postman for MCP servers

Basic information

Category

Other

Runtime

node

Transports

stdio

Publisher

lonexreb

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "MCPstudio": {
      "command": "python",
      "args": [
        "-m",
        "venv",
        "venv",
        "&&",
        "source",
        "venv/bin/activate",
        "#",
        "Windows:",
        "venvScriptsactivate"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCPStudio?

MCPStudio is a web platform for creating, testing, managing, and discovering Model Context Protocol (MCP) servers. Like Postman for APIs, it provides a visual interface that abstracts away protocol complexity, allowing users to connect to MCP servers, discover tools, execute them with parameters, and inspect results—all from the browser.

How to use MCPStudio?

Clone the repository, then install and run the backend (Python 3.10+ with UV) and frontend (Node.js 16+ with npm). Open http://localhost:8080, sign up or log in, and start managing MCP servers. The guided onboarding tour helps you get started.

Key features of MCPStudio

  • Server creation, configuration, and connection with status tracking
  • Auto-discovery and execution of MCP tools via dynamic forms
  • Visual pipeline builder with drag-and-drop DAG canvas
  • Tool Execution Arena for side-by-side comparison with JSON diff
  • MCP server discovery from npm and GitHub registries
  • Supabase authentication with email/password and OAuth2 for Google Drive

Use cases of MCPStudio

  • Developers prototyping and testing MCP server integrations
  • Data scientists chaining MCP tools into reusable pipelines
  • Teams collaborating on MCP tool execution and configuration
  • Discovering and evaluating MCP-compatible servers from the community

FAQ from MCPStudio

What are the runtime requirements for MCPStudio?

Python 3.10+, Node.js 16+, and optionally MongoDB (falls back to in-memory mock). The UV package manager is recommended for the backend.

How does authentication work?

MCPStudio uses Supabase email/password signup and login with JWT tokens. It also supports OAuth2 flows for service integrations like Google Drive.

Where is execution history and user data stored?

Execution history, pipeline definitions, and prompt templates are stored in IndexedDB (via Dexie) on the client side. The backend uses MongoDB (or in-memory mock) for persistent server-side logs. Zustand state is persisted to localStorage.

What transport does MCPStudio use for real-time updates?

WebSocket streams are used for tool execution and server status changes (endpoint: /ws/servers/{id}/tools/{id}/execution).

Can I export and import server configurations?

Yes, MCPStudio supports exporting server configs as JSON or YAML (with credentials redacted) and importing via file upload, drag-and-drop, or paste.

Comments

More Other MCP servers