feat(blog): add canonical "What is an MCP gateway?" article (draft)#11
Merged
feat(blog): add canonical "What is an MCP gateway?" article (draft)#11
Conversation
First piece of the audit's category-creation content strategy (Phase 2). Draft is ~2000 words, targeting the "MCP gateway" search term and anchoring SEO for every comparison piece that follows. Structure: - Hook and lede - Quick MCP refresher (tools, JSON-RPC, transports) - Why every team writing their own MCP server re-creates 2010s API sprawl - The MCP gateway as the obvious next step - Four jobs of an MCP gateway: tool exposure, governance, observability, AI-specific middleware - MCP gateway vs AI gateway vs API gateway disambiguation - Why spec-first matters - Checklist for 2026 buyers - Soft Barbacane mention at the end linking to /mcp/ Saved as draft: true; flip to false in a follow-up commit to publish (same pattern as the Strangler Fig article).
…ility Two passages drifted from reality once ai-proxy + the AI governance middleware suite were verified: 1. The "MCP gateway vs AI gateway vs API gateway" section claimed the three are "not the same box". They are three categories, but a single well-architected gateway (dispatcher + middleware composition) can span all three. Reworded to clarify that the architecture choice is orthogonal to the category distinction. 2. The closing Barbacane mention positioned Barbacane only as an MCP gateway, which undersells actual capability. Updated to mention all three layers: API gateway, outbound AI gateway (ai-proxy), and MCP gateway, composed from the same primitives. Claims verified against: - docs.barbacane.dev/guide/dispatchers.html (ai-proxy) - adr/0024-ai-gateway-plugin.md (positioning) - barbacane-dev/barbacane#67 (AI governance middleware suite)
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.
Summary
First of the audit's category-creation content strategy (Audit §9 Phase 2). Pulled forward from Phase 2 because it anchors SEO for every comparison piece that follows and because nobody is using the phrase "MCP gateway" yet - first mover in naming owns the category (Audit §6.2 #9).
~2000 words, targets the search term "MCP gateway", soft-CTA to /mcp/ at the end.
Structure
Notes
draft: true. Merging this PR does not publish the article; a follow-up commit flips the flag (same pattern as the Strangler Fig article)./mcp/, which ships in feat(site): audience nav, /mcp + /platform pages, AI cards in feature grid #10. Land feat(site): audience nav, /mcp + /platform pages, AI cards in feature grid #10 first or accept a temporary broken link while this article is still a draft.Test plan
npm run buildpasses locally