The mcpcert CLI

Provision a hosted development CIMD and test your MCP client's OAuth from your local development workflow, with no account required.

npm PyPI

Install

Two builds, one identical command set. Both install an executable named mcpcert.

Node.js (npm)Node ≥ 22

npm install mcpcert-cli

View on npm

Python (PyPI)Python ≥ 3.11

pipx install mcpcert-cli

View on PyPI

Usage

mcpcert init --accept-tos     # provision a hosted dev CIMD (no account)
mcpcert info                  # show it (offline)
mcpcert conformance run       # end-to-end OAuth 2.0 + PKCE conformance check
mcpcert update --redirect-uri http://127.0.0.1:8080/callback

mcpcert initProvision an anonymous development CIMD.

mcpcert updateEdit metadata (e.g. redirect URIs) before expiry.

mcpcert infoPrint the local CIMD, expiry, and dashboard claim link.

mcpcert conformance runDrive the OAuth 2.0 + PKCE flow end to end.

mcpcert conformance listList conformance runs for the development CIMD.

mcpcert conformance show <runId>Show one conformance run's trace.

Run mcpcert <command> --help for flags. Add --json to any command for machine-readable output.

From dev to production

When your client is ready, claim its development CIMD in the web dashboard using the auth token saved by mcpcert init in .mcpcert/credentials.json. Once claimed, promote it to permanent production hosting from your dashboard. Remember you have 60 days to claim and promote an auto-provisioned CIMD before it expires.

Open source - Apache-2.0 - same command set for npm and PyPI

Get it on npm Get it on PyPI