@gram-ai/[email protected]

@gram-ai/[email protected]

@gram-ai/[email protected]

Minor Changes

• 3fc0efc: allow for defining resources in mcp builds of gram functions
• add1481: Removed the per-tool config for declaring environment variables and instead opts
  for updating the Gram class to optionally accept an input environment and an
  associated zod schema for it. When a schema is defined, the code benefits from
  strict types and transforms when accessing environment variables via the tool
  context.

@gram-ai/[email protected]

Minor Changes

• 24118c5: Updated the Gram Functions framework template to include an MCP server for local
  development that wraps a Gram instance. This will provide developers a better
  feedback loop when developing tools before deploying them to Gram.

@gram-ai/[email protected]

@gram-ai/[email protected]

@gram-ai/[email protected]

Patch Changes

• a609f61: Added an "engines" field to the package.json files of the @gram-ai/functions
  requiring Node.js version 22.18.0 or higher. This ensures that we are in a
  runtime that supports import assertions and native support for running
  TypeScript files without experimental flags.

@gram-ai/[email protected]

Patch Changes

• cd9df97: Added the missing 'zx' dependency to the Gram TS SDK's package.json. It is
  needed for the build process.

@gram-ai/[email protected]

@gram-ai/[email protected]

@gram-ai/[email protected]

@gram-ai/[email protected]

[email protected]

Patch Changes

• 3c00725: Set of improvements for functions onboarding UX, including better support for mixed OpenAPI / Functions projects
• 99ef7d6: reinstroduced oauth protected resource, the way we are exposing this is generally correct even though many clients don't really process it yet
• 1a46e29: Allows MCP to work in browser based MCP inspector which was the original intention
• 6a2eecf: Sets up the ability to track gram functions memory and cpu usage per tool call coming from the function runner
• 12fef9e: Prevent nil pointer dereference panic during server and worker shutdown. This
  was happening because the Gram Functions orchestrator was retuning nil shutdown
  functions at various code paths.

[email protected]

Patch Changes

• 6a2eecf: Sets up the ability to track gram functions memory and cpu usage per tool call coming from the function runner