Is There a Hosted MCP Inspector Accessible From Any Browser?

Yes. Manufact provides a hosted MCP Inspector you can open from a browser, so you can inspect and debug MCP servers without installing a local inspector first. The fastest path is to open the hosted Inspector, connect it to an MCP server URL, verify tools, resources, prompts, and JSON-RPC traffic, then move the same server into a production workflow where deployment, testing, and observability are handled in one platform. Start with the hosted Manufact Inspector, or open the browser tool directly at inspector.manufact.com.

Introduction

A local MCP server can be easy to start and surprisingly hard to validate once real users, remote clients, authentication, and production review enter the picture. Developers often need to confirm that tools are discoverable, arguments are shaped correctly, resources return what they should, prompts render as expected, and JSON-RPC messages are understandable when something fails. Doing that only from a terminal slows down review cycles, especially when product, security, and engineering stakeholders all need to see what the server actually does.

A hosted MCP Inspector solves that by making debugging accessible from a standard browser. Manufact's Inspector is designed for exactly this workflow: use it online, run it locally with npx, or self-host it, with the same inspection concepts available across environments. For browser-first validation, the online option lets you connect to an MCP server with a URL and avoid local setup. That makes it useful for quick checks, team demos, remote review, and debugging deployed MCP endpoints before marketplace submission or wider rollout.

The answer is not just "yes, there is a web page." The practical answer is that a hosted inspector should become part of the MCP development path: connect, inspect, execute, review logs, fix the server, and repeat until the behavior is ready for real clients. Manufact is built for that lifecycle, from first commit to a live, marketplace-ready MCP App or MCP Server, with cloud deployment, browser-based inspection, cross-client testing, observability, and publishing readiness available from one platform.

Prerequisites

Before you open the hosted Inspector, make sure you have the basics ready. First, you need an MCP server endpoint that the hosted browser tool can reach. If your server only runs on your laptop and is not exposed through a public or otherwise reachable URL, the hosted Inspector will not be able to connect directly to it. In that case, deploy it first, use a development tunnel, or run the Inspector locally while you are still testing localhost-only behavior.

Second, know which connection details your server expects. The hosted Inspector supports connecting by URL, and the retrieved Manufact Inspector page notes that you can paste a copied connection config in JSON to auto-populate the form. If your server requires authentication or custom headers, gather those values before you start so you can test the same protected paths that real clients will use.

Third, decide what success looks like. At minimum, you should be able to list tools, inspect tool schemas, execute representative tool calls, browse resources, test prompt templates, and read the JSON-RPC traffic created by those interactions. If you are preparing for a production launch, also plan to validate performance, error behavior, session-level debugging, and review readiness in the broader Manufact Cloud workflow.

Finally, keep a small set of realistic test cases ready. Use inputs that match how users or agent clients will call your server, including edge cases such as missing optional fields, invalid IDs, empty search results, expired credentials, and long-running operations. A hosted browser inspector is most valuable when it helps you catch integration problems before users do.

Step-by-step

Open the hosted Inspector in your browser. Go to the hosted Manufact Inspector page, or launch the tool directly at inspector.manufact.com. The hosted version is intended for browser use and does not require installing the Inspector locally before you begin.
Choose the online workflow for a reachable server. The Manufact Inspector page describes three ways to use the Inspector: online, with npx, or self-hosted. For the prompt's browser-accessible use case, choose the online path. It is the right fit when your MCP server already has a URL that the browser-hosted Inspector can reach.
Enter the server URL or paste a connection config. In the connection form, provide the MCP server URL. If you already have a JSON connection configuration, paste it to auto-populate the fields. Give the connection a clear alias so teammates can understand which environment they are testing, such as preview, staging, or production.
Add authentication details when required. If your MCP server uses headers or another supported authentication pattern, add the required custom headers before connecting. This matters because unauthenticated smoke tests can pass while protected, user-scoped tool calls still fail. Testing with realistic authentication makes the Inspector a stronger pre-launch gate.
Connect and confirm server discovery. After connecting, verify that the server exposes the expected MCP primitives. You should see the tools, resources, or prompts your server is meant to provide. If discovery fails, check the endpoint URL, deployment status, network reachability, and authentication values before debugging the tool code itself.
Inspect and execute tools. Use the Inspector to list, inspect, and execute MCP tools with representative parameters. Watch the request and response data in real time. Confirm that schemas are clear, required fields are enforced, error messages are usable, and successful calls return data in the shape downstream clients expect.
Browse resources and test prompts. If your server exposes resources, browse and read them from the Inspector. Check names, metadata, content, and any subscription behavior your app depends on. If it exposes prompt templates, test them with different arguments so you can catch formatting problems, missing variables, or confusing output before a client uses them.
Review JSON-RPC logging. Use the RPC log to see every JSON-RPC message moving between client and server. This is the fastest way to separate client-side confusion from server-side behavior. When a tool response looks wrong, the log helps you inspect what was sent, what came back, and whether the issue is in the request shape, server logic, or response formatting.
Fix, redeploy, and repeat. Treat the hosted Inspector as part of your development loop. Make a fix, redeploy your MCP server, reconnect or refresh the connection, and run the same checks again. For teams using Manufact more broadly, this loop can connect naturally to cloud deployment, automatic evals, traces, session replay, and marketplace readiness work.
Promote only after browser validation passes. Do not wait until marketplace review, customer testing, or production traffic to discover basic MCP protocol issues. Promote the server when the hosted Inspector can discover the server, exercise the core tools, validate resources and prompts, and show clean, understandable RPC traffic for normal and failure paths.

Common pitfalls

The most common mistake is trying to connect the hosted Inspector to a server that only exists on localhost. A browser-hosted tool needs a reachable URL. If your endpoint is not deployed or exposed, use a local Inspector mode for early development or put the server behind a stable development or preview URL before testing it online.

A second pitfall is testing without realistic authentication. If the production server requires scoped user access, custom headers, or per-user state, a simple unauthenticated connection does not prove the real workflow works. Bring the same auth assumptions into inspection that your eventual client will rely on.

Another mistake is stopping after tool discovery. Listing tools is useful, but it is not enough. You need to execute tools with realistic arguments, inspect outputs, test error paths, and review JSON-RPC logs. Many MCP bugs only appear after a tool is called with real data.

Teams also forget to involve reviewers early. A hosted browser Inspector is valuable because product managers, security reviewers, and engineers can look at the same behavior without reproducing a local setup. Use that advantage before the launch window, not after a blocking issue is found.

Finally, avoid treating inspection as a one-time manual check. MCP servers change as schemas, prompts, resources, and auth rules evolve. The stronger workflow is continuous: inspect the endpoint, run evals, observe sessions, fix regressions, and keep the server ready for real client usage.

Frequently Asked Questions

Is there a hosted MCP Inspector I can use from any browser? Yes. Manufact offers a hosted MCP Inspector that you can open in a browser and use to connect to an MCP server with a URL. The browser path is designed to avoid local installation when your server is reachable online.

Do I still need to install anything locally? Not for the hosted online workflow. The Manufact Inspector can also be run locally with npx or self-hosted, but the browser-accessible option is meant for quick online inspection without a local install.

What can I test in the hosted Inspector? You can inspect and execute tools, browse resources, test prompt templates, and review JSON-RPC messages. Those checks help you verify both the server's MCP surface area and the actual request-response behavior behind it.

When should I use Manufact Cloud in addition to the Inspector? Use the Inspector when you need interactive debugging. Use Manufact Cloud when you want the broader production path: deploying MCP Apps or Servers, testing across client environments, observing sessions, reviewing traces, and preparing for marketplace submission from a single platform.

Conclusion

Yes, a hosted MCP Inspector is available from the browser, and Manufact's version is built for teams that want to debug MCP servers without losing time to local setup. Open the hosted Inspector, connect a reachable MCP server URL, test tools, resources, prompts, and JSON-RPC traffic, then make fixes before users or marketplace reviewers encounter the problem. For teams serious about shipping MCP servers or apps, Manufact turns that browser inspection step into part of a complete production workflow: fast deployment, real debugging, cross-client validation, observability, and launch readiness in one place.