Skip to content

Commit b37fda7

Browse files
committed
docs: update walkthroughs
1 parent 9342e2a commit b37fda7

2 files changed

Lines changed: 20 additions & 6 deletions

File tree

docs/src/guide/server/ruby/walkthrough.md

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ http_server.mount('/mcp', MCPServlet, mcp_server)
114114

115115
The `MCPServlet` processes incoming `POST` requests, passes them to the MCP server instance, and returns the JSON response. It also handles CORS `OPTIONS` requests to allow cross-origin communication with a web client.
116116

117-
## 5. Run the Server
117+
## 5. Run and Test
118118

119119
Finally, add the code to start the server.
120120

@@ -131,4 +131,16 @@ Your `server.rb` is now complete. You can run it with:
131131
ruby server.rb
132132
```
133133

134-
The server will be available at `http://localhost:8081/mcp`.
134+
The server will be available at `http://localhost:8081/mcp`.
135+
136+
To test your new endpoint, you can use the [`ui-inspector`](https://github.com/idosal/ui-inspector):
137+
138+
1. Go to the [ui-inspector repo](https://idosal.github.io/ui-inspector/) and run locally.
139+
2. Open the local client in a browser (usually `http://localhost:6274`)
140+
3. Change the Transport Type to "Streamable HTTP".
141+
4. Enter your server's MCP endpoint URL: `http://localhost:3000/mcp`.
142+
5. Click "Connect".
143+
144+
The inspector will show tools for the different content types. When you call them, the UI resource will be rendered in the inspector's Tool Results.
145+
146+
You've now successfully integrated `mcp-ui` into your Ruby server! You can now create more complex tools that return different types of UI resources.

docs/src/guide/server/typescript/walkthrough.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -133,10 +133,12 @@ npx ts-node server.ts
133133

134134
To test your new endpoint, you can use the [`ui-inspector`](https://github.com/idosal/ui-inspector):
135135

136-
1. Go to the **[ui-inspector website](https://idosal.github.io/ui-inspector/)**.
137-
2. Enter your server's MCP endpoint URL: `http://localhost:3000/mcp`.
138-
3. Click "Connect".
136+
1. Go to the [ui-inspector repo](https://idosal.github.io/ui-inspector/) and run locally.
137+
2. Open the local client in a browser (usually `http://localhost:6274`)
138+
3. Change the Transport Type to "Streamable HTTP".
139+
4. Enter your server's MCP endpoint URL: `http://localhost:3000/mcp`.
140+
5. Click "Connect".
139141

140-
The inspector will show the `greet` tool. When you call it, the UI resource will be rendered in the inspector's "UI" tab.
142+
The inspector will show tools for the different content types. When you call them, the UI resource will be rendered in the inspector's Tool Results.
141143

142144
You've now successfully integrated `mcp-ui` into your TypeScript server! You can now create more complex tools that return different types of UI resources.

0 commit comments

Comments
 (0)