Skip to content
PartnerMCPPartnerMCP

§00Integrations

Early access

Connect anything.
Operate everything.

Priority ERP, SAP, Oracle, NetSuite, Dynamics 365 and Salesforce — and the commerce, payment, data and internal systems around them. PartnerMCP connects each one through the interfaces its vendor supports, in the cloud or behind your firewall.

Build an IntegrationBrowse all systems

Flagship integrations

  1. 01ERPPriority ERP
    1. REST (OData v4)
    CloudOn-prem
  2. 02ERPSAP S/4HANA
    1. OData V2/V4 (published APIs)
    CloudOn-prem
  3. 03ERPOracle Fusion ERP (Oracle Fusion Cloud ERP)
    1. REST (fscmRestApi)
    Cloud
  4. 04ERPNetSuite (Oracle NetSuite)
    1. SuiteTalk REST
    Cloud
  5. 05ERPDynamics 365 (Microsoft Dynamics 365 Finance)
    1. OData v4 (data entities)
    Cloud
  6. 06CRMSalesforce
    1. REST API
    Cloud
§01—Pick any two

Pick any two.

Choose where an integration starts and where it lands. PartnerMCP sketches the plan it would build: the trigger, every step, and each system’s own object names.

Try
Salesforce → Priority
Sandbox
Opportunity · Closed WonCustomer lookupSchema mappingCreate / update customerCreate sales orderMonitor orderSync fulfillmentSync invoice statusUpdate Opportunity
Plan: Salesforce to Priority ERP. Salesforce to Priority ERP.
  1. Opportunity · Closed Won — Salesforce: Trigger · Change Data Capture
  2. Customer lookup — PartnerMCP: Account ⇄ CUSTOMERS
  3. Schema mapping — PartnerMCP: fields · products · prices
  4. Create / update customer — Priority ERP: CUSTOMERS
  5. Create sales order — Priority ERP: ORDERS + ORDERITEMS_SUBFORM
  6. Monitor order — PartnerMCP: status · delivery · invoice
  7. Sync fulfillment — Priority ERP: DOCUMENTS_D
  8. Sync invoice status — Priority ERP: AINVOICES
  9. Update Opportunity — Salesforce: fulfillment · invoice status
Product preview · sample data

PartnerMCP will

  1. Detect Opportunities that move to Closed Won in Salesforce.
  2. Match or create the customer in Priority.
  3. Create the sales order with its products, quantities and prices.
  4. Monitor delivery and invoicing in Priority.
  5. Write fulfillment and invoice status back to Salesforce.
  6. Retry temporary failures automatically.
  7. Send unresolved errors for review.
See Salesforce ↔ Priority ERP, field by fieldBuild this integration
§02—Directory

Find your systems.

Each one shows the interface PartnerMCP would connect through first and where the system runs. Systems with an integration page open it; the rest start an integration with that system selected.

55 systems · 8 categories

ERP15

ERP integrations

CRM10

CRM integrations

Commerce5

Commerce integrations

Finance7

Finance and payments integrations

Support4

Data8

Data integrations

Productivity6

Custom4

Custom and legacy integrations
§03—Custom systems

Connection types

Not in the directory? It doesn’t have to be.

PartnerMCP connects through the interface a system actually has, and learns custom systems from an OpenAPI spec, a GraphQL schema, a WSDL or a database schema.

Custom and legacy integrations
  • MCP
  • REST
  • GraphQL
  • SOAP
  • OData
  • Webhooks
  • Event streams
  • SQL
  • SFTP
  • SDKs
  • Custom APIs
  • Legacy APIs
  • On-premise applications

Product names and logos are trademarks of their respective owners. Their use indicates compatibility only and does not imply endorsement or partnership.

§04Start

Tell PartnerMCP what should connect.

Name your systems and describe what should happen. You’ll see the plan before anything is built.

Build an IntegrationConnect a custom system