generateUuidLABSCO SUMMARY
One tool, and the version choice is the point.
A model asked to invent an id will invent something that looks like a UUID and is not one. This hands the job to the uuid package and picks v7 specifically, so the ids it returns sort chronologically — which matters the moment they become keys in a table you will later order by.
What it is
A small TypeScript server exposing one tool. It uses the official uuid package to produce UUID v7 values, which carry a millisecond Unix timestamp and are therefore chronologically sortable.
What you get
- A UUID v7 string on request, with no input parameters at all —
generateUuid - Ids that sort by creation time, because the timestamp sits in the first part of the value
- Collision resistance from randomised data, so several ids created in the same millisecond stay distinct
Requirements
No account and no key. npm install then npm run build, and point the client at the absolute path of the built build/index.js. The package is uuid-mcp 1.0.0.
Setup effort
Build from source
USE CASES
Generating ids for seed data
Get real UUIDs for fixtures instead of hand-typed strings that collide.
Creating a correlation id mid-task
Ask for one id and use it across the logs and records the agent is about to write.
Needing keys that sort by time
Use v7 so the natural ordering of the key matches the order things were created.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
git clone https://github.com/tanker327/uuid-mcp
cd uuid-mcp
# Install dependencies
npm install
# Build the project
npm run buildMCP Clients
Claude Desktop
{
"mcpServers": {
"uuid-provider": {
"command": "node",
"args": [
"<YOUR_PATH_TO_UUID_MCP>/build/index.js"
]
}
}
}