@modelcontextprotocol/inspector 0.16.6 → 0.16.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -98,6 +98,16 @@ The MCP Inspector provides convenient buttons to export server launch configurat
98
98
  }
99
99
  ```
100
100
 
101
+ **Streamable HTTP transport example:**
102
+
103
+ ```json
104
+ {
105
+ "type": "streamable-http",
106
+ "url": "http://localhost:3000/mcp",
107
+ "note": "For Streamable HTTP connections, add this URL directly in your MCP Client"
108
+ }
109
+ ```
110
+
101
111
  - **Servers File** - Copies a complete MCP configuration file structure to your clipboard, with your current server configuration added as `default-server`. This can be saved directly as `mcp.json`.
102
112
 
103
113
  **STDIO transport example:**
@@ -131,9 +141,23 @@ The MCP Inspector provides convenient buttons to export server launch configurat
131
141
  }
132
142
  ```
133
143
 
144
+ **Streamable HTTP transport example:**
145
+
146
+ ```json
147
+ {
148
+ "mcpServers": {
149
+ "default-server": {
150
+ "type": "streamable-http",
151
+ "url": "http://localhost:3000/mcp",
152
+ "note": "For Streamable HTTP connections, add this URL directly in your MCP Client"
153
+ }
154
+ }
155
+ }
156
+ ```
157
+
134
158
  These buttons appear in the Inspector UI after you've configured your server settings, making it easy to save and reuse your configurations.
135
159
 
136
- For SSE transport connections, the Inspector provides similar functionality for both buttons. The "Server Entry" button copies the SSE URL configuration that can be added to your existing configuration file, while the "Servers File" button creates a complete configuration file containing the SSE URL for direct use in clients.
160
+ For SSE and Streamable HTTP transport connections, the Inspector provides similar functionality for both buttons. The "Server Entry" button copies the configuration that can be added to your existing configuration file, while the "Servers File" button creates a complete configuration file containing the URL for direct use in clients.
137
161
 
138
162
  You can paste the Server Entry into your existing `mcp.json` file under your chosen server name, or use the complete Servers File payload to create a new configuration file.
139
163
 
@@ -1,4 +1,4 @@
1
- import { u as useToast, r as reactExports, j as jsxRuntimeExports, p as parseOAuthCallbackParams, g as generateOAuthErrorDescription, S as SESSION_KEYS, I as InspectorOAuthClientProvider, a as auth } from "./index-B_qh-Btq.js";
1
+ import { u as useToast, r as reactExports, j as jsxRuntimeExports, p as parseOAuthCallbackParams, g as generateOAuthErrorDescription, S as SESSION_KEYS, I as InspectorOAuthClientProvider, a as auth } from "./index-3LzLs-Yz.js";
2
2
  const OAuthCallback = ({ onConnect }) => {
3
3
  const { toast } = useToast();
4
4
  const hasProcessedRef = reactExports.useRef(false);
@@ -1,4 +1,4 @@
1
- import { r as reactExports, S as SESSION_KEYS, p as parseOAuthCallbackParams, j as jsxRuntimeExports, g as generateOAuthErrorDescription } from "./index-B_qh-Btq.js";
1
+ import { r as reactExports, S as SESSION_KEYS, p as parseOAuthCallbackParams, j as jsxRuntimeExports, g as generateOAuthErrorDescription } from "./index-3LzLs-Yz.js";
2
2
  const OAuthDebugCallback = ({ onConnect }) => {
3
3
  reactExports.useEffect(() => {
4
4
  let isProcessed = false;