If you work with AI coding tools like Claude Code, Cursor, or Codex, you know the pain: every new project means hunting down configs, re-adding MCP servers, copying prompts, and hoping nothing breaks. Caliber fixes that with one command.
Caliber continuously syncs your AI setups, generates optimized agent skills, MCPs and config files, and keeps everything in one place so your whole team starts fast and stays consistent.
We are building this in the open and we want the community to shape what comes next. Here is what is on our roadmap right now.
1. MCP server discovery, sync, and installation
Right now, MCP server configs live in scattered files across your machine. Caliber will scan your existing tool configs (Cursor, Claude, Codex), store them centrally, and automatically install them for every developer joining a project. No more "it works on my machine" for AI setups. Secrets stay out of git, transport support covers both HTTP and stdio servers, and the whole thing runs in under 30 seconds on a fresh machine.
2. SkillBench: a community skill marketplace built into the CLI
Think npm, but for AI agent skills. With SkillBench you will be able to run caliber skills search to find community-built skills by framework or use case, install them with one command, and publish your own. Skills are ranked by stack compatibility and community usage, and the registry follows the OpenSkills format so they work across tools. A developer should be able to find and install a relevant skill in under 10 seconds.
3. Show instant value: tokens saved, time saved, errors prevented
One of the hardest parts of adopting any new tool is justifying it to your team or yourself. After you run caliber init or caliber score, Caliber will immediately show you the tangible impact: estimated tokens saved per session, developer time recovered from pre-configured commands, and errors caught from wrong file paths or hallucinated configs. No setup required to see the ROI.
What do you think is missing?
This is the part where we genuinely want your help. We are building Caliber for developers who use AI tools every day and we know there are pain points we have not thought of yet.
Drop a comment below with what you would add to this roadmap, what you wish existed in the AI tooling space, or just tell us if any of these features would actually change your workflow. You can also browse the full public roadmap and comment directly on the issues on GitHub: https://github.com/caliber-ai-org/ai-setup
If you want to follow along, contribute, or just lurk, join the conversation on r/aisetups on Reddit. All feedback shapes what gets built next.
Top comments (0)