Bulwark MCP Server

Connect Bulwark to Claude, Cursor or any other MCP client and it stops being a tab you switch to. AI agent governance: content scanning, audit logs, policy evaluation, session management. The bulwark mcp server is what makes that connection.

What the server does

Bulwark sits between AI agents and external tools, enforcing policies, managing credentials, inspecting content, and maintaining a complete audit trail. One policy governs all your agents — Claude Code, OpenClaw, Codex, or any MCP/HTTP client.

• Policy enforcement — — YAML-based rules control which tools agents can use, with glob patterns, scope-based precedence, and hot-reload
• Credential management — — Agents never see real secrets. Bulwark injects credentials at the last mile, encrypted at rest with age
• Content inspection — — Scan requests and responses for secrets, PII, and prompt injection. Block or redact automatically
• Audit logging — — Every action recorded in a tamper-evident SQLite database with blake3 hash chains
• Rate limiting — — Token-bucket rate limits per session, operator, tool, or globally. Cost tracking with budget enforcement
• MCP-native — — Works as an MCP gateway or HTTP forward proxy. Governance metadata on every tool call response

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• MCP-native — Works as an MCP gateway or HTTP forward proxy. Governance metadata on every tool call response
• name — github
• Mode — Transport

Credentials and setup notes

Configuration is passed through the environment: GITHUB_TOKEN, BULWARK_SESSION, GITHUB_PERSONAL_ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Bulwark's toolset — MCP-native, name, Mode — is a fair guide to whether it matches your workflow. It is maintained by bpolania; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.