Your content should not just be written with AI.
It should be visible to AI.
Forge gives every module /llms.txt, /llms-full.txt, and /aidoc by default.
A Go CMS framework built for you and AI. Zero dependencies. SEO, AI-indexing, Social sharing and content lifecycle.
Zero dependencies. No ambiguity.
https://github.com/forge-cms/forge
#Golang #MCP #AI #Framework #cms #EUtech
| github | https://github.com/forge-cms/forge |
| web | https://forge-cms.dev/ |
Your content should not just be written with AI.
It should be visible to AI.
Forge gives every module /llms.txt, /llms-full.txt, and /aidoc by default.
Your data, your jurisdiction.
Forge runs on your server, under your rules. No third-party services. No visitor tracking. No data leaving your infrastructure.
The story behind the name, the palette, and why we dropped the terminal aesthetic:
Forge module imports have moved.
Update your go.mod:
forge-cms.dev/forge
forge-cms.dev/forge-mcp
forge-cms.dev/forge-media
forge-cms.dev/forge-cli
Shipped: Go 1.26.2. Vanity import paths. And something visual coming soon.
Anthropic recommends rich tool semantics for MCP servers -- agents should know what fields mean without extra prompting.
Forge bakes this into the Go struct:
forge_description: "1-2 sentences used as meta description"
forge_format: "markdown"
These go into the MCP schema automatically. No extra system prompt needed.
https://forge-cms.dev/devlog/anthropic-mcp-production-servers
Anthropic just published the spec for production MCP servers.
Remote transport. Intent-grouped tools. Field semantics. Standardised auth.
Forge already does all of it -- before this article existed.
https://forge-cms.dev/devlog/anthropic-mcp-production-servers
https://claude.com/blog/building-agents-that-reach-production-systems-with-mcp