Install the MCP Adapter
The MCP adapter is a local stdio program. It sits between your MCP client and an MCP server, and sends each tools/call request to the control plane for a decision before it is forwarded. This page covers installing the binary and checking its file integrity. For configuration, see MCP Adapter. MCP over HTTP does not use this binary. It is governed through the Transparent Proxy.
Before you start
- Your organization must have the
mcp.enabledentitlement. See Licensing & Distribution. - You need an API key for your organization. See Quickstart.
- Choose the release that matches your operating system and CPU architecture.
1. Download the binary
The coordinated 0.9.0 artifacts are verified as published. Use the matching
mcp-pep-v0.9.0 binary release and v0.9.0 SDK/Envoy adapter versions.
The public Envoy Docker image is for MCP over
HTTP, not a replacement for this stdio binary. Do not substitute mixed versions during an
approval-binding upgrade. See release and upgrade guidance.
Each release publishes one binary per platform, named:
openprodkt-mcp-pep_<version>_<os>_<arch>
Supported combinations:
| OS | Architecture | <os> | <arch> |
|---|---|---|---|
| Linux | Intel/AMD 64-bit | linux | amd64 |
| Linux | ARM 64-bit | linux | arm64 |
| macOS | Intel | darwin | amd64 |
| macOS | Apple silicon | darwin | arm64 |
Each release also includes a SHA256SUMS file that lists the checksum of every binary.
Download the release assets from the release page for your version:
https://github.com/<owner>/<repo>/releases
Replace <owner>/<repo> with the repository your organization was given. Then make the binary executable and move it onto your PATH:
chmod +x openprodkt-mcp-pep_<version>_<os>_<arch>
mv openprodkt-mcp-pep_<version>_<os>_<arch> /usr/local/bin/openprodkt-mcp-pep
2. Verify the checksum
Check the binary against SHA256SUMS before you run it. Download SHA256SUMS into the same directory as the binary.
On Linux:
sha256sum -c SHA256SUMS --ignore-missing
On macOS:
shasum -a 256 -c SHA256SUMS --ignore-missing
Each binary you downloaded should report OK. A FAILED line means the file does not match the published release. Do not run it. Download it again, and report the problem if the mismatch persists.
3. Understand the verification limits
The release publisher verifies SHA-256 checksums before upload and checks the downloaded assets against the build's checksum manifest after publication.
These checks detect file corruption or a mismatch with the published checksum. They do not authenticate the publisher or prove which source produced the binary. Releases do not include signed build provenance attestations. Obtain the binary and checksum file from your organization's trusted release location; if your deployment requires signed provenance, these artifacts alone do not satisfy that requirement.
4. Check the SBOM
Each release includes a software bill of materials (SBOM) in SPDX format. Use it to review the dependencies included in the release. It is published with the release assets.
5. Run it
Confirm the binary starts and reports its version:
openprodkt-mcp-pep --version
Then configure it to wrap your MCP server. Follow MCP Adapter for the configuration keys, the API key setup, and how to point your MCP client at the adapter.
If the adapter cannot reach the control plane, it denies tool calls. See Troubleshooting for the symptoms and fixes.
Upgrading
Download the new release, repeat the checksum checks and review the SBOM, and replace the binary. The adapter keeps no state of its own. Decisions are recorded by the control plane.
When you upgrade from a release before 0.8.0, pause and drain approval-bearing operations before the coordinated
control-plane/SDK/adapter upgrade or rollback. Existing approvals are not
silently rebound to new canonicalization. Keep traffic paused until matching
artifacts and the deployment are verified; see Upgrade and rollback.