[CHORE][DOCS]: Consistent "ContextForge" naming and "AI Gateway" positioning across project

[crivetimihai]

Overview

The project inconsistently refers to itself as "MCP Gateway", "ContextForge MCP Gateway", "MCP Context Forge", or just "ContextForge" depending on the file. The scope description also varies — some places narrowly describe it as a "gateway for MCP servers" when it actually supports MCP, A2A, REST, gRPC, and more.

This issue tracks making the naming and positioning consistent:

• Product name: ContextForge (not "MCP Gateway")
• Positioning: AI Gateway supporting MCP, A2A, REST, gRPC, and more
• Internal code (mcpgateway/, package name, imports): no change

---

Current State

A grep -ri "mcp gateway" across docs, config, and top-level files surfaces ~30+ inconsistencies. Key offenders:

File	What it says	What it should say
README.md:1	# MCP Gateway	# ContextForge
README.md:3	> Model Context Protocol gateway & proxy...	Broader AI Gateway description
README.md:~816	MCP Gateway can be deployed to...	ContextForge can be deployed to...
pyproject.toml:16	"A production-grade MCP Gateway & Proxy..."	AI Gateway + MCP, A2A, REST, gRPC
mcpgateway/main.py:8	MCP Gateway - Main FastAPI Application.	ContextForge - Main FastAPI Application.
mcpgateway/__init__.py:7	MCP Gateway - A flexible...	ContextForge - ...
docs/mkdocs.yml:7	site_description: "MCP Gateway Documentation"	"ContextForge Documentation"
docs/mkdocs.yml:72	cover_subtitle: MCP Gateway Documentation	ContextForge Documentation
docs/docs/index.md:1	# MCP Gateway	# ContextForge
docs/docs/overview/index.md:3	Welcome to the MCP Gateway documentation	Welcome to the ContextForge documentation
docs/docs/overview/index.md:9	## What is MCP Gateway?	## What is ContextForge?
Makefile:3	(An enterprise-ready Model Context Protocol Gateway)	(An enterprise-ready AI Gateway...)
Makefile:7	...for the MCP Gateway project	...for the ContextForge project
Makefile:26	--name "MCP Gateway"	--name "ContextForge"
.env.example:2	# MCP Gateway Configuration Example	# ContextForge Configuration Example
charts/mcp-stack/Chart.yaml	description: MCP Gateway application...	ContextForge application...
charts/mcp-stack/values.yaml	APP_NAME = "MCP_Gateway"	APP_NAME = "ContextForge"
llms/mcpgateway.md:1	MCP Gateway: Full Project Overview	ContextForge: Full Project Overview
AGENTS.md / CLAUDE.md:17	MCP Gateway (ContextForge) is a...	ContextForge is a production-grade AI gateway...

---

Proposed Implementation

1. Sweep all .md files in docs/, llms/, README.md, AGENTS.md, CLAUDE.md — replace "MCP Gateway" with "ContextForge" where it refers to the product name.
2. Update config/build files — pyproject.toml description, Makefile banners, .env.example header, mkdocs.yml metadata.
3. Update Helm chart metadata — Chart.yaml description, values.yaml APP_NAME.
4. Update Python docstrings in mcpgateway/main.py and mcpgateway/__init__.py.
5. Widen scope descriptions — anywhere the project is described, ensure it mentions being an AI Gateway supporting MCP, A2A, REST, gRPC, and more (not just "MCP servers").

Leave unchanged:

• Python module name mcpgateway/ and import paths
• PyPI package name mcp-contextforge-gateway
• Git repo name mcp-context-forge
• Database table names, internal variable names
• References to "MCP" when describing the protocol itself (not the product)

---

Verification

# Should return zero results for product-name references (protocol references are fine)
grep -ri "mcp gateway" docs/ README.md Makefile .env.example charts/ llms/ AGENTS.md CLAUDE.md \
  | grep -vi "protocol"

---

Acceptance Criteria

• All user-facing documentation uses "ContextForge" as the product name
• Key descriptions position it as an "AI Gateway" supporting MCP, A2A, REST, gRPC, and more
• No regressions in tests or builds

[crivetimihai]

See also: [CHORE][DOCS]: Consistent ContextForge logo and branding assets across project #2715