Skip to content

v3.5.0 — Streamable HTTP transport

Latest

Choose a tag to compare

@felores felores released this 07 Jun 00:22
· 1 commit to main since this release
5eb20b0

@felores/kie-ai-mcp-server@3.5.0

Adds a remote Streamable HTTP transport (MCP spec 2025-11-25) alongside the default stdio path. Reimplements the capability from closed PR #3 against the current monorepo.

Added

  • Streamable HTTP transport — opt in with MCP_TRANSPORT=http or --http; stdio stays the default. Single /mcp endpoint (POST + GET/SSE + DELETE), stateful sessions keyed by Mcp-Session-Id (each session gets its own MCP Server over a shared Kie.ai client + task DB).
  • Health endpoint GET /health{status, transport, sessions, version}, unauthenticated and exempt from Origin/DNS-rebind checks for container probes.
  • Bearer-token auth (KIE_MCP_HTTP_TOKEN) and DNS-rebinding protection (MCP_ALLOWED_HOSTS, required when binding beyond loopback; the server fails fast otherwise). New env: MCP_HTTP_HOST (default 127.0.0.1), MCP_HTTP_PORT (default 3000).
  • Deploymentpackages/mcp/Dockerfile (multi-stage, bundled, non-root mcp user, HEALTHCHECK), root .dockerignore, docker-compose.coolify.yml, and docs/DEPLOY_HTTP.md.
  • README documents the feature and its benefits in English and Spanish.

Notes

  • stdio remains the default; the @felores/kie-cli package is unaffected.
  • Out of scope for now: OAuth 2.0 (RFC 9728) and eventStore stream resumability — the transport supports adding both later.

See CHANGELOG.md and docs/DEPLOY_HTTP.md.

npm: npx -y @felores/kie-ai-mcp-server