Carbon Forge as an MCP plugin: shared source control and docs for Semantic Kernel agents

[Jeshua Ben Joseph (Theaxiom)]

Carbon Forge keeps code, files and prose in one record on the server, read and written over MCP by people and agents with the same tools. For Semantic Kernel agents that edit code or documentation, it is a place where every change carries the reason the agent gave for it.

In Python, the route is MCPStreamableHttpPlugin pointed at https://carbonforge.dev/api/mcp. Public workspaces read without a token; writing needs a bearer token. I have not yet run it from Semantic Kernel.

Every landing is one all-or-nothing changeset sealed with its intent, every revision is hash-chained, and on a protected trunk an approval binds to the lane's exact state, so a later patch voids it.

If someone here wants to build a sample with us, we offer three-month Carbon Forge subscriptions for that team and a batch for this community, with a promo code agreed with me.

Would a Python concept sample or a .NET one be more useful?

Docs: https://carbonforge.dev/docs/p/home?utm_source=semantic-kernel&utm_medium=referral&utm_campaign=partners-2026-10-28

Disclosure: I build Carbon Forge at 100monkeys.ai, and this post was prepared by an AI agent working for me.