Enables testing interaction with the MCP server using command-line HTTP requests, allowing users to establish SSE sessions and call calculator tools in a two-terminal setup.
Provides explanation prompts, practice problems, and tutoring content in Markdown format through the explain-calculation, generate-problems, and calculator-tutor tools.
Used to visualize the communication flow between client and server in the README documentation, showing the sequence of events in the two-endpoint HTTP + SSE transport.
Serves as the runtime environment for the MCP server, with specific version requirements (v18.x or higher) needed to run the implementation.
Used as the implementation language for the MCP server, with type definitions for the calculator tools and server components.
Provides schema validation for all incoming tool parameters to prevent invalid data from causing runtime errors.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@example-mcp-server-ssecalculate 15 + 7"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
example-mcp-sse
migration-focused starter for building MCP servers on Streamable HTTP, replacing the deprecated SSE transport. uses TypeScript SDK v2 pre-alpha.
part of a series: stdio · stateless · stateful · sse (you are here)
what it does
runnable Streamable HTTP server with session management, event replay, and graceful shutdown
scaffold CLI (
create-mcp-streamable-starter/create-mcp-sse-starter) to generate new projects from a proven templatecalculator demo with tools, resources, prompts, and structured output to exercise all MCP primitives
vendored SDK v2 alpha tarballs for reproducible installs without npm registry dependency
smoke tests for both the root project and scaffolded output
CI workflow that validates root build, lint, typecheck, and generated project end-to-end
Related MCP server: MISP-MCP-SERVER
quick start
npm install
npm run devthe server starts at http://127.0.0.1:3000 with these endpoints:
endpoint | method | purpose |
| POST | JSON-RPC request/response |
| GET | notification stream (stateful SSE) |
| DELETE | session termination |
| GET | health check with active session list |
| GET | server metadata |
configure with environment variables or CLI flags:
PORT=4000 npm run dev
# or
npm run dev -- --port 4000scaffold cli
generate a new MCP Streamable HTTP project:
npm run create -- --name my-server --target ./my-server
cd my-server
npm install
npm run devthe generated project includes the full server module structure, vendored SDK tarballs, and its own smoke test. see docs/03-scaffold-cli.md for the complete reference.
documentation
doc | description |
documentation hub and reading order | |
prerequisites, install, run, verify | |
module layout, request lifecycle, design rationale | |
CLI reference, generated structure, extension workflow | |
v2 packages, migration checklist, vendoring strategy | |
root and generated project validation, release checklist |
sdk v2 context
this project targets the MCP TypeScript SDK v2 pre-alpha (2.0.0-alpha.0). v2 splits the monolithic @modelcontextprotocol/sdk into @modelcontextprotocol/server, @modelcontextprotocol/client, and @modelcontextprotocol/node. the server-side SSEServerTransport is removed; NodeStreamableHTTPServerTransport from @modelcontextprotocol/node is the replacement. v1.x remains the stable production recommendation from the upstream project. vendored tarballs in vendor/ pin the exact alpha artifacts for reproducible builds.
license
MIT
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.