Devpick

io.github.kimbobmarley03Published by GitHub account kimbobmarley03v1.0.1Updated Oct 24, 2026

43 local developer tools for AI agents: PDF, subnet, regex, JSON, conversion, and more.

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: io.github.kimbobmarley03/devpick
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account kimbobmarley03 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.kimbobmarley03%2Fdevpick.svg)](https://sourceweft.com/mcp/io.github.kimbobmarley03%2Fdevpick?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Devpick is a local MCP server that gives AI assistants 43 offline developer utilities such as JSON formatting, encoding, hashing, UUIDs and subnet calculations.

What you can do: Format and validate structured text such as JSON and .gitignore files, including auditing or generating a monorepo .gitignore. Encode and decode data with Base64, URL encoding and JWT decoding. Convert values such as Unix timestamps. Generate hashes and UUIDs. Work with other local utilities such as PDF and subnet tools. The README states tool inputs are processed client-side and never sent to DevPick.
When to use it: Useful when an assistant needs quick, self-contained developer utilities during coding or debugging, such as formatting JSON, decoding a JWT, generating a UUID or hash, or checking a .gitignore, without sending data to an external service.
Requirements: Runs as a local process over stdio, installed from the npm package @devpick/mcp-server, so Node.js and npm are needed. No accounts, API keys, environment variables or headers are declared, and the README states there is no backend, database or env vars.

Before you install

The README says inputs are processed client-side and not sent to DevPick, but it also mentions privacy-safe aggregate analytics on the web tools; verify behavior for the MCP package before feeding it sensitive data. Decoding JWTs or hashing secrets means those values pass through the tool, so treat outputs accordingly.

Installation

In SourceWeft

Open Devpick in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

devpick.sh

[License: MIT] [Live]

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

bash

npm run dev        # start dev servernpm run build      # production build (static export to /out)

npm run dev        # start dev servernpm run build      # production build (static export to /out)

Deploy (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.

bash

npm run dev     # start dev servernpm run lint    # eslintnpm run build   # production build (static export to /out)

npm run dev     # start dev servernpm run lint    # eslintnpm 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:

bash

docker compose up -d          # builds and serves on :8080# ornpx serve out                 # zero-config static server# ordocker run -d -p 8080:80 -v ./out:/usr/share/nginx/html nginx:alpine

docker compose up -d          # builds and serves on :8080# ornpx serve out                 # zero-config static server# ordocker 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.

Source: README.md at commit e905c22

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts