Forge CMS

@forge_cms
6 Followers
3 Following
46 Posts

A Go CMS framework built for you and AI. Zero dependencies. SEO, AI-indexing, Social sharing and content lifecycle.

Zero dependencies. No ambiguity.

https://forge-cms.dev/

https://github.com/forge-cms/forge

#Golang #MCP #AI #Framework #cms #EUtech

githubhttps://github.com/forge-cms/forge
webhttps://forge-cms.dev/
Forge now fires outbound webhooks on content lifecycle events: publish, update, archive.
HMAC-signed, async delivery with exponential backoff and a circuit breaker per endpoint. MCP clients get push notifications. No polling.
#golang #mcp #selfhosting
Forge turns content changes into automation triggers. Connect Zapier, Make, or n8n with no code. Point it at your own backend. Let AI agents subscribe via MCP and react in real time.
One infrastructure. Three levels of automation.
https://forge-cms.dev/solved/automation-unlocked
#MCP #AIagents #nocode
Automation unlocked — Forge

Notify your tools, trigger your pipelines, or orchestrate a fleet of agents. From the moment content is published.

The story behind the name, the palette, and why we dropped the terminal aesthetic:

https://forge-cms.dev/devlog/iron-and-ember

#design #brand #opensource

Iron & Ember — Forge

A name should do work. Iron & Ember does three things at once. Iron is structural - durable, compiled, the material you build things to last from. Ember is…

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

#golang #forge #opensource

Shipped: Go 1.26.2. Vanity import paths. And something visual coming soon.

#golang #opensource #buildinpublic

@the_moep With all respect: We post maybe once every week in average. Personally. How can we improve?

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

#ai #selfhosting #eutech #mcp #golang

Anthropic described the right way to build MCP servers. Here's how Forge got there first.

Anthropic published [Building Agents That Reach Production Systems with MCP](https://claude.com/blog/building-agents-that-reach-production-systems-with-mcp)…

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

#ai #selfhosting #eutech #mcp #golang

Anthropic described the right way to build MCP servers. Here's how Forge got there first.

Anthropic published [Building Agents That Reach Production Systems with MCP](https://claude.com/blog/building-agents-that-reach-production-systems-with-mcp)…

Ten years ago: Should we add a mobile app?
Today: Should we add an AI agent?

The answer is the same. It depends on your architecture.

#AI #MCP #AIagents #webdev

SQL reserved keywords, health endpoint gaps, missing absolute URLs.
Small things - but each one is a gap between technically correct and actually works.

-> forge-cms.dev/devlog/patch-sprint-absurl-sql-quoting-health-improvements-and-a-proper-404

#golang #go #devtools #opensource