[FEATURE]: Support MCP-CLI for on-demand loading of MCP tools for reduced token consumption #7406

Activity

1. HyunggyuJang

   added

   discussionUsed for feature requests, proposals, ideas, etc. Open discussionUsed for feature requests, proposals, ideas, etc. Open discussion

   on Jan 9, 2026
2. github-actions

   assigned

   thdxr

   on Jan 9, 2026
3. github-actions commented on Jan 9, 2026

   

   github-actionsBot

   on Jan 9, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [FEATURE]: Filter which tools are loaded from MCP servers (includeTools/excludeTools) #7399: Filter which tools are loaded from MCP servers (includeTools/excludeTools) - proposes selective tool loading from MCPs
   • Reduce token overhead: Task tool injects all subagent descriptions into system prompt #7269: Reduce token overhead from Task tool - addresses token consumption from tool injection
   • Implement virtual tools feature to allow GitHub Copilot models to run with more than 128 tools #2513: Implement virtual tools feature for GitHub Copilot - similar concept of on-demand tool loading to work around tool limits

   These issues discuss complementary approaches to reduce token consumption and manage tool availability. Feel free to ignore if this request has a specific MCP-CLI focus that differs from these.
4. airtonix commented on Jan 12, 2026

   

   airtonix

   on Jan 12, 2026

   Contributor

   More actions

   or you could just use skills to do this?
5. HyunggyuJang commented on Jan 12, 2026

   

   HyunggyuJang

   on Jan 12, 2026

   Author

   More actions

   Indeed, MCP CLI is necessary to turn MCP servers into skills. Without MCP CLI, skills feature doesn't help since MCP server will consume the context on top of any skill instructions. Otherwise, we need to reverse engineer existing MCP servers to CLI tools, which can be avoided with MCP CLI.
6. thdxr commented on Mar 25, 2026

   

   thdxr

   on Mar 25, 2026

   Member

   More actions

   To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
7. thdxr

   removed

   discussionUsed for feature requests, proposals, ideas, etc. Open discussionUsed for feature requests, proposals, ideas, etc. Open discussion

   on May 3, 2026
8. rekram1-node

   closed this as not plannedon May 22, 2026