Skip to content

Proposed README edits - #18

Open
a-effort wants to merge 2 commits into
mainfrom
readme/clarify-contextforge-dev-step
Open

Proposed README edits#18
a-effort wants to merge 2 commits into
mainfrom
readme/clarify-contextforge-dev-step

Conversation

@a-effort

@a-effort a-effort commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Changes proposed:

  • Clarify that starting mcp-context-forge is a separate repo/process (not a command in this repo), and name make dev and its default port (:8000).
  • Clarify the FASTAPI_URL guidance: .env.example's 4444 default is mcp-context-forge's production default (make serve), not make dev's :8000. Following the doc literally against a make dev instance pointed the BFF at the wrong port.
  • Disambiguate mcp-context-forge (upstream gateway) from contextforge-web-ui (this repo) throughout. The similar names made several "ContextForge" / "this repo" references ambiguous about which project was meant.
  • Replaced em dashes.

@a-effort
a-effort marked this pull request as ready for review August 12, 2026 19:44
@a-effort
a-effort force-pushed the readme/clarify-contextforge-dev-step branch from eebd633 to d3583aa Compare August 13, 2026 00:29

@marekdano marekdano left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@a-effort - thanks for improving README!

I have two suggestions below

Comment thread README.md Outdated
Comment thread README.md Outdated

@gcgoncalves gcgoncalves left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The current version uses ContextForge, and the proposed mcp-context-forge. Both here are old terms, we're trying to distance away from MCP - as the gateway is broader in scope. Let's use just Context Forge.

Refer to the backing service as the ContextForge API rather than "the
gateway", "ContextForge MCP Gateway", or "mcp-context-forge". "Gateway" is
ambiguous here: it is also a domain entity (GatewayCreate/GatewayRead,
/v1/gateways, Gateways.tsx), so "point the BFF at the gateway" read as if a
gateway had to be created first. The repo slug is now confined to links and
clone paths.

Add a component table up front so the body can use short forms, and lead
with "AI gateway" as category framing rather than a referring term.

Also fix two leftovers from when this lived inside mcp-context-forge: CI
workflow links pointed at ../.github/, and the structure tree was rooted at
client/.

Signed-off-by: Anna Effort <anna.effort@ibm.com>
@a-effort
a-effort force-pushed the readme/clarify-contextforge-dev-step branch from 914d4a2 to 8b32b7f Compare August 19, 2026 00:56
Use colons or semicolons for label separators and clause joins instead of
em dashes and hyphens, consistently across the definition lists.

Signed-off-by: Anna Effort <anna.effort@ibm.com>
@a-effort

Copy link
Copy Markdown
Contributor Author

Heads up that I rebased onto current main, so both inline comments may show as outdated. What changed:

  • Rebased over feat: UI/BFF docker + compose stack with Redis  #30, which renamed FASTAPI_URL to CONTEXTFORGE_URL, moved .env to the repo root, and changed the default port. The README reflects all of that now.
  • Per @gcgoncalves's point about distancing from MCP: the backing service is now "the ContextForge API" throughout, rather than "the gateway" or "mcp-context-forge". "Gateway" was doubly ambiguous, since it's also a domain entity (/v1/gateways, Gateways.tsx), so "point the BFF at the gateway" could read as if you had to create one first. "AI gateway" now leads the intro as category framing, where nothing collides with it.
  • Fixed two leftovers from when this lived inside mcp-context-forge: the CI workflow links pointed at ../.github/, and the structure tree was rooted at client/.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants