Write decoupled functions in JavaScript/TypeScript and let Mercury Composable engines (Java, and the official Rust port) orchestrate them from Event Script flows and MiniGraph knowledge graphs — with no orchestration code in Node.js at all.
This package is a deliberately lightweight wrapper of the Event-over-HTTP protocol:
- an Event API host (
POST /api/event) that dispatches incoming event envelopes to your registered functions, - a thin client (
PostOffice) to call functions on peer applications the same way, - the standard event envelope wire format codec (language-neutral MsgPack), and
- a primitive in-process event bus — the single dispatch pipeline: one FIFO mailbox
per route consumed by
instancesworker loops, and - the minimalist utilities shared with the engines for consistency: configuration management, logging in the engines' presentation format, and distributed-trace context, and
- the OpenTelemetry forwarder (opt-in,
otel.forwarding=true): the host's trace spans exported over OTLP/HTTP to Dynatrace, Splunk or a collector — no SDK, no new dependency, and - the LLM helper extension (
extensions/llm-helper):llm.chat,llm.streamandllm.healthon the official Anthropic SDK — the graph decides, the model advises;llm.streamrelays the model's token batches as they are produced. - the MCP binding extension (
extensions/mcp-binding): one composable route per allowlisted MCP tool, over stdio or streamable HTTP on the official MCP SDK — a graph's agent loop names the route, this app issues thetools/call, and a server cannot change a tool under the graph (its schema digest is pinned). - the built-in agent tools extension (
extensions/agent-tools): the essential tools an agent loop names in its catalog — files inside one workspace, the web inside an allowlist of sites, the agent's knowledge graph inside one database, a clock — each a composable function whose sandbox is deployment configuration, never an argument of a call, with its catalog row published. - the ask-a-person main flow extension (
extensions/ask-person):person.ask, the function a graph's hold path calls before it suspends for a person - a signed, stateless ticket, the resume link and one message event to the installation's channels; the reply page and endpoint that bring the decision back (RFC-0014, step 1); - the agent-question app (
extensions/agent-question): the first channel of that design, a store-and-forward inbox for a person whose device is not always connected - the intake, the replay, the stream and the automated click (RFC-0014, step 3).
Orchestration deliberately stays in the engines. Functions written here are addressed by
route name through the engines' declarative yaml.event.over.http map, so a flow or a
graph task calls a Node.js function exactly as if it were local.
Documentation: https://accenture.github.io/mercury-nodejs/ — including the AI Agent Guide for deterministic function generation.
Published on npm.
mercury-composablev4.12.30 is live —npm install mercury-composable. This repository was repurposed in August 2026 for the polyglot initiative: instead of re-porting the full composable foundation to Node.js, the fresh start rides the engines' Event-over-HTTP protocol — light by design. The previous Node.js port (up to v4.3.28) remains available in tagged releases only — it never occupied this name on the public registry.
// app.mjs
import { AppException, platform, preload } from 'mercury-composable';
preload('hello.node', { instances: 10 }, async (headers, body) => {
if (typeof body !== 'object' || body === null || !('text' in body)) {
throw new AppException(400, "missing 'text'");
}
return { text: String(body.text).toUpperCase(), language: 'node.js' };
});
await platform.run(); // port from rest.server.port (default 8085)Run it:
npm install mercury-composable
mercury-serve app.mjs -Drest.server.port=8087Call it from a Mercury engine application with two configuration entries and no code —
application.properties:
yaml.event.over.http=classpath:/event-over-http.yamlevent-over-http.yaml:
event.http:
- route: 'hello.node'
target: 'http://127.0.0.1:8087/api/event'Any Event Script task or MiniGraph graph.task node that names the route hello.node
now executes the Node.js function, with trace context carried end to end.
A handler receives the same two-part input as an engine TypedLambdaFunction —
(headers, body) — and returns the reply body (or an EventEnvelope for full control of
status and reply headers). Node.js is non-blocking by nature; handlers may be async.
- Throw
AppException(status, message)for intentional errors — it becomes the portable error contract on the wire (envelope status + message), handled by the calling flow's exception handler or the graph'serror.*contract. getTrace()exposestraceId/tracePath/cid;annotateTrace(k, v)sends an annotation back on the reply envelope.- Route aliases: the route is one name or a comma-separated list
(
preload('hello.declarative, hello.world', ...)), the engines'@PreLoadsemantics — every name is the same function with the sameinstancesand visibility, and a handler reads the name it was called as fromgetTrace().route. - Functions must be stateless; anything you must keep belongs to the caller's flow model or state machine.
PostOffice without an endpoint delivers through this application's own event bus —
the engines' semantics for an in-app po call:
isPrivate: truemeans exactly what it means in the engines: callable in-app only. Local calls reach private and public routes alike; the HTTP host keeps answering 403 for private targets from the wire.instancesis faithful: each route has one FIFO mailbox consumed by that many worker loops. RPC waits are bounded bytimeoutMs(the standard 408 envelope on breach), and a queued call whose caller already timed out is skipped, never wastefully executed.- There is no spill tier and no queue cap by design: back-pressure belongs to the tier that owns recovery — the engines' flows and graphs. A leaf host fails fast by deadline instead of hoarding work.
Local eventing is for simple leaf-side composition. Workflow processing belongs in Event Script and Knowledge Graph on the engines — that boundary is the architecture.
The same conventions as the engines, so a polyglot installation stays uniform:
| Key | Meaning | Default |
|---|---|---|
application.name |
application identity in logs | application |
rest.server.port |
Event API port | 8085 |
log.format |
text, json (pretty-printed) or compact (single-line JSONL) |
text |
log.level |
log level (LOG_LEVEL env var wins) |
INFO |
static.html.folder |
the folder of static web content the host serves (HTML, CSS, JS, images), relative to the application file | resources/public |
Configuration lives in the resources folder next to the application file, mirroring the
engines' classpath resources: resources/application.yml (or .yaml / .properties) beside
the file mercury-serve is given — never the working directory, so the configuration does not
depend on where the app is launched from — or an explicit --config path; see
examples/demo-app/resources/application.yml for a worked
sample. Values support ${ENV_VAR:default} substitution. Runtime parameter overrides use the
same -D syntax as the Java engine and the Rust port — checked first on every read, their values
resolved with the same substitution, so -Dkey='${ENV_VAR}' keeps a credential out of the process
list (appConfig().set(key, value) does the same programmatically, the f:setConfig analog):
mercury-serve app.mjs -Drest.server.port=8087 -Dlog.format=jsonLog lines follow the Java reference engine's pattern for one-aggregation consistency:
2026-08-22 10:15:30.123 INFO app:12 - Loaded PUBLIC hello.node, instances=10
The host serves the engines' operational endpoints on the same port as /api/event, so
Kubernetes probes and dashboards treat a Node.js app exactly like a Java or Rust engine app:
| Endpoint | Purpose |
|---|---|
GET / |
the static folder's index.html, else a minimal index page linking the endpoints below |
GET /info |
app identity, runtime, origin id, start time, uptime |
GET /info/routes |
registered routes split by visibility, with instance counts |
GET /env |
selected environment variables and configuration parameters |
GET /health |
dependency health checks — UP (HTTP 200) or DOWN (HTTP 400) |
GET /livenessprobe |
OK while the last health outcome was good, else HTTP 400 |
Configuration keys carry the engines' names: info.app.version, info.app.description,
show.env.variables and show.application.properties (opt-in lists — secrets are never
dumped wholesale), and mandatory.health.dependencies / optional.health.dependencies
(routes of health check functions; optional ones never change the overall status). A
health check function is a normal registered function — usually private — speaking the
engines' interface contract, called through the event bus:
preload('demo.health', { isPrivate: true }, async (headers, _body) => {
if (headers.type === 'info') {
return { service: 'demo.service', href: 'http://127.0.0.1' };
}
return 'demo.service is running fine'; // a non-200 reply marks it down
});JSON responses are pretty-printed — the engines' default-serializer presentation — and
unknown paths answer the engines' error shape
({"status": 404, "message": "Resource not found", "type": "error"}).
Kubernetes wiring: point livenessProbe at /livenessprobe and readinessProbe at
/health.
The host serves the files of static.html.folder — the Java engine's key, with the Rust engine's
location as its default, resources/public next to the application file — for any GET or HEAD
that no host path, extension route or function claims, so an application can ship a web front-end
beside its functions the way the engines' Playground does. A folder is served as its index.html,
so resources/public/index.html replaces the landing page at /. The content type follows the
engines' table by extension (text/javascript, text/css, image/svg+xml, fonts and images;
application/octet-stream otherwise); every file carries an ETag and answers If-None-Match with
304, and HTML is served Cache-Control: no-cache, so a redeployed page is revalidated while hashed
assets stay cached. A hidden entry, a .. segment, a symbolic link that leaves the folder or
anything that is not a regular file is not found, in the engines' error shape. A relative value of
the key is under the application file's folder, never the working directory; file: prefixes an
absolute path as in the Java engine; an empty value turns the service off.
The codec implements the
Event Envelope Wire Format
(standard format) and is verified against the golden conformance vectors shared by the
Java and Rust engines (test/vectors/vectors.json). The classic compact format is
detected and rejected with a teaching error — engines default to the standard format for
Event over HTTP.
Serialization notes: 64-bit integers beyond Number.MAX_SAFE_INTEGER decode as BigInt
(exact), smaller ones as number; timestamps travel as ISO-8601 UTC strings with
millisecond precision; binary payloads are Uint8Array.
This package intentionally contains no orchestration: no flows, no graphs, no persistence, no pub/sub broadcast — those live in the engines. What it does carry is deliberately minimal: functions, a primitive in-process event bus (route mailboxes + workers, RPC and drop-n-forget — nothing more), and the minimalist foundation utilities, keeping Node.js fast to prototype with while the composable core guarantees the architecture.
A function always runs in this process, never in a subprocess or an embedded interpreter. The one subprocess the pack may start is an MCP server reached over stdio: the pack runs it as a child process and talks to it over its standard input and output. That is why the MCP clients of the engines' agent loop (RFC-0011) live in the language packs: no engine starts a child process. The stdio MCP binding itself is still to come.
The LLM helper in extensions/llm-helper/ is an application on this package, not part of it
The MCP binding in extensions/mcp-binding/ is the other: the MCP client of the engines' agent loop, with
the one subprocess the Scope allows, an MCP server over stdio, started and owned by that app. The built-in
agent tools in extensions/agent-tools/ are the third: the file, web, knowledge-graph and clock tools such
a loop names in its catalog, each a composable function inside a sandbox the deployment configures.
(the npm package does not ship it). Its llm.chat is configurable: a stateless chat, or one
turn of a multi-turn tool-use loop whose transcript lives in the store the helper is configured
with.
The ask-a-person main flow in extensions/ask-person/ carries such a loop's wait for a person to the installation's
channels and brings the decision back through a resume link, knowing no channel and keeping no store; the
agent-question app in extensions/agent-question/ is one of those channels, a store-and-forward inbox for an
occasionally connected device, a separate application on the same package.
Apache 2.0 — see LICENSE.