Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Enterprise MCP guard: roles, allowlist policy, human confirmation, JSONL audit log, example tools.
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.
MCP_AGENT_TEMPLATE_ROLE, MCP_AGENT_TEMPLATE_CONFIRM, MCP_AGENT_TEMPLATE_AUDIT_DIRYou need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"agent-template": {
"command": "uvx",
"args": [
"mcp-agent-template",
"serve"
],
"env": {
"MCP_AGENT_TEMPLATE_ROLE": "your-value",
"MCP_AGENT_TEMPLATE_CONFIRM": "your-value",
"MCP_AGENT_TEMPLATE_AUDIT_DIR": "your-value"
}
}
}
}Run this in your terminal
claude mcp add agent-template --env MCP_AGENT_TEMPLATE_ROLE=your-value --env MCP_AGENT_TEMPLATE_CONFIRM=your-value --env MCP_AGENT_TEMPLATE_AUDIT_DIR=your-value -- uvx mcp-agent-template serveFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agent-template": {
"command": "uvx",
"args": [
"mcp-agent-template",
"serve"
],
"env": {
"MCP_AGENT_TEMPLATE_ROLE": "your-value",
"MCP_AGENT_TEMPLATE_CONFIRM": "your-value",
"MCP_AGENT_TEMPLATE_AUDIT_DIR": "your-value"
}
}
}
}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": {
"agent-template": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-agent-template",
"serve"
],
"env": {
"MCP_AGENT_TEMPLATE_ROLE": "your-value",
"MCP_AGENT_TEMPLATE_CONFIRM": "your-value",
"MCP_AGENT_TEMPLATE_AUDIT_DIR": "your-value"
}
}
}
}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.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
MCP_AGENT_TEMPLATE_ROLE envMCP_AGENT_TEMPLATE_CONFIRM envMCP_AGENT_TEMPLATE_AUDIT_DIR envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 with the GitHub account amineutron, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
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.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Master CSS
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.
Inspect Master CSS classes, generated CSS, and project stylesheets from your AI client.
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.
English summary. A template for MCP servers that an IT department can let an LLM agent use: every tool call goes through an allowlist policy (policy.yaml), a caller role (lecteur / operateur / admin, derived from the MCP tool annotations), per-parameter allowed values, a human confirmation for destructive actions (MCP elicitation, both the 2025-11-25 and 2026-07-28 protocols), and a JSONL audit log (mode 0600, one correlation id per call). The mcp-agent-template package ships two runnable examples: an enterprise one (tickets, a read-only LDAP-like directory, a read-only SQL inventory, all on fictitious local data) and a generic ops one (systemd and docker status, restart with confirmation). Local-first, self-hosted, on-prem; no cloud, no telemetry. Dual licensed: AGPL-3.0, or a commercial licence for companies of any size.
Donner des outils a un agent IA dans une entreprise pose toujours les memes questions : qui a le droit de faire quoi, qui a valide une action dangereuse, et ou est la trace. Ce depot est un modele (bouton « Use this template ») qui y repond une fois pour toutes, autour du SDK MCP officiel.
Chaque appel d'outil passe, dans l'ordre :
policy.yaml) : un outil absent est refuse.| Type d'outil | Annotation MCP publiee | Role minimal |
|---|---|---|
| lecture | readOnlyHint | lecteur |
| ecriture non destructrice | — | operateur |
| destructif | destructiveHint | admin + confirmation humaine |
password, token, api_key...) sont masques.Un refus renvoie une erreur lisible a l'agent, jamais un faux succes.
uvx mcp-agent-template --help
uvx mcp-agent-template serve --example enterprise # tickets, annuaire, inventaire (donnees fictives) uvx mcp-agent-template serve --example ops # systemd et docker uvx mcp-agent-template check-policy policy.yaml # valide une politique et resume ses regles
Dans un client MCP (Claude Code, Claude Desktop...) :
{
"mcpServers": { "entreprise": { "command": "uvx", "args": ["mcp-agent-template", "serve", "--example", "enterprise"], "env": { "MCP_AGENT_TEMPLATE_ROLE": "operateur" } } } }
| Variable | Role | Defaut |
|---|---|---|
MCP_AGENT_TEMPLATE_ROLE | role de l'appelant : lecteur, operateur, admin | lecteur |
MCP_AGENT_TEMPLATE_CONFIRM | elicit : l'humain confirme via le client ; client : le client confirme deja lui-meme (il lit destructiveHint) | elicit |
MCP_AGENT_TEMPLATE_AUDIT_DIR | dossier du journal d'audit | ~/.local/state/mcp-agent-template |
MCP_AGENT_TEMPLATE_DATA_DIR | bases SQLite des exemples | ~/.local/state/mcp-agent-template-demo |
Le role vient pour l'instant de la configuration du client : chaque poste ou chaque profil recoit le sien. La source du role est une petite interface (RoleSource) : une authentification par jeton pourra s'y brancher sans toucher aux outils.
Entreprise (--example enterprise), sur des donnees FICTIVES d'une societe « Exemple SA » creees en local, sans aucun service externe :
list_tickets, get_ticket, create_ticket (la priorite « critique » est reservee aux humains par la politique), close_ticket, delete_ticket (admin + confirmation) ;search_directory, get_user, group_members ;list_tables, query_inventory. Deux verrous : la base est ouverte en mode=ro, et un autorisateur SQLite refuse toute ecriture, PRAGMA ou ATTACH, meme cachee dans un WITH.Ops (--example ops) : service_status et list_containers en lecture, restart_service limite aux unites listees par la politique, apres confirmation.
from mcp.server.mcpserver import MCPServer
from mcp_agent_template import Guard, Policy, ToolKind
server = MCPServer("mon-agent") guard = Guard(server, Policy.load("policy.yaml"))
@guard.tool(ToolKind.READ, title="Lister les commandes") def list_orders(status: str = "ouverte") -> list[dict]: """Commandes du jour.""" ...
@guard.tool(ToolKind.DESTRUCTIVE, title="Annuler une commande") def cancel_order(order_id: int) -> dict: """Annule une commande (admin + confirmation humaine).""" ...
server.run()
# policy.yaml
version: 1 default: deny tools: list_orders: {} cancel_order: allowed_values: order_id: ["1042", "1043"]
Pour brancher un vrai outil de tickets, un vrai annuaire LDAP ou une vraie base, remplacer les classes de src/mcp_agent_template/examples/stores.py : les outils MCP et la garde ne changent pas.
uv sync
uv run pytest # garde, politique, audit, exemples, protocoles 2025-11-25 et 2026-07-28, stdio uv run ruff check src tests
Un devcontainer est fourni (.devcontainer/).
Double licence :
Les contributions sont acceptees sous l'accord CLA.md.
Meme approche que fedora-agents (journal d'audit avec identifiant de correlation, annotations MCP) et Lyra, l'assistant vocal French-first qui fait confirmer l'humain avant chaque action sensible.