Get the FREE Ultimate OpenClaw Setup Guide →

turbomcpstudio

A native desktop application for developing, testing, and debugging Model Context Protocol servers.

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add epistates-turbomcpstudio

How to use

TurboMCP Studio is a native desktop application designed to help you develop, test, and debug MCP (Model Context Protocol) servers. It provides tools for managing MCP server profiles, exploring available MCP tools, inspecting protocol messages in real time, and designing prompts and elicitation flows. While TurboMCP Studio itself is a client application, it integrates with your MCP servers via the standard MCP workflows exposed by the tools inside the Studio, including the Protocol Inspector, Tool Explorer, and Prompt Designer. Use the Studio to connect to your running MCP servers, configure server profiles, and leverage the built-in testing pipelines to validate messages, sampling, and elicitation sequences in a controlled UI environment. The tool emphasizes type safety, enterprise-grade state management, and a modern UI with support for multiple transport layers (STDIO, HTTP, WebSocket, TCP, and Unix sockets).

How to install

Prerequisites:

  • Rust toolchain (1.70 or later) and cargo
  • Node.js 20.x or later
  • pnpm 9.x or later

Install from source:

  1. Clone the repository: git clone https://github.com/Epistates/turbomcpstudio.git cd turbomcpstudio

  2. Install frontend dependencies (pnpm is required): pnpm install

  3. Build and run in development mode (hot-reload): pnpm run tauri dev

  4. Build for production (desktop app): pnpm run tauri build

Notes:

  • TurboMCP Studio is published to crates.io for the Rust backend during the build process. No additional runtime server setup is required to use the UI with your MCP servers; you will connect to your servers via the Studio’s tooling once the app is running.

Additional notes

Tips and considerations:

  • Prebuilt binaries are listed as coming soon in the README; the primary workflow is to build from source or use the published crates as part of the local build.
  • Ensure you have the required platform tools for your target OS when building (Xcode Command Line Tools on macOS, WiX NSIS for Windows, and relevant dependencies on Linux).
  • The Studio supports multiple transports; ensure your MCP server endpoints are reachable from the machine running TurboMCP Studio.
  • For production builds, consider platform-specific build notes (Gatekeeper on macOS, MSI/NSIS packaging on Windows, AppImage/DEB/RPM on Linux).
  • Regularly update Node.js and Rust toolchains to keep compatibility with the latest Studio features and tooling.

Related MCP Servers

Sponsor this space

Reach thousands of developers