Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y @dunx/[email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add dunx-mcp -- npx -y @dunx/mcp@3.10.5Ejecútalo en una terminal.
{ "mcpServers": { "dunx-mcp": { "command": "npx", "args": [ "-y", "@dunx/[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
Dependency injection for Bun. Everything a service needs, one version.
Controllers, dependency injection, validation, OpenAPI, WebSockets, queues, an ORM, auth, a test harness and an ops dashboard. Released together, tested together, on Bun's own primitives.
A Model Context Protocol server for dunx: the written guide and scaffold catalogue with no app, plus your routes, providers and modules once you point it at one
bunx @dunx/create-app my-api
Elysia and Hono hand you a router, and everything above it is yours to choose and keep in step. This is the other trade: one dependency, one release train.
Every one of those is a Bun primitive or a best-in-class library wired to one,
never a reimplementation. Each is opt-in: @dunx/core has zero dependencies,
and an app that imports no queue installs no queue.
import { Logger, Module } from '@dunx/core';
import {
Controller,
Get,
HttpFactory,
type Input,
type RouteSchemas,
} from '@dunx/http';
export class GreetingsService {
constructor(private readonly logger: Logger) {}
greet(name: string) {
this.logger.info('greeting', { name });
return { greeting: `hello, ${name}` };
}
}
@Controller('greetings')
export class GreetingsController {
constructor(private readonly greetings: GreetingsService) {}
@Get('/:name')
one(input: Input<RouteSchemas>) {
return this.greetings.greet(input.req.params['name'] ?? 'world');
}
}
@Module({
controllers: [GreetingsController],
providers: [GreetingsService],
})
export class AppModule {}
const app = await HttpFactory.create(AppModule);
await app.listen(3000);
There is no @Injectable(), no @Inject(), no reflect-metadata import and no
experimentalDecorators, and a handler returns a plain value instead of calling
Response.json(). Two lines in bunfig.toml turn the constructor types into
wiring:
preload = ["@dunx/transform/preload"]
[test]
preload = ["@dunx/transform/preload"]
Bun's test runner reads its own preload, so bun test needs the [test]
entry. Without it the app runs, but the tests fail at the first provider with a
constructor parameter.
The constructor injection above reads like NestJS. The mechanism resolving it underneath is different, in four places.
No reflect-metadata, and no experimentalDecorators. dunx uses standard
TC39 decorators. @dunx/transform reads each class's constructor parameter
types at load time with oxc-parser, a
Rust parser over N-API, and records them on the class. There are no parameter
decorators in the TC39 proposal, so @Inject() does not exist and never will.
A type that does not exist at runtime fails boot. If a parameter's type is
an interface, a primitive or a type-only import, dunx fails at boot and names
that parameter. emitDecoratorMetadata gives you undefined and a stack trace
three frames away from the mistake.
No forwardRef. The dependency record is a thunk, evaluated at resolution
rather than at class-definition time, so a circular import resolves on its own.
The container is scoped. Every module reference is a scope holding what it
declares, exports is its public surface, and an absent exports exports
nothing. A module that takes no options is a decorated class rather than a
forRoot(), because each forRoot() call returns a fresh object and so a fresh
scope.
One thing to add rather than delete: every relative import ends in .js,
because moduleResolution: nodenext is what the scaffold sets. An extensionless
specifier is a compile error rather than a runtime surprise.
examples/full running on a
Raspberry Pi 5: the API explorer, the ops dashboard, bull-board, and a
walkthrough that drives twenty-five capabilities from a browser, including a
transaction rolling back, a CSRF refusal, an idempotent retry, an order
crossing a RabbitMQ topic exchange, and the process's own request, query and
event-loop timingsAGENTS.md and a CLAUDE.mdStructure on Bun does not have to cost throughput. @dunx/http is a layer over
Bun.serve({ routes }). It lands at 88-99% of the raw server's throughput,
within noise of Elysia, and 3.8-5.5x NestJS on Fastify. Boot is 43 ms against
294 ms.
Median req/s, 64 connections, 5 runs:
The harness also runs Go, Rust and JVM subjects alongside these. The NestJS
subject is real NestJS with real reflect-metadata. It states what it cannot
measure, too: the load generator shares a machine with the subject, and the
closed-loop design is subject to coordinated omission.
Reproduce it with bun run --filter '@dunx/bench' start. The methodology is in
internal/bench/README.md.
Bun.serve, bun:sqlite, Bun.RedisClient and
Bun.password are load-bearing throughout.A provably-fair crash game: bet during the window, watch the rocket climb, cash out before it explodes. Every round is verifiable after the fact.
21 modules, 8 controllers, a WebSocket gateway and 4 job handlers across 165
backend files, on @dunx/core, @dunx/http, @dunx/infra, @dunx/auth,
@dunx/openapi, @dunx/testing, @dunx/transform.
Each is kept alive by CI. Each also exits 0 with no database, Redis or S3 installed.
bun install
bun run --filter '@dunx/example-minimal' start
Pull requests are welcome. CONTRIBUTING.md is the full guide: how to get set up, which checks CI runs, the repo's rules on native implementations and third-party dependencies, and the house style a review will hold you to.
The short version: Bun only, no npm/npx/yarn/pnpm; bun install then
bun run build before anything else; run bun run ci, every gate CI runs, before
you push; conventional commits; a bug fix comes with the test
that would have caught it; and a claim about performance comes with the numbers.
A Model Context Protocol server for dunx: the written guide and scaffold catalogue with no app, plus your routes, providers and modules once you point it at one
{ "mcpServers": { "dunx-mcp": { "command": "npx", "args": [ "-y", "@dunx/[email protected]" ] } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
@dunx/mcp se ejecuta localmente por stdio.
Última comprobación: 2026-10-28. A Model Context Protocol server for dunx: the written guide and scaffold catalogue with no app, plus your routes, providers and modules once you point it at one