MCP Web Worker Demo

Created By
weolopeza year ago
mcp demo, client and server as web workers from a web UI
Overview

What is MCP Web Worker Demo?

MCP Web Worker Demo showcases a Model Context Protocol (MCP) client implementation using a Shared Web Worker architecture, demonstrating how to utilize MCP in a browser environment with a decoupled architecture using pure JavaScript.

How to use MCP Web Worker Demo?

To use the demo, ensure the SDK is built, start a web server, and navigate to the provided URL in a compatible browser. Click the 'Connect to MCP' button to establish a connection and explore various features.

Key features of MCP Web Worker Demo?

  • Implementation of an MCP client in a worker context.
  • Simplified API for main thread communication.
  • Interactive UI for testing MCP features.
  • Diagnostics and connection status indicators.

Use cases of MCP Web Worker Demo?

  1. Testing and demonstrating the capabilities of the Model Context Protocol.
  2. Exploring the performance benefits of using Shared Web Workers.
  3. Learning about decoupled architecture in web applications.

FAQ from MCP Web Worker Demo?

  • What browsers support this demo?

The demo requires browsers that support Shared Web Workers, such as Chrome and Edge.

  • How do I troubleshoot issues?

Check the browser console for error messages and ensure you are accessing the demo via a web server, not from the file system.

  • Is there a fallback for unsupported browsers?

No, this demo is specifically designed to showcase Shared Worker advantages and does not provide fallbacks.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
weolopez
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago