§00Docs
How PartnerMCP works,
in depth.
Concept guides for architects and developers: how integrations are planned and run, how PartnerMCP reaches each system, and how changes and access are controlled.
What's documented where
- Concept guidesPublic — this site
- API referenceFull API reference is shared with early-access customers.
- Architecture reviewWith your security and network teams
Foundations
- 01
How PartnerMCP works
From a sentence to a running, monitored integration: what PartnerMCP does at each stage, and what actually runs in production.
- Intelligence at design time, determinism at runtime
- The lifecycle
- What an integration is made of
- What stays with you
- 02
Connection methods
How PartnerMCP chooses the path to each system: MCP where it's the right path, and REST, OData, GraphQL, SOAP, SQL, events or files where those are safer or the only option.
- How the path is chosen
- MCP, where it's the right path
- APIs: REST, OData, GraphQL and SOAP
- Change detection
Building
- 03
Field mapping
How PartnerMCP decides which field goes where — by meaning, with a confidence and a reason for every mapping. Worked example: Salesforce to Priority ERP.
- Names are not meaning
- Where the evidence comes from
- Confidence and review
- Salesforce → Priority, field by field
- 04
Change management
Every change to a running integration — requested by you, proposed by PartnerMCP or forced by a system — becomes a versioned diff that is tested, approved and reversible.
- Where changes come from
- Anatomy of a change
- When a system changes underneath
- Environments
Security & deployment
- 05
Edge Agent
Architecture concept: a small agent inside your network that connects out to PartnerMCP, so systems such as an on-prem ERP never need a public endpoint.
- How it works
- Design goals
- An allowlist, not a tunnel to everything
- Identity and revocation
- 06
Security model
How PartnerMCP limits what each integration can reach, what it keeps, and who can change what — described as design, without certification claims.
- Identity and access
- Secrets
- Intelligence at design time, determinism at runtime
- Protections specific to MCP
The docs explain the concepts. These pages show them working — and what we'll go through with your team.
§03Build
The fastest way to learn it is to try it.
Describe an integration between two of your systems. PartnerMCP shows you its plan before anything is built.