Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Early access - AI governance gateway for MCP tool calls (policies, PII masking, audit).
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"palveron": {
"command": "npx",
"args": [
"-y",
"@palveron/mcp-server"
]
}
}
}在终端中运行这条命令
claude mcp add palveron -- npx -y @palveron/mcp-server粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"palveron": {
"command": "npx",
"args": [
"-y",
"@palveron/mcp-server"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"palveron": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@palveron/mcp-server"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过 GitHub 账户 palveron 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(1.0.1)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
同一分类中有:Spec Driven Development, Remote Desktop Commander, OpenTakeoff
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
Construction takeoff for AI agents: load plans, set scale, measure, count, export with provenance.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
@palveron/mcp-server Official Palveron MCP server — advisory AI-governance checks for MCP hosts and coding agents
⚡ Early access. Palveron is launching soon and access is currently invite-gated. This server is fully functional — you just need a
pv_live_key, which comes with an Early Access invite. [Join the waitlist → palveron.com/early-access](https://palveron.com/early-access)
Give your MCP-capable client — Claude Code, Cursor, any other MCP host — governance tools it can call before executing an action: policy verdicts, PII-masking results, and an audit trace for every check, all from the Palveron AI Governance Gateway.
This package is the advisory path. It cannot physically stop a tool call: it answers the question "is this allowed?", and the calling agent (or your code via check()/wrap()) is expected to honor the answer. That is by design — it works with any MCP host, needs no network topology change, and gives you verdicts plus audit traces immediately.
Enforced, non-bypassable governance for MCP tool calls is a different product surface: the Palveron remote MCP proxy. There you register the *target* MCP server in the Palveron dashboard and point your IDE at POST {gateway}/api/v1/mcp/proxy/{server_id} instead of the target — every tools/call then structurally passes through policy checks, approval holds, and drift detection before it can reach the target server. No cooperation from the agent required.
This package (@palveron/mcp-server) | Remote MCP proxy | |
|---|---|---|
| Model | Voluntary pre-flight check | In-path enforcement |
| Can a call bypass it? | Yes — enforcement depends on the caller honoring the verdict | No — the proxy sits between client and target server |
| Setup | npx, one env var | Register the target server in the dashboard, point the IDE at the proxy URL |
| Use it when | You want verdicts + audit traces inside any MCP host, or wrap tool calls programmatically | You need governance that agents cannot skip |
See the MCP setup guide for the enforced path.
npm install -g @palveron/mcp-server
npx @palveron/mcp-server
The
pv_live_…key in the examples below requires an Early Access invite — request one here. Once you have a key, everything works out of the box.
Add to your claude_desktop_config.json:
{
"mcpServers": { "palveron": { "command": "npx", "args": ["@palveron/mcp-server"], "env": { "PALVERON_API_KEY": "pv_live_xxx", "PALVERON_BASE_URL": "https://gateway.palveron.com" } } } }
Any MCP-capable host can launch the server via the palveron-mcp binary:
PALVERON_API_KEY=pv_live_xxx palveron-mcp
| Tool | Purpose |
|---|---|
palveron_check | Check a tool call against governance policies before execution. Returns the decision (PASSED, BLOCKED, MODIFIED/REDACTED/ANONYMIZED with the sanitized input, PENDING_APPROVAL, …), whether the call may proceed, findings, and the audit trace ID. |
palveron_status | Governance status and diagnostics — gateway connectivity, circuit-breaker state, configured local lists. |
palveron_policy_list | List the project's active policies so the host can explain its decisions. |
The server reads its configuration from environment variables. The MCP host sets them; you never put secrets in code.
| Variable | Required | Description |
|---|---|---|
PALVERON_API_KEY | yes | API key (pv_live_…) — comes with an Early Access invite |
PALVERON_BASE_URL | no | Override the gateway endpoint (default: https://gateway.palveron.com) |
PALVERON_FAIL_OPEN | no | true = allow tool calls when the gateway is unreachable (default: false, fail-closed) |
PALVERON_LOG_LEVEL | no | debug / info / warn / error / silent (default: info) |
PALVERON_ALWAYS_BLOCK | no | Comma-separated tool names that are always denied locally, without a gateway call |
PALVERON_ALWAYS_ALLOW | no | Comma-separated tool names that always pass locally, without a gateway call |
MIT — Copyright © 2026 Palveron.