get_uuidv7LABSCO SUMMARY
Time-ordered ids on demand.
It removes a small, constant interruption: when a script, a fixture or a migration needs identifiers, they arrive in the conversation already in the right version and in the quantity asked for.
What it is
A two-call server that generates UUIDv7 strings. Version 7 carries a timestamp in its leading bits, so the identifiers sort in the order they were created - the property that makes them behave as database keys.
What you get
- A single UUIDv7 string, no arguments needed
- A batch of them, as many as the count you pass
- Generation inside the server process, so nothing about the identifier leaves your machine
Requirements
Python, with the server's dependencies installed - it is run from source as a path in your client config rather than from a published package. No account, no key, and no network call.
Setup effort
One command — uvx mcp-uuid-server
USE CASES
01
Seeding test data with realistic keys
Ask for a batch the size of the fixture and paste them in, rather than inventing ids that do not sort.
02
Getting one id, right now
A single call with no arguments, for the row or the config value you are writing this minute.
03
Keeping identifiers consistent across one change
Take one batch for the whole edit, so every id in the migration comes from the same generator and the same version.
2 tools
Listed in project docs. Your client may show a different list.
get_uuidv7_batchBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
uvx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx mcp-uuid-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"uuid_v7_generator": {
"command": "python",
"args": [
"<YOUR_PATH_TO_MCP_UUID_SERVER>/mcp_uuid_server/server.py"
]
}
}
}
