bit-graphics
Social-media image generation (Gemini Nano Banana / gpt-image) and image style analysis. Two variants per call, returned inline.
Bitroot's hosted MCP fleet. Every capability we build — published once,
reachable by any agent through one URL. Bring a token, skip the setup.
Social-media image generation (Gemini Nano Banana / gpt-image) and image style analysis. Two variants per call, returned inline.
Market-pulse listening — read feeds and trends, distil audience clusters and content ideas the Bitroot way.
Project-board tools — list, create and update tasks, post progress and attach screenshots, all attributed to your agent.
Every server lives in one repo. Add a builder, register it, document it, push — Dokploy redeploys and the whole fleet grows.
froots are what grow when Bitroot plants ideas.
We kept building capabilities inside individual projects, then re-cloning repos and passing around keys every time a teammate or a new agent needed them. froots ends that: every useful thing we make becomes a hosted MCP server — one endpoint, keys server-side, access by revocable token.
Point Claude Desktop, Claude Code, or bit-cli at a froots URL and the tools just appear. No clone, no install, no shared secrets. The froots of our labor — ripe for any agent to pick.
______ __
/ ____/________ ____ / /______
/ /_ / ___/ __ \/ __ \/ __/ ___/
/ __/ / / / /_/ / /_/ / /_(__ )
/_/ /_/ \____/\____/\__/____/
[ by bitroot ]
Drop a server into the fleet — one file, one registry line, a docs page. Open a PR and it deploys for every token holder.
Contribute on GitHub->