[Docs]: Provide an example for a custom adapter

[filip-dupanovic-deel]

What is the documentation issue?

There's currently examples on how to use stock adapters and I would like if we can provide an example for a custom adapter.

Is there any context that might help us understand?

I'm trying to do some dynamic tool and resource registration by examining the OpenAPI schema of my API and using AI to fill in the blanks and I'm not entirely sure how to readily do this.

I see that the adapters need to be a string, so think this might require using webpack to create and resolve some modules, or the config and API for adapters might need some more internals being surfaced.

[valebearzotti]

Hey @filip-dupanovic-deel !

Currently, custom adapters cannot be built from scratch with xmcp modules or anything like it, but instead use the provided ones. We do encourage users to contribute on adding the ones they believe fit best (e.g. for other frameworks).

We do not support dynamic tool discovery just yet but would be a great addition in the short term. But this should be done in the core level of the framework, not strictly tied to a specific adapter. Should be something you can toggle on/off or chain as you wish.

I see that the adapters need to be a string

Yup, you cannot plug any more configs in runtime.

the config and API for adapters might need some more internals being surfaced

Do you mean exporting modules for constructing your own? I'd explore more of this take cause it sort of conflicts with DX. I'd like to keep out-of-the-box options. Learning to construct one of your own requires a learning curve many users don't want to go through.

[langri-sha]

Thanks @valebearzotti! I guess we can close this issue then.

So for, say, like loading tools dynamically, would it be possible for the config to provide a callback to modify the server? I guess that would work nicely and wouldn't be tied to an adapter.

Maybe it wouldn't work for everyone, someone would want truly dynamic tooling, I'm just interested more at when server instances get initialized that I add a few more that aren't phrased as TS modules on the tools path.