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:

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