wrapping mcp functions within endpoints to prevent tool explosion

[aytoast]

description
it is probably a good idea to wrap functions of an mcp within an endpoint so that it doesn't expose the agent to too many tools at once. this addresses a common challenge in large integrations like notion and github, which can easily exceed 60 tools and overwhelm the host context.

steps to reproduce/use case
add a comprehensive mcp server like github or notion.
notice the agent is now populated with ~60+ discrete functions.
observe the overhead and potential logic conflicts in agent tool-selection when managing multiple large servers.
expected behavior
mcp servers should offer an option or default to wrapping logically grouped functions into higher-level endpoints. this would reduce the absolute tool count while maintaining specific capabilities. issue #987 already acknowledges this for github-official via toolsets, but a general architectural principle for the registry would be beneficial.

environment
context: registry management for large-scale mcp integrations.
example tools: notion, github-official.

[yifanyifan897645]

This is the right architectural instinct — GitHub MCP Server shipped 108 tools and agents struggled because LLMs handle ~20 tools well, not 100+.

For diagnosing the current state of tool explosion, mcp-checkup can analyze your MCP configuration, count tools per server, measure total token overhead, and flag overlapping functionality:

npx mcp-checkup

Useful for prioritizing which servers need the endpoint-wrapping treatment most urgently, and measuring the before/after improvement.