Palveron MCP Server

@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.

• Drop-in MCP server — one binary, configure your MCP host, you're done
• Advisory governance verdicts — the gateway decides allow / mask / deny / hold; the agent (or your wrapping code) acts on the verdict
• Audit trail per check — trace IDs flow back to the Palveron dashboard
• Built on `@palveron/sdk` — retry, circuit breaker, typed errors out of the box

Advisory check vs. enforced governance — which one do you need?

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.

See the MCP setup guide for the enforced path.

Installation

npm install -g @palveron/mcp-server

or use directly via npx

npx @palveron/mcp-server

Quick Start

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.

Claude Code

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" } } } }

Other MCP hosts

Any MCP-capable host can launch the server via the palveron-mcp binary:

PALVERON_API_KEY=pv_live_xxx palveron-mcp

Tools exposed via MCP

Configuration

The server reads its configuration from environment variables. The MCP host sets them; you never put secrets in code.

Requirements

• Node.js 18 or newer
• An MCP-capable client (Claude Code 0.4+, Cursor, etc.)

Links

• Early Access / Waitlist — palveron.com/early-access
• Documentation — docs.palveron.com/integrations/mcp
• Dashboard — palveron.com
• Support — hello@palveron.com
• GitHub — palveron/mcp-server
• Changelog — CHANGELOG.md

License

MIT — Copyright © 2026 Palveron.