MCP SSE demo

Created By
the-vampiirea year ago
demo of MCP SSE server limitations using the bun runtime
Overview

What is MCP SSE Demo?

MCP SSE Demo is a reproducible demonstration that showcases the limitations of an MCP SSE server when using the Bun runtime compared to Node.js.

How to use MCP SSE Demo?

To use MCP SSE Demo, follow these steps:

  1. Install dependencies using Bun: bun install.
  2. Run the MCP inspector with npm run inspect.
  3. Open the inspector at http://localhost:5173.
  4. Select SSE as the transport and enter http://localhost:3500/sse as the URL.
  5. Open the dev tools network tab to inspect traffic.
  6. In another terminal, run the server using Bun: npm run start:bun.
  7. Connect to the server using the inspector and observe the logs.
  8. Kill the Bun server and run the server using Node.js: npm run start:node.
  9. Connect again to see the successful SSE connection.

Key features of MCP SSE Demo?

  • Demonstrates server behavior with different runtimes (Bun vs Node.js).
  • Provides a visual inspector for monitoring SSE connections.
  • Allows users to observe network traffic and logs during the connection process.

Use cases of MCP SSE Demo?

  1. Testing server performance with different runtimes.
  2. Educational purposes for understanding SSE connections.
  3. Debugging server issues related to transport protocols.

FAQ from MCP SSE Demo?

  • What is the purpose of this demo?

The demo illustrates how an MCP SSE server behaves under different runtime environments.

  • Is it necessary to use Bun?

No, you can also run the server using Node.js to compare the results.

  • Can I use this demo for production?

This demo is intended for educational and testing purposes, not for production use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
the-vampiire
Star
0
Language
TypeScript
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