Run SignerSet
Set up MPAS with the installer CLI, then connect independent proposers and maintainers. Start with separate accounts, or explore a local demo first.
Just exploring? Try the single-account macOS demo
Recommended setup: separate accounts
Keep these three roles in separate accounts:
Proposer account
Runs the agent that proposes actions through MPAS bridges.
Maintainer account
Is used by the approver who independently reviews and approves actions.
Verifier account (Credential Adapter)
Holds application credentials and enforces the approval policy. An operator, not a general-purpose agent, sets up this account.
Install your harness and Node.js
In the separate accounts above, install your preferred agent harness for the proposer and maintainer. Then install Node.js 22 or later, including npm, in all three accounts.
Install the MPAS CLI
Run this in each account. These steps are for a new installation.
All three accounts
npm install -g @oma3/mpas-cli@0.1.0-alpha.3Initialize the Credential Adapter
Run this in the Credential Adapter account. The installer creates its key and prints its public DID.
Credential Adapter account
mpas init verifier --action https://api.signerset.com --mode relayInitialize the maintainer
Run this in the maintainer account and choose your harness when prompted.
Maintainer account
mpas init maintainer --coordination https://api.signerset.comInitialize the proposer
Run this in the proposer account. When prompted, paste the Credential Adapter’s public DID from Step 3.
Proposer account
mpas init proposer --coordination https://api.signerset.com --action https://api.signerset.comCreate your SignerSet account
In the portal’s Participants page, add each participant with its role and public DID. Keep private keys in their own accounts.
Install your application integrations
Choose an application and follow both guides.
Proposer account
Install the MPAS bridge. For its Action and Coordination URLs, use https://api.signerset.com instead of 127.0.0.1. If no bridge package is published, follow the manual setup.
Install a proposer bridgeCredential Adapter account
Install the application’s MCP server and adapter configuration. Keep application credentials here only; use hosted relay mode.
Install the adapter integrationSet the approval policy
In the adapter configuration, set the allowed proposers, maintainers, and required approvals. Follow the adapter guide to validate the configuration. Portal registration does not set this policy.
Start the Credential Adapter
In the Credential Adapter account, run the mpas adapter start command printed by the installer. Confirm the adapter health check passes before continuing.
Verify the approval flow
Check the tools in each harness. Submit a low-risk action that requires approval, approve it from the maintainer account, and confirm it executes only after authorization.