Watch

History

Repository files (latest commit first)
Filename	Latest commit message	Latest commit date
Olivier Chafik 2dd223b611 refactor: rename request methods to remove send prefix (#161 ) * refactor: rename request methods to remove send prefix Following the MCP TS SDK convention where request methods don't have the "send" prefix (reserved for notifications): - App.sendMessage() → App.message() - App.sendOpenLink() → App.openLink() - AppBridge.sendResourceTeardown() → AppBridge.resourceTeardown() The old method names are kept as deprecated aliases for backwards compatibility. Updated all examples to use the new method names. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * test: add tests for deprecated method aliases - Update existing tests to use new method names (message, openLink) - Add tests verifying deprecated aliases are same reference as new methods - Add tests verifying deprecated aliases still work functionally 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> * refactor: rename message→sendMessage, resourceTeardown→teardownResource - App.message() → App.sendMessage() (with deprecated message alias) - AppBridge.resourceTeardown() → AppBridge.teardownResource() (with deprecated aliases) This better follows the pattern where methods that send data have 'send' or action verb prefix. * fix: update examples to use sendMessage instead of message * fix: update basic-host to use teardownResource * fix: update threejs-server to use sendMessage * refactor: remove deprecated app.message alias The app.message alias was removed since sendMessage is the correct name. sendResourceTeardown already exists in AppBridge. * refactor: remove resourceTeardown alias, keep only sendResourceTeardown --------- Co-authored-by: Claude <noreply@anthropic.com>		2025-12-16 22:07:06 +00:00
..
src	refactor: rename request methods to remove send prefix (#161 )	2025-12-16 22:07:06 +00:00
mcp-app.html	Add color-scheme meta tag to all example apps	2025-12-15 11:42:18 -08:00
package.json	fix: Windows compatibility - bun as optional dep, cross-env for examples (#145 )	2025-12-16 14:07:38 +00:00
README.md	Add wiki-explorer-server example (#122 )	2025-12-11 13:58:05 +01:00
server.ts	feat: add server helpers, make connect() to default to parent post transport (#165 )	2025-12-16 21:25:26 +00:00
tsconfig.json	Add wiki-explorer-server example (#122 )	2025-12-11 13:58:05 +01:00
vite.config.ts	Add wiki-explorer-server example (#122 )	2025-12-11 13:58:05 +01:00

README.md

Example: Wiki Explorer

Visualizes Wikipedia link graphs using a force-directed layout. Explore how Wikipedia pages are connected by expanding nodes to reveal first-degree links.

Features

Force-directed graph visualization: Interactive graph powered by force-graph
Node expansion: Click any node to expand and see all pages it links to
Visual state tracking: Nodes change color based on state (blue = default, green = expanded, red = error)
Direct page access: Open any Wikipedia page in your browser

Running

Install dependencies:
```
npm install
```

Build and start the server:

npm run start:http  # for Streamable HTTP transport
# OR
npm run start:stdio  # for stdio transport

View using the basic-host example or another MCP Apps-compatible host.

Tool Input

To test the example, call the get-first-degree-links tool with a Wikipedia URL:

{
  "url": "https://en.wikipedia.org/wiki/Graph_theory"
}

Click nodes in the graph to Open (view in browser) or Expand (visualize linked pages).

Architecture

Server (`server.ts`)

MCP server that fetches Wikipedia pages and extracts internal links.

Exposes one tool:

get-first-degree-links - Returns links to other Wikipedia pages from a given page

App (`src/mcp-app.ts`)

Vanilla TypeScript app using force-graph for visualization that:

Receives tool inputs via the MCP App SDK
Renders an interactive force-directed graph
Supports node expansion to explore link relationships