§00Integrations / Custom
Custom and legacy integrations: If it has an API, PartnerMCP can learn it.
Internal software rarely has a connector, and it doesn't need one. PartnerMCP reads what you already have — an OpenAPI 3.x spec, a Postman collection (v2.1 JSON or v3 YAML), a GraphQL SDL, a WSDL, OData $metadata or a database schema — treats it as a hypothesis, confirms it against your sandbox, and turns it into read, create and update capabilities with auth, limits and idempotency.
Systems
4 · first interface · runs
- Custom or legacy ERPSQL · SFTP · SOAP · On-premCloudOn-prem — start an integration with Legacy ERP
- Custom CRMREST · SQL · Cloud · On-premCloudOn-prem — start an integration with Custom CRM
- Custom internal softwareOpenAPI / REST · Cloud · On-premCloudOn-prem — start an integration with Internal app
- Warehouse management (WMS)REST · SFTP · EDI · Cloud · On-premCloudOn-prem — start an integration with WMS
What you can build.
Start from one of these, or describe your own. PartnerMCP plans every flow with the objects and interfaces of the systems you actually run.
- 01
Internal app ↔ CRM or ERP
Customers, orders and statuses kept in sync between Salesforce, Priority or SAP and your own system — without another custom integration service to maintain.
- 02
Legacy ERP through tables and files
Interface tables, SOAP services and EDI or CSV drops over SFTP, idempotent by file name and checksum because flat files carry no acknowledgements.
- 03
Database-backed applications
Change data capture from the application's PostgreSQL or SQL Server, read through a read-only role, instead of polling its tables.
- 04
Events in, APIs out
Signed webhooks from internal services verified and routed to the right system, with retries, idempotency keys and a dead-letter queue.
- 05
Behind the firewall
On-prem systems reached through the Edge Agent design (architecture concept): outbound-only connections, an allowlist of systems and operations, and credentials that stay in your network.
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.
Connect a custom system- MCP
- REST
- GraphQL
- SOAP
- OData
- Webhooks
- Event streams
- SQL
- SFTP
- SDKs
- Custom APIs
- Legacy APIs
- On-premise applications
Other categories.
A deal becomes an order, an order becomes a payment, and all of it lands in the warehouse. Integrations rarely stay in one category.
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.