Carbon Forge with McpToolset: a remote record ADK agents read and write

[Theaxiom]

Carbon Forge is a remote MCP server for source control and shared docs. Code, files and prose live in one record on the server, and people and agents read and write it through the same tools.

The route from ADK is McpToolset with StreamableHTTPConnectionParams and the URL https://carbonforge.dev/api/mcp. Without a token it reads public workspaces; writing needs a bearer token, and a token can be held to a preset such as SCM reader, which writes nothing. That suits a read-only agent beside a writing one. I have not yet run it from ADK; an example would settle it.

For multi-agent ADK setups: each agent opens a lane over the same trunk instead of cloning, a patch that no longer applies comes back as a named conflict, and Carbon Forge never merges text by itself.

We would like to publish an ADK sample with someone here. For that team there are three-month Carbon Forge subscriptions, and a batch for this community, with a promo code agreed with me.

Is a read-only agent paired with a writing agent the sample people here would want first?

Docs: https://carbonforge.dev/docs/p/home?utm_source=adk&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.