Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
UNIDROIT Principles 2016 as executable rules: closed questions answered with grounds and source text
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.arxo.io/mcp/piccOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"picc": {
"command": "npx",
"args": [
"-y",
"@arxo/mcp-picc"
]
}
}
}Run this in your terminal
claude mcp add --transport http picc https://mcp.arxo.io/mcp/piccclaude mcp add picc -- npx -y @arxo/mcp-piccPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"picc": {
"url": "https://mcp.arxo.io/mcp/picc"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"picc": {
"command": "npx",
"args": [
"-y",
"@arxo/mcp-picc"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"picc": {
"type": "http",
"url": "https://mcp.arxo.io/mcp/picc"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"picc": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@arxo/mcp-picc"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.arxo.io/mcp/piccMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain arxo.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (0.3.11) reached the registry 23 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, AvaHR
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Read hiring data and create inactive assessment and questionnaire drafts for human review.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Pinned canon, executable as it stands: source text with provenance, the model built over it and the scenarios that check its answers. The norms here are data — they are executed by law; this repository carries no rule code of its own.
| Package | Version | Scenarios | Dependencies |
|---|---|---|---|
unidroit.picc | 0.1.0 | 5 | 0 |
unidroit.picc_formation | 0.1.0 | 4 | 1 |
unidroit.picc_limitation | 0.1.0 | 3 | 1 |
unidroit.picc_non_performance | 0.1.0 | 4 | 1 |
unidroit.picc_obligations | 0.1.0 | 4 | 1 |
unidroit.picc_performance | 0.1.0 | 4 | 1 |
unidroit.picc_validity | 0.1.0 | 4 | 1 |
Every package is built by package.py with the pinned toolchain: compilation, §267 scenarios on both evaluators, replay of saved evaluations and a rebuild from the release itself. A failure of any step stops the build.
python3 tools/toolchain.py download --lock toolchain.lock.json --out /tmp/law-tools
python3 /tmp/law-tools/package.py packages/ \ --lawc /tmp/law-tools/law-cli --offline --out /tmp/ -release
Dependency bytes are pinned under packages/ /deps/ and verified against the contentHash recorded in law.lock: the build and the CI are offline.
Two ways, the same slice of the canon and the same engine; the difference is whose machine evaluates.
https://mcp.arxo.io/mcp/picc — requests are evaluated on Arxo infrastructure.docker compose -f mcp/compose.yml up — nothing leaves the machine.mcp/pin.json records what either one must answer from: the content hash of the canon profile, the pinned packages, the ABI version of the engine and the availability of the hosted endpoint. An answer that cannot be traced to that pin is not this repository's answer.
Each collection is a case package of its own: the facts, the questions and the answers, with the pinned canon as its dependency. Ask one from its directory with law ask . — nothing is downloaded.
| Collection | Cases | Questions |
|---|---|---|
packages/unidroit.picc/examples/applying-the-principles | 2 | 7 |
packages/unidroit.picc_formation/examples/battle-of-forms | 2 | 6 |
packages/unidroit.picc_limitation/examples/limitation-periods | 2 | 7 |
packages/unidroit.picc_non_performance/examples/interest-rate | 2 | 7 |
packages/unidroit.picc_performance/examples/hardship | 2 | 9 |
Code and model: see LICENSE. The pinned texts of the publishers keep their own terms of reproduction, listed per package in NOTICE; those terms are not covered by the code licence.
Maintainer: Rifat Dzhumagulov (hi@arxo.io). Address: https://github.com/arxohq/arxo-unidroit-picc.