Skip to content

§00Start building

Early access

Describe the integration.

Four questions. PartnerMCP sketches the plan as you answer — our engineers review every request and follow up by email.

Step 1 of 4: What systems do you want to connect?

Pick every system involved. PartnerMCP works out which way the data flows from what you describe next.

Type to filter. Enter adds the first match.

Or start from

ERP14

CRM10

Commerce5

Payments & finance6

Support4

Data8

Productivity6

Custom1

Nothing picked yet.
§01—Before you send

What happens after you send it.

What happens after I send this?

PartnerMCP’s engineers review the systems and the plan you described, then follow up by email. PartnerMCP is in early access, so every request is read by a person.

Is the plan preview the real plan?

It is a sketch from PartnerMCP’s planner, made from the systems you name and the words you use. A real plan starts from your systems’ own schemas once they are connected, and every plan is reviewed before anything is built.

Do I need API credentials or documentation now?

No. This page doesn’t connect to anything — it only sends your request. Access to your systems comes later, starting in a sandbox, with permissions you approve.

Can I connect a system that isn’t listed?

Yes. Choose Other / custom system and say what it is. If it has an API, PartnerMCP can learn it — from an OpenAPI spec, a Postman collection, a GraphQL schema, a WSDL or a database schema.

What if our ERP runs on-premise?

PartnerMCP is designed to reach systems inside your network through the Edge Agent — a small agent that connects out over HTTPS, so no inbound ports need to be opened.