Skip to main content
Glama

MCP Inspector

Test any MCP server from your browser. Supports every Model Context Protocol feature, including tools, resources, prompts, tasks, elicitation, sampling, and OAuth 2.1.

About MCP Inspector

Inspect any MCP server directly from your browser. No login required.

  • State persisted in URL for easy sharing and bookmarking
  • Requests go directly to the MCP server, never logged by Glama
  • Additional debugging info printed to browser console

Try the inspector with our test server.

Missing a feature? Join our Discord to request it.

Supported MCP Features

Glama's MCP Inspector implements the full Model Context Protocol specification.

Core primitives

  • Tools – invoke server-defined functions
  • Resources – read data exposed by the server
  • Resource Templates – parameterized resource URIs
  • Prompts – reusable prompt templates

Server → client requests

  • Elicitation – server asks the user for structured input mid-call
  • Sampling – server asks the client to run an LLM
  • Roots – server queries client filesystem roots

Long-running operations

  • Tasks – long-running tool executions with status tracking
  • Progress Notifications – real-time progress updates with percent and message
  • Cancellation – abort in-flight requests

Real-time updates

  • Resource Subscriptions – live updates when a resource changes
  • List-changed Notifications – servers announce tool, prompt, and resource changes
  • Logging – structured server logs streamed to the client

Utilities

  • Ping – connection health check
  • Completion – argument autocomplete for tools and prompts
  • Pagination – cursor-based list iteration

Authentication

  • OAuth 2.1 – authorization code flow with refresh tokens
  • Dynamic Client Registration (DCR) – automatic client provisioning
  • PKCE – proof key for code exchange
  • Bearer Token – static token authentication
  • Custom Headers – arbitrary request headers
  • Search Params – API key in URL query string

Transports

  • Streamable HTTP – modern transport replacing SSE
  • Server-Sent Events (SSE) – legacy streaming transport
  • Local stdio servers – exposed via mcp-proxy public tunnel

Content types

  • Text – plain text responses
  • Images – base64 image content (PNG, JPEG, WebP)
  • Audio – base64 audio content (WAV, MP3)
  • Embedded Resources – linked resource references

Expose Local MCP Servers

Test your local MCP servers with the inspector by exposing them via a public tunnel using mcp-proxy.

# Expose your MCP server via a public tunnel
npx mcp-proxy --port 8080 --tunnel -- tsx server.js

# Request a specific subdomain
npx mcp-proxy --port 8080 --tunnel --tunnelSubdomain myapp -- tsx server.js

# When the tunnel is established, you'll see a message like:
tunnel established at https://bright-wombat-83.tunnel.gla.ma

Once the tunnel is established, you can use the provided URL to connect to your local server in the inspector.

Bookmarkable URLs

Your server configurations are automatically saved in the URL. You can bookmark the current page to save your server setup, or share the URL with others to give them the same configuration.

URL Parameters

serversJSON array containing server configurations (name, URL, authentication, headers, timeout)
activeID of the currently selected server
tabActive tab: tools, resources, resource-templates, or prompts
toolName of the selected tool
argsJSON object containing tool arguments