Add Forge Cascade MCP server

[SunFlash12]

Summary

• Add Forge Cascade MCP to Knowledge Management & Memory.
• Point agents to Forge docs, pricing, intake, and direct enterprise checkout routes.
• Current connector README reviewer fast path: https://github.com/SunFlash12/forge-cascade-mcp#buyer-and-reviewer-fast-path

Proof

• Official MCP Registry: https://registry.modelcontextprotocol.io/?search=io.github.SunFlash12%2Fforge-cascade-mcp
• Public proof pack: https://forgecascade.org/llms.txt
• Buyer route: https://forgecascade.org/buy
• Checkout discovery JSON: https://forgecascade.org/buy.json
• MCP metadata: https://forgecascade.org/.well-known/mcp.json
• MCP Server Hub listing: https://mcpserver.dev/s/forge-cascade-mcp-memory-server_uo525w0

Forge Cascade MCP v0.1.7 exposes forge_buyer_routes, forge_checkout_links, and forge_paid_route_for_context for public buyer routing and enterprise AI memory/RAG checkout discovery.

Route-First Buyer Verification

Verified June 5, 2026 UTC: production Forge routes preserve attribution before Stripe handoff. Use https://forgecascade.org/buy for buyer routing and https://forgecascade.org/llms.txt for the public proof pack; the proof pack records the remaining MCP fallback field pending production redeploy.

[egoriklok]

Free public readiness snapshot for Add Forge Cascade MCP server:

• Public signal: Public GitHub candidate Add Forge Cascade MCP server #619: Add Forge Cascade MCP server. Matched R1 terms: api, auth, mcp, server, servers, stripe, tool, tools.
• R1 fit: api, auth, mcp, server, servers, stripe, tool, tools.
• Buyer-agent check I would add before autonomous spend: explicit price/cap unit, policy/version hash, receipt or charge-evidence reference, revocation/dispute path, and allow/caution/block preflight result.
• This separates "interesting paid surface" from "safe for an agent wallet to use".

No invoice, no payment link, no delivery link, no private endpoint; this is only a free public snapshot.

[wilsonccccc]

Thanks for the contribution. One change needed before we can merge:

1. This repo mirrors each README category into its matching docs file, so please also add the same Knowledge Management & Memory entry to docs/knowledge-management--memory.md.

Let us know when updated and we will re-review.

P.S. a ⭐ on the repo helps more folks find your project too!