01 · Developer platform · AI tooling
aidevkit
A package manager and public hub for AI agents, skills and MCP servers: one command installs a building block into Claude Code, GitHub Copilot or Codex, and one command takes it back out.
the problem.
Every AI coding tool keeps its agents, skills and MCP configuration in its own folders and formats. Reusing one across tools meant copying files by hand, with no view of what a piece could access and no clean way to undo it.
what i built.
- The aidevkit CLI (aidevkit-cli on npm): it resolves a listing, shows the permissions it asks for, writes the configuration each tool expects and records a rollback point.
- Provider adapters for GitHub Copilot, Claude Code and Codex behind one plan, apply, backup and rollback engine, with a lockfile and version locking.
- A NestJS registry API on Postgres (PGlite in development) with accounts, organisations, policies and usage events.
- A Next.js and Tailwind discovery site with 30,000+ real listings imported from the official MCP Registry and permissively licensed collections.
- An artifact schema with semver, validation, content hashing and a security scanner that rejects risky content.
how it flows.
- aidevkit CLIsearch, install
- Caddy/v1 to the API
- Registry APINestJS + Postgres
- Provider adapterCopilot, Claude Code, Codex
- Config + rollback point
decisions that mattered.
Real data, never invented
Every listing is imported from a public source with its license, and install counts start at zero. Collections come in only when their content is permissively licensed, and imported listings are labelled as not reviewed.
Skip, never guess
MCP servers whose connection needs templated URLs, headers or user-supplied arguments are skipped instead of guessed. Placeholders are dropped and each publisher is capped, which took about 38.7k registry entries down to about 21k listings.
Every install is reversible
Each install creates a rollback point, major versions are never applied silently, and a lockfile restores a setup on another machine.
Usable by agents, not only people
JSON output and a stable exit-code contract, checked by an end-to-end test that drives the built binary the way a coding agent would: search, inspect, install.
One origin in production
Postgres, the API and the site run in Docker Compose on a VPS behind Caddy, which sends /v1 to the API and everything else to the site, so the website and the CLI share one origin.
built with.
- TypeScript
- Node.js
- NestJS
- Next.js
- Tailwind
- Postgres
- PGlite
- Zod
- Vitest
- Docker
- Caddy
the result.
Live at aidevkit.in since October 2026 with 30,000+ building blocks, MIT licensed and open source.