Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Cork MCP
Overview
Description from the maker (original English)
Every Cork API operation, plus cross-client risk attribution and exploitability-first vuln triage.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
- You need to fill in: CORK_API_KEY
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
CORK_API_KEY,CORK_BASE_URL,CORK_USER_AGENT,PRINTING_PRESS_CLIENT_PROFILE
Values marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
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.
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.
Values you fill in
- Set the CORK_API_KEY credential for the Cork MCP server.
CORK_BASE_URLenvBase URL for the Cork API. Leave the prefilled default unless your account uses a different regional or self-hosted host.CORK_USER_AGENTenvOverrides the User-Agent the CLI sends on Cork requests. Leave blank to use the CLI's own built-in User-Agent.PRINTING_PRESS_CLIENT_PROFILEenvBinds this MCP server to one tenant-gated client profile, so every call answers for that customer. Leave blank to use the profile configured as default_client_profile.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account servosity, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32558 servers in this category
- Published to the registry more recently than 72% of the other 32558 servers in this category
- Basic checks equal to or better than 100% of the other 32558 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Cork MCP safe?
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.
What keys or codes does it need?
You need to fill in: CORK_API_KEY
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.8) reached the registry 14 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, FactLot
Alternatives
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
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
FactLot
by 9mp96ygnbk-alt
Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.
Computer or cloudUpdated today
Install
README from the maker
Open the README
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.
Cork + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP
Unofficial. Community-built Claude Code Skill and MCP server for the Cork
API. Not affiliated with, endorsed by, or sponsored by Cork.
Cork and Cork Vantage are trademarks of Cork Protection, Inc.
Every Cork API operation, plus cross-client risk attribution, exploitability-first vulnerability triage, overdue-compliance detection, and stale-connector health checks that a stateless API mirror cannot answer in a single call. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.
Works with your agent
Security note (until this connector is reprinted). Do not put this
connector behind the
supergatewaybridge or any other stdio-to-HTTP bridge,
not even on localhost. The bridge adds no password, so anyone who can reach
its port can use the MCP tools with your credentials. Use the default stdio
transport. If you set up a bridge or a tunnel for a remote agent, shut it
down. A fix is on the way.
The six agents MSP owners actually use (self-serve, works today):
| Your AI agent | How to install the Cork skill |
|---|---|
| Claude Desktop | Run installer, then Settings > Extensions to register cork-mcp (no JSON editing). |
| ChatGPT (desktop app) | Run installer, then add cork-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet. |
| Codex CLI | Paste the install prompt below. |
| Claude Code | Paste the install prompt below. |
| Claude Cowork | Paste the install prompt below. |
| GitHub Copilot (VS Code) | Run installer, add cork-mcp to mcp.json under the servers key, then pick Agent mode. |
The ChatGPT desktop app runs cork-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server. This connector speaks stdio only, and the bridge it would need is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Also for the Microsoft and Google stacks
Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.
| Agent | What it takes |
|---|---|
| Microsoft 365 Copilot / Copilot Studio | Not supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list. |
| Google Gemini | Gemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet. |
Skill-native agents (also covered): Hermes and OpenClaw read this skill's
SKILL.mddirectly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).
Run more than one agent? Install across all 51+ supported agents in one command:
npx skills add Servosity/msp-skills@latest(requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.
Install in 60 seconds
Prefer the Claude Code plugin? Add the marketplace once, then install:
/plugin marketplace add Servosity/msp-skills/plugin install cork@msp-skills
Path A - paste one prompt into your AI agent (recommended)
Copy this into Claude Code, Codex CLI, or Claude Cowork:
Install the Cork Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cork/install.sh). If it uses Windows PowerShell, runiwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cork/install.ps1 | iex. Then authenticate per the README and runcork-cli --helpto explore.
The same prompt works in any agent that can run shell.
Path B - run the installer yourself
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cork/install.ps1 | iexmacOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cork/install.sh)The installer drops both cork-cli (the CLI) and cork-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.
Verify:
cork-cli --versionUpgrade to the latest version
The installer always fetches the current release - re-run it to upgrade:
macOS / Linux:
bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cork/install.sh)Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/cork/install.ps1 | iexClaude Code plugin users: /plugin update cork@msp-skills.
Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client
After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.
Install for Hermes
From the Hermes CLI:
hermes skills install servosity/msp-skills/skills/cork --forceInside a Hermes chat session:
/skills install servosity/msp-skills/skills/cork --forceHermes speaks MCP natively, so it can also use the cork-mcp server directly - same install path, same env vars.
Install for OpenClaw
Tell your OpenClaw agent (copy this):
Install the cork skill from https://github.com/servosity/msp-skills/tree/main/skills/cork. The skill defines how its required CLI (
cork-cli) can be installed via theopenclaw:frontmatter block.
OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.
Authenticate
Set the API key the CLI needs (Cork portal > Settings > API Keys):
export CORK_API_KEY=<your key>cork-cli doctor
doctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.
One property of Cork keys is worth knowing up front: an API key inherits the permissions of the user who created it. A 403 on the distributor or integration endpoints usually means the key was minted by an operator without that scope, not that the key is wrong. That property is also your best control - mint a read-only key for read-only work. See governance.md.
Sync before you ask
search, score regressions, and the client-roster lookups inside several other commands read a local mirror. Populate it once:
cork-cli syncsync is read-only against the Cork API (GET requests only) and writes to a SQLite file under your own user account. Re-run it whenever you want fresher data; commands tell you when the mirror is stale rather than answering from data you did not expect.
What this skill does
| Question your MSP keeps asking | Command |
|---|---|
| Why did this client's risk score move, and which component drove it? | cork-cli score attribute --since 30d |
| Which clients across the whole book slipped the most this week? | cork-cli score regressions --since 7d |
| What should we patch first, ranked by what is actually being exploited? | cork-cli vulnerabilities triage |
| An advisory just named a CVE. Are we exposed, and where? | cork-cli vulnerabilities exposure CVE-2023-21608 |
| Which compliance events have blown their remediation window? | cork-cli compliance overdue |
| Which connectors report healthy but stopped syncing? | cork-cli integrations health |
| Did this client get fully monitored after onboarding? | cork-cli coverage gaps --client |
| Which unwarranted clients are carrying the most risk? | cork-cli warranties exposure |
| Is my auth and connectivity actually working? | cork-cli doctor |
Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.
What makes this different
Cork's own tooling is a stateless mirror of its REST API: it answers one client, right now. Every question an MSP actually asks is cross-client, cross-time, or both, and the Cork API exposes no cross-client aggregate endpoint at all, so the live path for any of them is a fan-out across every client with no stored yesterday to compare against.
This skill syncs Cork into a local SQLite mirror and does the fan-out and the joining for you, so "the risk score dropped" becomes "the risk score dropped *because* compliance moved, and here are the overdue events behind it" - one command instead of a per-client walk you assemble by hand.
Only score regressions answers purely from the local mirror. The other seven fetch from the Cork API on every run, because the rows they need carry no id that can be mirrored - vulnerability findings, compliance events, connector state, and score history. Several of them do use the mirror for the client roster so they can skip a live /clients fan-out, and fall back to a live roster scan when the mirror is empty. Every one of them caps its own scan and prints when a sweep was truncated, instead of reporting a false all-clear.
The pain this closes
- A score drops eleven points between QBRs. Cork returns the four components per timestamp but never differences them, so someone exports two snapshots and subtracts by hand.
cork-cli score attributedoes the subtraction and ranks the cause. - "Which clients got worse this week" has no endpoint.
cork-cli score regressionsanswers it as one local query. - The vulnerability endpoint's server-side
sort_byaccepts onlysw_vendorandsw_product, so exploitability ordering is impossible upstream.cork-cli vulnerabilities triageranks known-exploited first, then EPSS, then CVSS, with a blast-radius device count. cve_idexists only nested insidecves[]and no endpoint accepts a CVE filter at any page size.cork-cli vulnerabilities exposureanswers "are we exposed to this one" directly.- A connector reports
connection_status: okwhilelast_synced_atis days old. Both fields ship in the same payload and nothing compares the timestamp to now. `cork-cli
Only the beginning is shown; read the rest in the repo