About devpick
devpick is a browser-based collection of developer utilities, including 43 local tools intended for AI agents. It suits developers who want client-side processing without accounts or a backend; the project is an open-source static site.
Key features
- 01Provides 118 browser-based developer tools
- 02Offers 43 tools for AI agents
- 03Processes inputs entirely client-side
- 04Builds as a static site for self-hosting
Use cases
- 01Formatting or validating JSON in a browser
- 02Generating or auditing a .gitignore
- 03Running developer utilities without sending inputs to a backend
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
43Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| files | array | Yes | Array of absolute paths to PDF files to merge |
| output | string | Yes | Absolute path for the merged output PDF |
Details
From the project READMEdevpick.sh
Developer tools that don't suck.
118 free developer tools. Everything runs 100% in your browser — no accounts, no tracking, your input never leaves your machine. Open source under MIT.
Tools
| Tool | Route | Category |
|---|---|---|
| JSON Formatter | /json-formatter | Format & Validate |
| Base64 | /base64 | Encode & Decode |
| URL Encoder | /url-encoder | Encode & Decode |
| JWT Decoder | /jwt-decoder | Encode & Decode |
| Timestamp | /unix-timestamp-converter | Convert |
| Hash Generator | /hash-generator | Generate |
| UUID Generator | /uuid-generator | Generate |
| .gitignore Generator & Auditor | /gitignore-generator | Generate & Audit |
Dev
npm run dev # start dev server
npm run build # production build (static export to /out)
Deploy (Cloudflare Pages)
npm run build
# Upload /out folder to Cloudflare Pages
Build output: ./out (static HTML/CSS/JS)
Stack
- Next.js 16 (App Router, static export)
- Tailwind CSS v4
- lucide-react (icons)
- next/font (Inter + JetBrains Mono)
- next-sitemap
Privacy
Tool inputs are processed client-side and are never sent to DevPick. Privacy-safe aggregate analytics measure page and tool outcomes without collecting inputs, filenames, or generated output.
Contributing
Each tool is a self-contained route under app/<tool-name>/page.tsx — copy an existing one as a starting point. PRs welcome: new tools, better UX, bug fixes.
npm run dev # start dev server
npm run lint # eslint
npm run build # production build (static export to /out)
Self-host
There is no backend — the build produces a plain out/ directory of static files. Serve it with anything:
docker compose up -d # builds and serves on :8080
# or
npx serve out # zero-config static server
# or
docker run -d -p 8080:80 -v ./out:/usr/share/nginx/html nginx:alpine
No database, no env vars, no API keys. Every tool runs 100% client-side.
Writing
- I ship 118 dev tools as a single static export: here's the setup — how the repo's conventions, build-time SEO audit, and privacy-safe analytics work.
License
MIT — see LICENSE. Fork it, self-host it, use it commercially. If you build something cool with it, a link back is appreciated but not required.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.