io.github.kimbobmarley03/devpick
43 local developer tools for AI agents: PDF, subnet, regex, JSON, conversion, and more.
devpick.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.
Installation
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @devpick/mcp-serverSet up in your AI client
Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-kimbobmarley03-devpick": {
"command": "npx",
"args": [
"-y",
"@devpick/mcp-server"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencePackage
@devpick/mcp-servernpmCompatible MCP Clients
io.github.kimbobmarley03/devpick works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
- Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect. - Cursor
~/.cursor/mcp.jsonRestart Cursor for changes to take effect. - VS Code
.vscode/mcp.jsonReload VS Code window for changes to take effect. - Windsurf
~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect. - Claude Code
.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.