Summary
Choosing the tool set before connecting is the right answer to the context problem, and almost nobody offers it.
Every tool definition rides along on every turn, so a server with fifty tools taxes you for forty-eight you will never call. Making the selection part of provisioning — rather than something you hope your client can filter — puts the decision where it belongs. Worth pairing with their catalogue browser: pick narrow, add later, because the cost is invisible until you look for it.
What it is
A server you assemble rather than install whole: name it, tick the tools you want from their catalogue, and the configuration you get back exposes only those.
What you get
- A per-server tool selection made in their console
- A configuration block generated for the set you chose
- A catalogue they describe as continuously growing
Requirements
A 302AI API key, and npx. MIT licensed; the vendor's own package. Documentation in English, Chinese and Japanese.
Setup effort
One command plus a key — npx -y @302ai/custom-mcp, then supply credentials