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., "@MCP Local-to-Hosted Deployment Fix reset the demo and run the smoke tests"
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.
# MCP Local-to-Hosted Deployment Fix
A local MCP server can work on its author's laptop while a hosted-like client fails because transport, endpoint, authentication, version, and discovery are implicit. This MVP makes one supported path explicit and testable.
Related MCP server: mock-mcp-server
Before: manual local process, unclear endpoint, unpinned dependencies, vague errors. After: Node 22 server version demo-1, streamable HTTP at /mcp, sandbox bearer token, stable two-tool registry, tenant fixtures, request IDs, deterministic failures, smoke client, reset script, and runbook.
No package installation is required or permitted for this demo.
./scripts/reset-demo.sh
./scripts/start-demo.sh
# in another terminal
node runtime/client.mjs
node runtime/run-tests.mjsHealth, token issuance, initialize, discovery, tenant-a read, and approval-denied archive are covered by smoke/client.ts. The read returns only tenant-a titles. The write never mutates data and is denied without a request-bound approval string.
Use MCP_FAILURE=timeout ./scripts/start-demo.sh or MCP_FAILURE=unavailable ./scripts/start-demo.sh. The failure matrix is represented by deterministic unit and integration checks in tests/run-tests.mjs.
The dependency-free runner verifies token rejection and expiry, protocol mismatch, discovery, schemas, tenant isolation, approval policy, read, write, and registry behavior. Run it after reset. Logs are JSON lines in logs/events.jsonl and never contain the raw bearer token.
See docs/architecture.md, docs/compatibility.md, and docs/runbook.md. Intended dependency versions are pinned in package.json; no node_modules is required for the constrained fallback.
Maintained by Kiell Tampubolon. More selected work at kielltampubolon.id.
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP Gateway: wrap any MCP server with cold-start retries, uptime SLA, and per-execution MPP billing.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Guarded MCP server for agent-readable business truth, provenance, readiness, and discovery.
Minimal streamable HTTP MCP server used for owned-account registry connectivity tests.
