You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 6, 2026. It is now read-only.
MCP servers expose a lot of things that would be helpful to get from the hook as well. It would be great to just retrieve anything that the server can provide so the consumers of this hook can do what they want with it.
Maybe the next generation would put the tools in this server object as well:
const{server: { tools }}=useMcp("...");// And expandconst{server: { tools, ressources }}=useMcp("...");// Or flatten it out, but this mixes the result of the server with the // other meta arguments such as state, retry, etc., maybe not the clearest designconst{ tools, ressources }=useMcp("...");
MCP servers expose a lot of things that would be helpful to get from the hook as well. It would be great to just retrieve anything that the server can provide so the consumers of this hook can do what they want with it.
I would assume something like this:
Maybe the next generation would put the tools in this server object as well: