feat(patterns): add Gateway Pattern for multi-platform MCP aggregation - #379
Open
keewillidevnet wants to merge 2 commits into
Open
feat(patterns): add Gateway Pattern for multi-platform MCP aggregation#379keewillidevnet wants to merge 2 commits into
keewillidevnet wants to merge 2 commits into
Conversation
Add the Gateway Pattern to agentic_patterns, describing an architectural approach for aggregating multiple MCP servers behind a single entry point using AGNTCY components (Agent Directory, OASF, Identity, TBAC, SLIM, Observability). Includes centralized, edge-native, and hybrid topology variants with support for Cisco IOx, Dell TPCM/SONiC, and whitebox switches. Defines seven agent types that compose multi-platform workflows through the gateway. References MIGA MCP Gateway as a reference implementation. Follows up on agntcy/docs#392 per maintainer feedback to place pattern documentation in coffeeAGNTCY/agentic_patterns. Signed-off-by: keewillidevnet <keewillidevnet@users.noreply.github.com>
keewillidevnet
requested review from
Shridhar-2205,
codyhartsook,
shanchunyang0919 and
therealaditigupta
as code owners
February 13, 2026 22:38
Signed-off-by: Keenan W. <130465946+keewillidevnet@users.noreply.github.com>
Author
|
@jparello following up on agntcy/docs#392 — I moved the Gateway Pattern into agentic_patterns here as you suggested, and just pushed an update tightening the reference-implementation section so it matches the current MIGA repo. It's passing checks and cleanly mergeable against agentic-patterns. The doc covers centralized, edge-native (on-device MCP via IOx, Dell TPCM/SONiC, whitebox SONiC), and hybrid topologies. Whenever you or the team have a chance to review, I'd appreciate it. And per your note about bringing patterns into the demonstrations, I'm glad to contribute more and help wire these into coffeeAGNTCY whenever you want to start. |
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
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.
Add the Gateway Pattern to agentic_patterns, describing an architectural approach for aggregating multiple MCP servers behind a single entry point using AGNTCY components (Agent Directory, OASF, Identity, TBAC, SLIM, Observability).
Includes centralized, edge-native, and hybrid topology variants with support for Cisco IOx, Dell TPCM/SONiC, and whitebox switches. Defines seven agent types that compose multi-platform workflows through the gateway. References MIGA MCP Gateway as a reference implementation.
Follows up on agntcy/docs#392 per maintainer feedback to place pattern documentation in coffeeAGNTCY/agentic_patterns.
Description
Please provide a meaningful description of what this change will do, or is for.
Bonus points for including links to related issues, other PRs, or technical
references.
Note that by not including a description, you are asking reviewers to do extra
work to understand the context of this change, which may lead to your PR taking
much longer to review, or result in it not being reviewed at all.
Issue Link
Link the primary issue in the PR description using
#(e.g.Fixes #123). This enables two‑way linking.Type of Change
Checklist