Further iteration of the tool typing

[domarmstrong]

Goal

Make the api a bit nicer for defining type safe tools and resources.

With this change, the client classes have factory function that allow you to Client.createTool(...) Client.createResource(...)`.

Design

Make Client an abstract class and add factory functions to the base class. This allows us to use type inference without any explicit typing.

BugsnagClient.createTool({ ... }, async ({ client <- instance of BugsnagClient, args <- inferred from config }))

One thing required to be able to use this though is you need to use dynamic imports in the clients register functions. If you tried to do a static import of the tool files at the top of the client file the client class would not have been created yet and be undefined.

Changeset

Refactoring

Testing

[domarmstrong]

I stuck with the name args as that is in the mcp types and most other clients are using 'args'

[domarmstrong]

could still use named exports, but consistently using default makes the imports a bit more straightforward.

[domarmstrong]

With the current implementation, you have to also manually type any additional arguments to the handler factory. With this change you don't need any explicit typing or extra function nesting.