
Supplier Directory
io.github.theluckystrikePublished by GitHub account theluckystrikev0.22.5Updated Oct 24, 2026
A supplier directory that does not rot: contacts, payment terms, lead times, due-review report.
Overview
A local supplier directory MCP server that lets an assistant add, look up, update and review supplier records, and export them to CSV or Markdown.
- What you can do
- Add suppliers with category, contact details, payment terms, lead time and notes, each getting a SUP number
- List the directory A to Z with review age, filtered by category or free text, and read single records in full
- Update any field on a record, remove a supplier, and stamp records as reviewed
- Produce a due-review report of records not reviewed in N days, most overdue first (Pro)
- Export the directory as CSV (free) or a Markdown table (Pro)
- Check or activate a Pro license
- When to use it
- Useful for freelancers or small purchasing workflows that keep supplier contacts, terms and lead times in a spreadsheet and want the assistant to answer questions like which records have gone stale. It suits people who want the data to stay on their own machine with no account.
- Requirements
- Runs as a local process on the user's machine (desktop only). The README's install entries use npx, but the npm package is not published yet, so a clone and build is currently the working path. Data is stored locally under the user's data directory. An optional Pro license key can be supplied via the MCP_LICENSE_KEY environment variable.
Installation
In SourceWeft
- Open Supplier Directory 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
mcp-supplier-list
[theluckystrike/mcp-supplier-list MCP server]
In the official MCP Registry (io.github.theluckystrike/supplier-list).
This is the mcp supplier list server: a supplier directory inside your MCP client that does not rot the way the spreadsheet does. Add each supplier once, what they supply, who to contact and how, the payment terms, the lead time in days, and notes, and every record carries the date it was last reviewed, so "which of these records have gone stale?" is a question the directory answers instead of a chore you forget. Ask for a supplier by name, list the directory by category, and export the whole thing to CSV or Markdown when someone else needs it. Everything stays on this machine; there is no account and no network call.
Built by theluckystrike.
npm publish for @theluckystrike/mcp-supplier-list is pending, so npx -y @theluckystrike/mcp-supplier-list returns 404 today. Until then, a clone+build is the working path.
Why not a spreadsheet
A spreadsheet of suppliers rots because nothing in it tells you it is stale: the phone number changed eight months ago and you find out when the order bounces. An mcp supplier list lives where the purchasing conversations already happen, and the review stamp on every record turns "is this still true?" into a report instead of a memory test.
Install
Claude Desktop
macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json:
Claude Code
Cursor
~/.cursor/mcp.json (global) or .cursor/mcp.json (project), same entry as Claude Desktop.
Tools
Free vs Pro
The directory itself is never metered. Ten suppliers is a real working list for a freelancer, and reading, changing, searching and CSV-exporting the suppliers you have stays free for good. What Pro lifts is how many suppliers the directory holds, Markdown export, and the due-review report that keeps a bigger directory honest.
Get Pro: https://mcp.zovo.one/buy/supplier-list, $19 one-time for this server, or $39 for the bundle.
Privacy
All data stays local, in ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/supplier-list/. Two files: suppliers.json, counter.json. Nothing is sent anywhere, there is no account, no API key and no network call in this server at all. License keys are verified offline.
Built by theluckystrike. https://github.com/theluckystrike
Use these docs as an MCP server
Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install:
- Docs MCP URL: https://gitmcp.io/theluckystrike/mcp-supplier-list
Source: servers/supplier-list/README.md at commit 55b3f42
Tools
0Version history
2- v0.22.5LatestOct 14, 2026
- v0.22.0Sep 23, 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