Streamable HTTP Transport for Web Fetch API

Created By
enZanea year ago
A Stremeable Http Transport for the Model Context Protocol (MCP) suited for frameworks like Hono, enabling real-time communication using Server-Sent Events (SSE) and standard HTTP requests. Implements the MCP Streamable HTTP transport specification for edge-compatible environments.
Overview

What is Streamable HTTP Transport?

Streamable HTTP Transport is a server transport implementation for the Model Context Protocol (MCP) designed for edge-compatible environments, enabling real-time communication through Server-Sent Events (SSE) and standard HTTP requests.

How to use Streamable HTTP Transport?

To use this transport, integrate it into your web framework (like Hono) and utilize the provided APIs for real-time data streaming and HTTP responses.

Key features of Streamable HTTP Transport?

  • Real-time bi-directional communication using SSE.
  • Supports both stateful and stateless session management.
  • Resumability support via an extensible event store.
  • Optimized for edge computing platforms.

Use cases of Streamable HTTP Transport?

  1. Building real-time applications that require instant data updates.
  2. Implementing live notifications and updates in web applications.
  3. Streaming data from servers to clients in a seamless manner.

FAQ from Streamable HTTP Transport?

  • What frameworks can I use with Streamable HTTP Transport?

It is designed to work with modern web frameworks like Hono.

  • Is there support for error handling?

Yes, the transport includes mechanisms for handling errors during data streaming.

  • Can I contribute to the project?

Absolutely! Contributions are welcome, and you can find guidelines in the CONTRIBUTING.md file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
enZane
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
//beforeyouship — LLM Cost Modeling From Your Editor
@Indiegoing

Query realistic LLM cost models without leaving your editor. beforeyouship models the **true monthly cost** of an LLM app architecture — retries, prompt caching, batch discounts, infra overhead, and 3×/10× growth — across GPT-5.x, Claude, Gemini, DeepSeek, and more. Not a token calculator: a planning tool for the design phase, before you commit to a stack. **No API key needed to try it** — demo mode covers the six free-tier models. A Pro key from [beforeyouship.dev](https://beforeyouship.dev) unlocks the full 18-model catalog. ## What you can ask - "How much will a RAG chatbot cost at 10,000 requests/day?" - "Compare Claude Haiku vs Gemini Flash pricing for my workload" - "What's the cheapest model for a multi-step agent at scale?" - "Show me current per-token prices for Anthropic models" ## Tools ### `estimate_cost` Full cost model for an architecture at a given usage level. Returns Naive / Realistic / Worst Case monthly cost per model, 3×/10× growth scenarios, and an opinionated recommendation with reasoning. ### `get_model_prices` Current per-1M-token pricing — input, output, cached input, batch — with context windows and staleness metadata. ### `list_archetypes` Seven preset architecture patterns (simple chatbot, chatbot with history, RAG pipeline, multi-model router, coding assistant, document processor, multi-step agent) used as starting points for estimates. ## Setup **Claude Code:** ​```bash claude mcp add --transport http beforeyouship https://beforeyouship.dev/api/mcp ​``` **Cursor / other clients** — add a remote server: ​```json { "mcpServers": { "beforeyouship": { "type": "streamable-http", "url": "https://beforeyouship.dev/api/mcp" } } } ​``` Add an `Authorization: Bearer bys_...` header with a Pro key for the full catalog. ## Try it > Estimate the monthly cost of a RAG pipeline at 10,000 requests/day

16 hours ago
Mnemom

18 hours ago
Linkpulse

19 hours ago