Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Pre-flight spend authorization for AI agents. Set a budget, enforce limits, audit every decision.
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.
FIGUARD_API_KEY, FIGUARD_BASE_URL, FIGUARD_DATABASE, FIGUARD_MODEValues marked secret are keys to your account. Never share them or paste them into a chat.
You 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": {
"figuard": {
"command": "npx",
"args": [
"-y",
"figuard-mcp"
],
"env": {
"FIGUARD_API_KEY": "your-value",
"FIGUARD_BASE_URL": "your-value",
"FIGUARD_DATABASE": "your-value",
"FIGUARD_MODE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add figuard --env FIGUARD_API_KEY=your-value --env FIGUARD_BASE_URL=your-value --env FIGUARD_DATABASE=your-value --env FIGUARD_MODE=your-value -- npx -y figuard-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"figuard": {
"command": "npx",
"args": [
"-y",
"figuard-mcp"
],
"env": {
"FIGUARD_API_KEY": "your-value",
"FIGUARD_BASE_URL": "your-value",
"FIGUARD_DATABASE": "your-value",
"FIGUARD_MODE": "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": {
"figuard": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"figuard-mcp"
],
"env": {
"FIGUARD_API_KEY": "your-value",
"FIGUARD_BASE_URL": "your-value",
"FIGUARD_DATABASE": "your-value",
"FIGUARD_MODE": "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.
FIGUARD_BASE_URL envFIGUARD_DATABASE envFIGUARD_MODE 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 figuard, 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.
You need to fill in: FIGUARD_API_KEY
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 (1.2.0) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Zendesk
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.
Zendesk MCP Pack — tickets, users, organizations via OAuth.
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.
FiGuard MCP server — use FiGuard directly from Claude Code, Cursor, or Claude Desktop without writing any SDK code.
Adds 14 FiGuard tools to your AI assistant. Instead of writing SDK code, you just talk to Claude:
"Create a $500 travel budget with $300 for flights and $200 for hotels"
→ Claude calls
figuard_create_budget
"Authorize a $149 economy flight from this budget"
→ Claude calls
figuard_authorize→ returns AUTHORIZED or DENIED
"The flight ended up costing $147 — confirm the actual amount"
→ Claude calls
figuard_confirm
claude mcp add figuard-mcp \
--env FIGUARD_API_KEY=fg_live_... \ --env FIGUARD_BASE_URL=http://localhost:8080
Or add to ~/.claude/claude_desktop_config.json manually:
{
"mcpServers": { "figuard": { "command": "npx", "args": ["figuard-mcp"], "env": { "FIGUARD_API_KEY": "fg_live_...", "FIGUARD_BASE_URL": "http://localhost:8080" } } } }
Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):
{
"mcpServers": { "figuard": { "command": "npx", "args": ["figuard-mcp"], "env": { "FIGUARD_API_KEY": "fg_live_...", "FIGUARD_BASE_URL": "http://localhost:8080" } } } }
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS):
{
"mcpServers": { "figuard": { "command": "npx", "args": ["figuard-mcp"], "env": { "FIGUARD_API_KEY": "fg_live_...", "FIGUARD_BASE_URL": "http://localhost:8080" } } } }
Point FIGUARD_BASE_URL at the hosted sandbox to try FiGuard without running a local server:
{
"FIGUARD_API_KEY": "sb_live_demo", "FIGUARD_BASE_URL": "https://figuard-sandbox-g1ha.onrender.com" }
| Tool | What it does |
|---|---|
figuard_create_budget | Create a spending envelope; returns session_token |
figuard_authorize | Pre-flight check — AUTHORIZED or DENIED with reason |
figuard_confirm | Close a reservation with the actual amount after success |
figuard_fail | Release a reservation when the action fails |
figuard_void | Cancel an unused reservation |
figuard_get_budget | Check budget status, spent, reserved, available |
figuard_get_ledger | List all spend events with filtering |
figuard_resume_budget | Unfreeze a budget paused by anomaly detection |
figuard_extend_budget | Extend a budget's expiry time |
figuard_cancel_batch | Cancel up to 100 budgets in one call |
figuard_fund_budget | Adjust a budget's total limit (CREDIT / DEBIT / RESET / RESET_SPENT) |
figuard_create_delegation_token | Create a scoped per-agent token against a fleet budget |
figuard_revoke_delegation_token | Revoke a delegation token (idempotent) |
figuard_get_delegation_token | Check delegation token state and cap usage |
FIGUARD_API_KEY is configured as an environment variable, not a tool argument. Tool arguments appear in LLM context windows — API keys must never be passed as tool parameters.
Session tokens returned by figuard_create_budget are short-lived (they expire with the budget) and are safe to use as tool arguments within a session.
git clone https://github.com/figuard/figuard-core
cd figuard-core docker compose up -d
FiGuard will be available at http://localhost:8080.