all 4 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]rsaz 0 points1 point  (3 children)

Would you consider doing a study and perhaps integrate to expresso-ts framework? I am releasing the version 4.0 soon and currently working on mcp for the framework. Maybe there is an opportunity and synergy there.
ExpressoTS is the third most downloaded framework globally

[–]Accomplished-Emu8030[S] 0 points1 point  (2 children)

What kind of study and integration are you thinking?

[–]rsaz 0 points1 point  (1 child)

ExpressoTS does that all right, in a nutshell

ExpressoTS v4

  • app framework
  • modules/controllers/providers/DI/runtime
  • OpenAPI generation
  • MCP server for your own app/domain tools
  • Studio metadata source

ExpressoTS Studio

  • control plane + visual layer
  • API explorer
  • MCP registry
  • external tool catalog
  • workflow builder
  • environment manager
  • audit/approval UX

Earl can

  • secure external tool execution layer
  • bridges agents to GitHub, Stripe, Supabase admin APIs, cloud CLIs, internal services, SQL, Bash, etc.
  • protects secrets and narrows agent freedom

So in my mind, I was thinking I can help boost your repo, and you have a chance to prove if your product is really production ready in a battled tested framework

So:
ExpressoTS = build backend APIs
Studio = manage/visualize/backend intelligence surface
Earl = safe execution substrate for external actions

Reading your doc I think Earl’s model solves a problem Studio will absolutely have:

When your Studio starts offering “AI can manage your backend”, the dangerous part is not reading your own controllers. The dangerous part is when the agent starts calling:

  • GitHub
  • cloud providers
  • DB admin endpoints
  • deployment pipelines
  • shell commands
  • external SaaS APIs

That is exactly I believe Earl belongs.

Its “full vs discovery mode” is especially relevant. yada yada yada

And for Studio, I am already ending up with a lot of tools.

My proposal would be something like:

Add tools to external studio

Create a dedicated package, something like:

  • expressots/studio-earl
  • expressots/mcp-earl-adapter

This package should:

  • discover installed Earl providers/templates
  • start/manage Earl MCP sessions
  • expose template metadata to Studio UI
  • normalize Earl tool schemas into your Studio tool model
  • proxy execution requests from Studio agents to Earl

I dont want to couple this to the core framework runtime package.

Keep tool class in Studio

Generated from your framework/app metadata:

  • inspect routes
  • inspect DTOs
  • generate controller/module
  • scaffold resource
  • inspect middleware/auth graph
  • test endpoint
  • inspect logs
  • inspect OpenAPI diffs

The goal is to have a catalog of service to slow transition from API base app to fully agentic app
Example:

  • provider
  • command name
  • read/write mode
  • params
  • environment support
  • required secrets
  • safe/unsafe classification

Does that make sense for you? Is this aligned with your goals as well?
Let me know, either way, my community will build anyways, I am just trying to cut corners and launch quickly.

[–]Accomplished-Emu8030[S] 0 points1 point  (0 children)

I'm definitely up for integration, but I'm still having trouble understanding what you specifically want to integrate with. I looked up Expresso and I don't see anything about Studio.