Integrate MPP
What It Means to Host MPP
A host is any application that runs AI agent tools on behalf of users — an IDE, an enterprise AI platform, an agent orchestration framework, or a custom internal application. By integrating the MPP runtime, your platform gains a complete, standards-backed layer for tool verification, permission management, and sandboxed execution.
You don't need to build this yourself. The MPP runtime handles the security pipeline. You provide the user interface and the integration with your agent.
What Your Platform Gains
- Instant security credibility. Telling users that all tools in your platform are cryptographically verified and sandboxed is a meaningful differentiator — especially for enterprise and regulated market buyers.
- No bespoke trust infrastructure. The protocol defines how packages are verified, how permissions are evaluated, and how execution is contained. You implement the integration; the hard security guarantees are already specified.
- Access to the growing MPP tool ecosystem. Any tool published to the MPP registry works in your platform without modification. As the ecosystem grows, so does your catalogue.
- User trust and transparency. Your users see exactly what tools have been approved, what permissions they hold, and which version is running. This visibility builds confidence in AI-assisted workflows.
- Governance features out of the box. Administrators can control which publishers are trusted, enforce organisation-wide permission policies, and maintain a complete audit log of tool invocations.
What Integration Enables
Verified Tool Catalogues
Build a tool marketplace or internal catalogue where every listing is a verified, signed package. Users browse, approve, and install tools with confidence — no more “trust the developer” on faith.
Governed Agent Deployments
Enterprise customers can define which tools their agents are permitted to use, enforce approval workflows for new tool installations, and receive notifications when tool versions are updated. MPP makes agent governance tractable at scale.
Compliant AI Workflows
In regulated industries — finance, healthcare, legal — the ability to demonstrate that AI tools were verified, sandboxed, and operating within declared permissions is increasingly a compliance requirement. MPP provides the evidence trail.
Private Registries
Licensed customers can run their own MPP registry. This allows organisations to publish internal tools, restrict access to approved packages, and maintain complete control over what runs in their environment — without depending on a public registry.
What You Need to Provide
Hosting MPP requires three things from your application:
- A permission approval UI. Users need to see and confirm what a tool is requesting before it runs for the first time.
- Confirmation flows for sensitive operations. High-risk tool actions require explicit user confirmation. Your UI surfaces this; the runtime enforces it.
- Trust store management. Your platform maintains a list of approved publishers. The runtime uses this to decide whether a package's author is trusted.
The runtime takes care of everything else: verification, sandboxing, capability enforcement, privacy filtering, and lifecycle management.
Get Access
Integrating MPP requires a host licence. Contact the team to discuss your platform and the appropriate licensing structure.