1. Conduid
  2. AI
  3. Workbench
MCP server · AI

Workbench

A mock MCP server repository to build and test mcp servers

Unclaimed last commit 9 months ago ai
34Low

Scored 14 days ago · breakdown

About Workbench

Workbench is an MCP server published by conductor-oss in the AI category: a mock MCP server repository to build and test mcp servers.

The repository has 2 stars and 0 forks, with the last commit 9 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/conductor-oss/mcp-workbench

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Workbench

Powered by Claude · Grounded in docs

I know everything about Workbench. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README

MCP Workbench

A visual debugger and test client for Model Context Protocol (MCP) servers.

MCP Workbench lets you connect to an MCP server over Streamable HTTP, inspect protocol traffic, explore resources, and execute tools with zero guesswork. It’s built for developers who want fast feedback and full visibility into what their server is actually doing.

What This Tool Is For

  • Debugging MCP servers during development
  • Verifying protocol compliance (handshake, capabilities, message flow)
  • Manually testing tools, prompts, and resources
  • Inspecting raw JSON-RPC traffic in real time

If you’re building or maintaining an MCP server, this is your control panel.

Features

  • Streamable HTTP Client**

  • Session handling via MCP-Session-Id

  • Auto-generated input forms from JSON Schema

  • Execute tools and inspect raw responses

  • Browse and inspect server-exposed resources

  • List and test available prompts

  • Authentication Support

    • OAuth 2.0 (Authorization Code flow with popup)
    • API key support via custom headers
  • Multi-Server Configs

    • Save, switch, and reuse multiple MCP server connections

Getting Started

Requirements

  • Node.js 18+
  • npm or yarn

Setup

git clone https://github.com/conductoross/mcp-workbench.git
cd mcp-workbench
npm install
npm run dev

Open:

http://localhost:5173

Testing Local Stdio Servers (Node.js/Python)

To connect the Workbench to a local MCP server running over Stdio (e.g. node server.js), use the included Bridge script:

  1. Run the bridge with your command:

    node scripts/stdio-bridge.js "node my-server.js"
    # or for Python
    node scripts/stdio-bridge.js "uv run main.py"
    
  2. Copy the URL printed (e.g., http://localhost:3001/mcp)

  3. In Workbench, select Streamable HTTP and paste the URL.


CORS Handling

Your MCP server must allow cross-origin requests from the Workbench origin. If CORS is misconfigured, requests will fail silently in the browser.

Safari requires an additional CORS header for localhost:

Access-Control-Allow-Private-Network: true

Add this to your server's CORS middleware. Chrome and Firefox are more permissive.


Contributing

Pull requests are welcome. Keep changes focused, readable, and aligned with MCP specifications.


License

MIT License


README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Workbench

How do I install Workbench?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Workbench safe to use with an AI agent?

Its trust score is 34 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Workbench still maintained?

The last commit was 9 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.