Hosted App

MCPJam Inspector is available as a hosted web app at app.mcpjam.com. Build, test, debug, and evaluate MCP servers and apps with frontier models — all from the web.

​

Why use the hosted app?

• No installation — Open a browser and start testing.
• Always up to date — You’re always on the latest version without running npx @mcpjam/inspector@latest.
• Shareable — Share server URLs with your team. Everyone can inspect the same server without local setup.

​

Share your MCP server

Send a link to your MCP server or app the same way you’d share a Google Doc. Anyone with a MCPJam account who opens it can immediately start chatting with the server right in their browser. Try it yourself with the Excalidraw MCP server:

​

Quick start

1. Go to app.mcpjam.com
2. Click Add server and enter your MCP server’s URL (must be HTTPS)
3. Choose your authentication method (None, Bearer Token, or OAuth 2.0)
4. Start inspecting tools, resources, and prompts

​

Usage limits

The hosted app uses a daily credit system to power AI features like chat.

• Guests get a free daily usage allowance. The sidebar shows a progress bar with how much of your daily limit you’ve used and when it resets. When you reach the limit, you’ll be prompted to sign in.
• Signed-in users get 10× the daily usage of a guest. Your daily usage and any paid credit balance are visible in the account menu at the bottom of the sidebar.
• Paid credits can be topped up from the billing page and are shown alongside your daily limit in the account menu.

​

Signing out

Open the account menu at the bottom of the sidebar (click your avatar or email) and choose Sign out. You’ll be returned to the public app as a guest, and any signed-in usage allowance is replaced by the guest allowance until you sign back in. OAuth tokens you connected while signed in remain in your hosted workspace and are restored the next time you sign in on the same account.

​

OAuth token reveal

When you connect an OAuth server in the hosted app, your OAuth credentials are stored securely in Vault. You can inspect those tokens on demand from the server’s Overview tab without them ever being written to localStorage or shared with other users. To reveal tokens:

1. Open the Servers tab and click the server name to open its detail modal.
2. Go to the Overview tab.
3. Under OAuth Tokens, click Reveal tokens.
4. Each token (access token, refresh token, ID token) is masked by default. Click the eye icon next to a token to reveal its value, or click the copy icon to copy it directly without revealing it.

Expired tokens are automatically refreshed before being returned. Revealed values are kept component-local and are cleared when you close the modal.

​

What’s different

The following features are not available in the hosted app. They are available when running MCPJam locally via npx, Docker, or the desktop app.

​

HTTPS only

The hosted app requires all MCP server connections to use HTTPS. If your server only supports HTTP, use the local inspector instead.

​

No STDIO connections

STDIO servers are not available in the hosted version of MCPJam. Use a Streamable HTTP endpoint instead, or switch to the local inspector.

​

No tunneling

Tunneling exposes a local MCP server over HTTPS for remote access. Since the hosted app connects to already-remote servers, tunneling is not applicable.

​

No skills

Skills live on your filesystem and can only be discovered and run from the local inspector or desktop app.

​

No tasks

Tasks are not yet available in the hosted app.

​

Billing

​

Payment history

The Payment history card on the org billing page lists your recent credit top-ups. Each row shows: If a receipt isn’t available yet the cell shows Processing (for pending charges) or Not available (for succeeded charges without a receipt link). To add credits, click Top up — either from the empty state when you have no history, or from the credit balance card above.