feat(mcp): expose MCP servers as standalone toolsets#1907
Merged
Conversation
Each configured MCP server now registers as its own toolset in TOOLSETS
(e.g. TOOLSETS['github'] = {tools: ['mcp_github_list_files', ...]}),
making raw server names resolvable in platform_toolsets overrides.
Previously MCP tools were only injected into hermes-* umbrella toolsets,
so gateway sessions using raw toolset names like ['terminal', 'github']
in platform_toolsets couldn't resolve MCP tools.
Skips server names that collide with built-in toolsets. Also handles
idempotent reloads (syncs toolsets even when no new servers connect).
Inspired by PR #1876 by @kshitijk4poor.
Adds 2 tests (standalone toolset creation + built-in collision guard).
This was referenced Mar 24, 2026
angelburgosrosado
pushed a commit
to angelburgosrosado/hermes-agent
that referenced
this pull request
Apr 27, 2026
…b29f73b2 feat(mcp): expose MCP servers as standalone toolsets
02356abc
pushed a commit
to 02356abc/hermes-agent
that referenced
this pull request
May 14, 2026
…b29f73b2 feat(mcp): expose MCP servers as standalone toolsets
olympus-terminal
pushed a commit
to olympus-terminal/hermes-agent
that referenced
this pull request
May 16, 2026
…b29f73b2 feat(mcp): expose MCP servers as standalone toolsets
gweeteve
pushed a commit
to gweeteve/hermes-agent
that referenced
this pull request
Jun 2, 2026
…b29f73b2 feat(mcp): expose MCP servers as standalone toolsets
Egavasyug
pushed a commit
to Egavasyug/hermes-agent
that referenced
this pull request
Jun 10, 2026
…b29f73b2 feat(mcp): expose MCP servers as standalone toolsets
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Each configured MCP server now registers as its own toolset in
TOOLSETS(e.g.TOOLSETS['github'] = {tools: ['mcp_github_list_files', ...]}), making raw server names resolvable inplatform_toolsetsoverrides.Problem: Gateway sessions using raw toolset names like
['terminal', 'file', 'github']inplatform_toolsets.telegramcouldn't resolve MCP tools because they were only injected intohermes-*umbrella toolsets.Solution:
_sync_mcp_toolsets()creates a standalone toolset for each MCP server name, plus continues injecting intohermes-*sets for the default path. Skips server names that collide with built-in toolsets.Salvaged from PR #1876 by @kshitijk4poor (MCP toolset feature only — unrelated refactoring dropped).
Tests
2 new tests (standalone toolset creation + built-in collision guard). All 140 MCP tests pass.