TypeScript capabilities
Define product and business actions in code, then validate locally.
Developer implementation
Define the tools and experiences your workflow needs. Noodle Seed provides the runtime and operating foundation, and our team can help you integrate, validate and launch it.
Technical approach
Software companies and enterprise teams can use the same public TypeScript authoring path. Our team works with yours on the integration and operating model.
Define product and business actions in code, then validate locally.
Carry user and tenant context into the experience while keeping your APIs authoritative.
Evaluate identity, credentials, permissions, evidence and release requirements.
Embed an assistant that understands the screen, acts for the signed-in user, and follows your existing permissions. Your product stays in control.
import { createAssistantSessionHandler } from "@noodleseed/assistant/server";
import { authenticateAssistantRequest } from "../../../../lib/noodle-assistant-auth";
// Generated by noodle assistant embed; adapt the verified identity seam.
export const POST = createAssistantSessionHandler({
serviceUrl: process.env.NOODLE_SERVICE_URL,
clientId: process.env.NOODLE_ASSISTANT_CLIENT_ID,
clientSecret: process.env.NOODLE_ASSISTANT_CLIENT_SECRET,
origin: process.env.PUBLIC_APP_ORIGIN,
authenticate: authenticateAssistantRequest,
});import { NoodleAssistant } from "@noodleseed/assistant/react";
// Use the signed-in user/tenant key to reset browser state on account changes.
<NoodleAssistant key={principalKey} sessionEndpoint="/api/assistant/session" />tool("current_workspace", {
contextProvider: true,
input: z.object({}),
output: z.object({
workspaceId: z.string(),
plan: z.string(),
openProjects: z.number(),
}),
annotations: annotations.readOnly(),
fulfil({ user }) {
return loadWorkspaceFor(user.subject);
},
});
// Every tool in this turn receives the same snapshot.
const workspace = context.ambient;Evaluate the boundary category by category, then inspect the host and security evidence behind it.
| Capability | DIY SDK | MCP host | Connector gateway | Noodle Seed |
|---|---|---|---|---|
| Product model | Imperative handlers | Bring a server | Connector configuration | One compiled product definition |
| Local proof | Build it | Varies | Varies | Validate and test locally |
| Generated product surfaces | Build each surface | Hosted endpoint | Connector tools | MCP + Apps + operations |
| Customer identity and tenancy | Build it | Varies | Agent-side | Managed boundary |
| Per-tool authorization | Build it | Varies | Agent-side | Scopes and roles |
| Operator model | Build it | Deployment settings | Agent-side | Org, app, environment, version |
| Operations and evidence | Build it | Hosting metrics | Connector logs | Managed boundary |
Protocol compatibility begins with the same product definition. Rich host presentation is verified separately, because every client evolves on its own schedule.
Host validation continues
Tokens are validated for the exact MCP resource and configured audience.
Verified identity selects the customer boundary before connector execution.
Discovery and invocation enforce the same per-tool authorization rule.
Validated identity is exchanged for a narrow downstream credential.
Connector secrets stay out of source, agent context, widgets, and runtime evidence.
Connector egress is constrained to declared origins and routing policy.
Operational evidence excludes request bodies, tokens, secrets, and nested values.
Start with one useful result
We can define the experience, connect the relevant systems and validate it with your team.