Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
MCP server for Google Cloud Armor WAF log patrol: deny summaries and false-positive checks
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 …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"cloudarmor": {
"command": "uvx",
"args": [
"cloudarmor-mcp"
]
}
}
}Run this in your terminal
claude mcp add cloudarmor -- uvx cloudarmor-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cloudarmor": {
"command": "uvx",
"args": [
"cloudarmor-mcp"
]
}
}
}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": {
"cloudarmor": {
"type": "stdio",
"command": "uvx",
"args": [
"cloudarmor-mcp"
]
}
}
}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.
These 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 shigechika, 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.7.0) reached the registry 31 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, Rystic
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.
Start, seed, clock, inspect and diff Rystic API simulators from your agent.
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 | 日本語
MCP server for Google Cloud Armor WAF log patrol — deny summaries per rule, home-region false-positive checks, and preview (dry-run) rule review, straight from Cloud Logging.
Built for a daily "is the WAF healthy?" patrol: one daily_brief call answers *what did we block, did we block anyone we shouldn't have, and are the preview rules ready to promote*.
Documentation: https://shigechika.github.io/cloudarmor-mcp/
| Tool | Purpose |
|---|---|
daily_brief | One-call morning summary: enforced DENYs by rule priority, home-region false-positive lens, preview DENYs |
enforce_denies | Enforced DENY counts per rule priority |
home_region_denies | Enforced DENYs whose source IP geolocates to your home region — anything not marked known-normal is a false-positive candidate |
preview_denies | Preview (dry-run) DENY counts — a quiet preview rule is a promotion candidate |
health_check | Version, config presence, and a minimal Cloud Logging probe |
All tools are read-only. Counts are hard-capped (default 2000 entries per query) and a capped result is reported as >= N (capped), never as an exact total.
Create a service account with `roles/logging.viewer` only and download a key. Unlike human accounts, service accounts are not subject to organization re-authentication policies, so an unattended patrol never silently expires.
gcloud iam service-accounts create waf-log-viewer --project=YOUR_PROJECT
gcloud projects add-iam-policy-binding YOUR_PROJECT \ --member=serviceAccount:waf-log-viewer@YOUR_PROJECT.iam.gserviceaccount.com \ --role=roles/logging.viewer gcloud iam service-accounts keys create key.json \ --iam-account=waf-log-viewer@YOUR_PROJECT.iam.gserviceaccount.com
pip install cloudarmor-mcp
uv tool install cloudarmor-mcp
| Variable | Required | Meaning |
|---|---|---|
CLOUDARMOR_PROJECT | yes | GCP project ID that receives the load-balancer logs |
GOOGLE_APPLICATION_CREDENTIALS | yes | Path to the service-account key file |
CLOUDARMOR_BACKEND_SERVICES | no | Comma-separated backend service names to filter (default: all) |
CLOUDARMOR_HOME_REGION | no | ISO region code treated as home traffic, e.g. JP. Enables the false-positive lens |
CLOUDARMOR_RULES_INI | no | Path to a rules INI (labels + known-normal priorities, see below) |
CLOUDARMOR_MAX_ENTRIES | no | Max entries fetched per query (default 2000) |
Keep your rule numbering out of prompts and give the reports human-readable labels:
[rules]
101 = block non-home deep-path crawlers 500 = AutoDiscover probe block 1002 = OWASP LFI protection
[home] ; home-region DENYs on these priorities are expected, not false positives known_normal_priorities = 500, 600
This repository doubles as a single-plugin marketplace, so Claude Code can install the server for you:
/plugin marketplace add shigechika/cloudarmor-mcp
/plugin install cloudarmor-mcp@cloudarmor-mcp
The plugin launches uvx cloudarmor-mcp and reads the same environment variables described in Environment variables above; export them before starting Claude Code. GOOGLE_APPLICATION_CREDENTIALS still has to point at a service-account key file that exists on your own machine — the plugin can't ship or fetch that file for you, so this server can't be fully configured through the plugin's own settings alone.
uvx must be on the PATH of the process that runs Claude Code — a login shell usually has it, but a GUI-launched app may not; install uv system-wide if the plugin fails to start.
claude mcp add cloudarmor -- cloudarmor-mcp
with the environment variables above in the server's env.
codex mcp add cloudarmor -- cloudarmor-mcp
Pass the environment variables above with --env KEY=VALUE (before --).
Any other MCP client that launches stdio servers works the same way: give it cloudarmor-mcp as the command and set the environment variables above in its environment.
cloudarmor-mcp --version # print version
cloudarmor-mcp --check # config + API probe (exit 0 when healthy) cloudarmor-mcp --brief # print daily_brief to stdout (cron / smoke tests)
cloudarmor-mcp deny-export --date 2026-09-22 --tz Asia/Tokyo > out.tmp && mv out.tmp 2026-09-22.json
Writes one JSON document to stdout with one record per DENY log entry of that calendar day ([00:00, 24:00) in --tz, default UTC): the enforced and preview policy verdicts (policy, priority, action, outcome, rule_ids), source IP, region code and ASN as Cloud Armor logged them, method, host, path (query string dropped — only its length is kept), status, User-Agent (200 chars) and backend. --kind both (default) fetches entries where either policy says DENY in a single query, so a request that matched a preview rule *and* was denied appears once with both sections filled. --backend a,b overrides CLOUDARMOR_BACKEND_SERVICES.
This and traffic-export (below) are the only outputs of the package that contain per-request log data; it is meant for an operator batch on the same host that aggregates the day itself. The document ends with count, fetched, malformed and capped: when capped is true the export stopped at --max-entries (default 200000; CLOUDARMOR_MAX_ENTRIES does not apply) and is a prefix of the day, oldest first. Records are streamed, so memory does not grow with the day, and pages are fetched at most one per 1.2 s to stay under the Cloud Logging read quota (60 requests per minute), so a day with 200,000 entries takes a few minutes. A day that has not ended yet is refused. Run it some minutes after local midnight — Cloud Logging entries arrive with a delay — and write to a temporary file first: on a query failure the exit code is 1 and stdout may hold an unterminated document.
cloudarmor-mcp traffic-export --date 2026-09-22 --tz Asia/Tokyo --sample 0.01 > out.tmp && mv out.tmp 2026-09-22.json
Same document layout and record fields as deny-export, but for every load-balancer request of the day — allowed, denied and served from the CDN cache — thinned by Cloud Logging's sample(insertId, RATE) (--sample, default 0.01). The sample is a hash of each entry's insertId, so it is spread evenly over the day and the same rate selects the same entries on every run; scale counts by 1 / sample to estimate the day — but not when capped is true: entries are read oldest first, so a capped export covers only the early part of the day (lower --sample or raise --max-entries instead). Each record adds cache_hit. When no backend security policy evaluated a request (a CDN cache hit, for example) it has enforced: null and no region code or ASN; use cache_hit, not enforced, to tell cache hits apart. The header carries sample instead of kind. Use it to see who visits — browsers, crawlers, AI agents — which the DENY logs cannot show. The per-request caveats of deny-export apply: the records include legitimate visitors' addresses.
known_normal_priorities list keeps expected rules (e.g. an AutoDiscover block) out of the suspicious list.MIT