About Example MCP Sse
Example MCP Sse is an MCP server published by yigitkonur in the AI category: reference MCP server over SSE transport — calculator domain, teaching patterns.
The repository has 1 stars and 0 forks, with the last commit 5 months ago. Recent commit activity is the strongest signal that reported issues will get attention.
Install
git clone https://github.com/yigitkonur/example-mcp-sseThis server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.
Ask AI
Ask AI about Example MCP Sse
Powered by Claude · Grounded in docs
Security checks
Static checks derived from the repository 4 days ago. Heuristics on the source, not an audit.
- ✓README presentThe repository ships documentation.
- !License declaredNo license file. Legally you have no right to use it in a product.
- !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
- ✓Dependencies pinnedA lockfile pins dependency versions.
- ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
- !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.
README
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 template - calculator 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
quick start
npm install
npm run dev
the server starts at http://127.0.0.1:3000 with these endpoints:
| endpoint | method | purpose |
|---|---|---|
/mcp |
POST | JSON-RPC request/response |
/mcp |
GET | notification stream (stateful SSE) |
/mcp |
DELETE | session termination |
/health |
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 4000
scaffold cli
generate a new MCP Streamable HTTP project:
npm run create -- --name my-server --target ./my-server
cd my-server
npm install
npm run dev
the 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 |
|---|---|
| docs/README.md | documentation hub and reading order |
| docs/01-getting-started.md | prerequisites, install, run, verify |
| docs/02-architecture.md | module layout, request lifecycle, design rationale |
| docs/03-scaffold-cli.md | CLI reference, generated structure, extension workflow |
| docs/04-sdk-v2-notes.md | v2 packages, migration checklist, vendoring strategy |
| docs/05-validation.md | 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
README fetched from the repository 4 days ago. The original is authoritative.