@guillem_puche/mastra-effect 0.0.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Guillem Puche
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,25 @@
+@guillem_puche/mastra-effect
+Copyright 2026 Guillem Puche
+
+This product includes software developed as part of the Mastra project
+(https://github.com/mastra-ai/mastra), Copyright Mastra AI, Inc., licensed
+under the Apache License, Version 2.0.
+
+Portions of src/index.ts are derived from the in-tree Mastra server adapters,
+principally @mastra/elysia (server-adapters/elysia). The behaviour carried over
+includes the stream framing for both SSE and record-separated formats, the
+error-swallowing forwarding stream, the stripping of Transfer-Encoding from a
+forwarded response, the structure of the responseType dispatch, and the decision
+not to await the MCP transport start call. Further portions follow @mastra/hono
+(server-adapters/hono): propagating a client disconnect to an MCP transport
+(from its mcp-disconnect.ts), carrying the caller's auth into MCP transports,
+answering a failed MCP transport start with a server error, closing a stream
+that fails partway, reading every value of a repeated query key, reading the
+requestContext query parameter on POST, and passing an error's failingItems
+through. Those portions remain under the Apache License, Version 2.0.
+
+This package depends on Effect (https://github.com/Effect-TS/effect), which is
+licensed under the MIT License and is a peer dependency rather than redistributed
+here. A copy of Effect's source is vendored under docs/repos/effect as a git
+subtree for reference only; it is excluded from the published package and remains
+under its own license.

package/README.md

@@ -0,0 +1,219 @@
+# Mastra on an Effect HTTP server
+
+`@guillem_puche/mastra-effect` runs [Mastra](https://mastra.ai) — AI agents, workflows, memory, tools
+and MCP — inside an [Effect](https://effect.website) v4 HTTP server, instead of Hono, Express,
+Fastify, Koa, NestJS or Elysia.
+
+It registers Mastra's whole server route table onto an Effect `HttpRouter`, so Mastra's routes sit
+alongside your own on one port, one router and one middleware stack. A community adapter, maintained
+out of tree, verified against Mastra's own published conformance suites.
+
+## Why
+
+Mastra ships adapters for the popular Node frameworks, but not for Effect. Without one, an Effect
+application that wants agents has to run Mastra as a second process behind its own server, and then
+reconcile two routers, two sets of middleware and two ideas of what a request is.
+
+This removes that. Mastra's routes join your Effect server: one port, one router, one middleware
+stack. Because the adapter binds to a live `HttpRouter` **service** rather than a Layer, you hand it
+the router you already own — Mastra does not take the server over. A client that disconnects cancels
+the Mastra work it started, so an abandoned agent stops calling its model, and with a tracer
+installed every request gets a server span carrying its route pattern.
+
+Mastra itself runs its agents, tools and workflow steps as ordinary promises, outside the request's
+fiber. Three things cross back into Effect:
+
+- **Server errors.** A route that answers with a 5xx also fails the Effect request, as a
+  `MastraRouteError` that answers with Mastra's own response. Clients see no difference; your
+  middleware can `catchTag('MastraRouteError')`, and your logs and traces record the failure. A 4xx
+  stays a normal response. `new MastraServer({ errorChannel: false })` turns this off.
+
+  Like any failed Effect request, these skip middleware that changes the response with `Effect.map`.
+  To touch every answer, use a pre-response handler, as Effect's CORS middleware does —
+  [`alongside-your-routes`](examples/alongside-your-routes) shows one.
+- **Your services and the request's span, inside tools and steps.** `runInRequest` runs Effect code
+  from a tool or step through your own runtime, with the HTTP request's span as its parent, and
+  interrupts it when Mastra's abort signal fires:
+
+  ```ts
+  const runtime = ManagedRuntime.make(AppServicesLive);
+
+  const findUser = createTool({
+    id: 'find-user',
+    inputSchema: z.object({ id: z.string() }),
+    execute: (input, context) => runInRequest(runtime, Users.find(input.id), context),
+  });
+  ```
+
+  For a tool an agent calls, that signal fires when the client leaves. A workflow step's belongs
+  to the run and fires only when the run is cancelled. The spans that code creates are made by the
+  runtime's own tracer, so give the runtime your tracer as well, or they are never exported. With
+  OpenTelemetry, `runtimeTracing` in [`examples/full-app`](examples/full-app/src/observability.ts)
+  does this.
+
+- **Mastra's own spans.** With Mastra's OpenTelemetry bridge, agent runs, model calls with token
+  counts and tool calls land in the same trace as the HTTP request, under its span.
+  [`examples/full-app`](examples/full-app) sets this up. It needs the tracer provider registered
+  globally, which Effect's `NodeSdk.layer` does not do by itself
+  ([mastra-ai/mastra#24950](https://github.com/mastra-ai/mastra/issues/24950)).
+
+## Install
+
+```bash
+pnpm add @guillem_puche/mastra-effect effect@rc @mastra/core zod
+```
+
+`effect@rc` matters: `effect@latest` is still v3, which has no `effect/unstable/http`, and the
+install will succeed and then fail at runtime. Requires Node >= 22.13, `effect@>=4.0.0-rc.117` and
+`@mastra/core@>=1.68.0`.
+
+To let Effect own the server, as below, add `@effect/platform-node` at the same `rc` version.
+
+## Quick start
+
+```ts
+import { createServer } from 'node:http';
+
+import { NodeHttpServer } from '@effect/platform-node';
+import { createMastraServer } from '@guillem_puche/mastra-effect';
+import { Effect, Layer } from 'effect';
+import { HttpServer } from 'effect/unstable/http';
+
+import { mastra } from './mastra';
+
+const { router } = await createMastraServer({ mastra });
+
+const server = HttpServer.serve()(router.asHttpEffect()).pipe(
+  Layer.provide(NodeHttpServer.layer(() => createServer(), { port: 3000 })),
+);
+
+await Effect.runPromise(Layer.launch(server));
+```
+
+Mastra now answers on `http://localhost:3000/api/*`.
+
+To add your own routes, or to mount something else like an auth handler, create the router yourself
+and hand the same instance to the adapter:
+
+```ts
+import { MastraServer, createRouter } from '@guillem_puche/mastra-effect';
+import { Effect } from 'effect';
+import { HttpServerResponse } from 'effect/unstable/http';
+
+const router = createRouter();
+
+await Effect.runPromise(router.add('GET', '/healthz', HttpServerResponse.text('ok')));
+
+const adapter = new MastraServer({ app: router, mastra, prefix: '/api' });
+await adapter.init();
+```
+
+If you would rather embed Mastra in an existing fetch-based setup than run an Effect server,
+`toWebHandler(router)` returns `{ handler, dispose }`. `handler(request)` answers a Web `Request` with
+a `Response`. Its optional second argument is an Effect `Context`, so give a framework that passes a
+second argument of its own — Next.js does — `request => handler(request)` instead. Effect logs every
+request it answers; `toWebHandler(router, { disableLogger: true })` turns that off. `dispose()`
+releases the handler, not Mastra.
+
+## Examples
+
+Each example is a small runnable app with its own README, and runs with no API keys, no database and
+no containers. CI runs every example's tests, so none of them can quietly stop working.
+
+| I want to… | Example | Open first |
+|---|---|---|
+| serve Mastra on Effect, and nothing else | [`minimal`](examples/minimal) | [`server.ts`](examples/minimal/src/server.ts) |
+| add Mastra next to my own Effect routes | [`alongside-your-routes`](examples/alongside-your-routes) | [`server.ts`](examples/alongside-your-routes/src/server.ts) |
+| keep Mastra behind one route, with middleware for Mastra only | [`mounted-as-one-route`](examples/mounted-as-one-route) | [`server.ts`](examples/mounted-as-one-route/src/server.ts) |
+| use Mastra from Bun, Deno, Workers or Next.js, with no Effect server | [`fetch-handler`](examples/fetch-handler) | [`handler.ts`](examples/fetch-handler/src/handler.ts) |
+| share one sign-in (Better Auth) between my app and Mastra | [`full-app`](examples/full-app) | [`auth.ts`](examples/full-app/src/auth.ts) |
+| serve Mastra's agents and tools over MCP | [`full-app`](examples/full-app) | [`mastra.ts`](examples/full-app/src/mastra.ts) |
+| export traces and logs with OpenTelemetry, locally or to a vendor | [`full-app`](examples/full-app) | [`observability.ts`](examples/full-app/src/observability.ts) |
+| show interactive API docs (Scalar) for Mastra's routes | [`full-app`](examples/full-app) | [`scalar.ts`](examples/full-app/src/scalar.ts) |
+
+```bash
+cd examples/minimal   # or any other
+pnpm test
+pnpm dev              # http://localhost:3000 — every example except fetch-handler, which has no server
+```
+
+### One router, or Mastra as one route?
+
+By default Mastra does not bring a router of its own: it adds each of its ~400 routes to *your*
+router, next to your routes, so one middleware stack covers everything. That is what Mastra's
+adapters for Hono, Express, Fastify and Koa do, and it is what
+[`alongside-your-routes`](examples/alongside-your-routes) shows.
+
+Effect can also keep Mastra behind a single route — its own router, forwarded from `/api/*` — so
+middleware and Mastra's request log cover Mastra alone. The trade-off: Mastra's custom API routes
+live outside `/api` and each needs a forward of its own. [`mounted-as-one-route`](examples/mounted-as-one-route)
+shows it and compares the two.
+
+## API
+
+| Export | Purpose |
+|---|---|
+| `createMastraServer(options)` | Builds a router, constructs the adapter, runs `init()`. Returns `{ router, adapter }` |
+| `createRouter(config?)` | An empty `HttpRouter` to hand to `new MastraServer({ app })`. Takes a partial `FindMyWay.RouterConfig` |
+| `MastraServer` | The adapter itself, for when you own the router and the lifecycle |
+| `toWebHandler(router, options?)` | `{ handler, dispose }` — a fetch handler over a populated router. `options.disableLogger` stops Effect logging each request |
+| `runInRequest(runtime, effect, context)` | Runs Effect code from a Mastra tool or workflow step: your runtime's services, the request's span as parent, Mastra's abort signal |
+| `requestSpan(requestContext)` | The HTTP request's Effect span, from a tool's or step's request context; `undefined` without a tracer |
+| `MastraRouteError` | What a route's server error (5xx) becomes in Effect's error channel. Answers with Mastra's own response |
+| `EffectRouter`, `EffectRequestContext`, `MastraServerOptions`, `CreateMastraServerOptions`, `ToolsInput` | Types |
+
+## Status
+
+Alpha. The route surface is verified against Mastra's published conformance suites
+([`@mastra/server-adapters-test-suite`](https://www.npmjs.com/package/@mastra/server-adapters-test-suite)),
+which iterate the live `SERVER_ROUTES` table rather than a hand-written list — so the check tracks
+Mastra's routes as they move rather than a snapshot of them.
+
+| Suite | Status |
+|---|---|
+| `createRouteAdapterTestSuite` | passing |
+| `createMCPRouteTestSuite` | passing |
+| `createBodyLimitTestSuite` | passing |
+| `createHttpLoggingTestSuite` | passing |
+| `createMultipartTestSuite` | passing |
+| `createMCPTransportTestSuite` | passing |
+
+CI runs them on Node 22.13 and 24 against the newest Mastra, and again against the oldest Mastra
+the package declares. MCP is tested with servers from both `@mastra/mcp` 1.x and 2.x. The adapter's own tests add what the suites
+do not reach: a disconnecting client cancelling Mastra's work, streamed answers, request bodies
+already read by middleware, cookies and session refresh. The examples exercise auth, OpenAPI, the
+docs page, OpenTelemetry export, both ways of attaching Mastra to a router and the fetch handler end
+to end.
+
+### Differences from the official adapters
+
+- **`server.middleware` and `mastra.setServerMiddleware()` are not run.** They take Hono middleware
+  (`(c, next) => …`), which only `@mastra/hono` can execute; Mastra logs a warning and skips them, as
+  it does under Express, Fastify and Koa. Add Effect middleware to the router instead
+  (`router.addGlobalMiddleware`).
+- **Cookies pass through Effect's cookie model.** Attributes it does not have — anything beyond
+  Domain, Path, Expires, Max-Age, HttpOnly, Secure, SameSite, Priority and Partitioned — are dropped,
+  and a cookie whose value cannot be sent is dropped with a warning instead of failing the response.
+- **A trailing slash still matches** (`/api/agents/`), as under `@mastra/elysia`; `@mastra/hono`
+  answers 404.
+
+## Effect version support
+
+Tracks the `rc` line, not the frozen `beta` line. Every API this adapter depends on is asserted at
+compile time in `src/effect-api-gate.ts`, so an incompatible Effect upgrade fails `tsc` instead of
+failing subtly at runtime.
+
+Two behaviours differ from what you might expect coming from the Effect beta or from stock
+`find-my-way`:
+
+- Effect vendors its own FindMyWay, which defaults `ignoreDuplicateSlashes` to **true**. This adapter
+  forces it off, so `/api//agents` 404s instead of being served as `/api/agents`.
+- Routes differing only in their path-parameter name at the same segment — Mastra has four such
+  pairs — register and dispatch correctly, binding the right name to each. The positional rewrite
+  that `@mastra/elysia` needs is unnecessary here.
+
+## License
+
+Apache-2.0 — matching Mastra, from whose in-tree adapters parts of this one are derived. See
+[NOTICE](NOTICE) for what was carried over and from where. Effect itself is MIT and is a peer
+dependency, not redistributed here.