§00System integrators
Keep the judgment. Hand off the plumbing.
PartnerMCP is an acceleration platform for integrators and consultancies. It drafts the discovery, the mappings, the tests and the monitoring; your engineers make the calls that need judgment, review every change and keep the client relationship.
| Stage | Scope | Discover | Map | Build | Test | Approve | Operate | Change |
|---|---|---|---|---|---|---|---|---|
| Your team | does the work | reviews | decides | reviews | reviews | decides | reviews | decides |
| PartnerMCP | reviews | does the work | does the work | does the work | does the work | does the work | does the work | |
| Client | does the work | decides | does the work |
| Stage | Your team | PartnerMCP | Client |
|---|---|---|---|
| Scope | does the work | reviews | does the work |
| Discover | reviews | does the work | |
| Map | decides | does the work | |
| Build | reviews | does the work | |
| Test | reviews | does the work | |
| Approve | decides | decides | |
| Operate | reviews | does the work | |
| Change | decides | does the work | does the work |
does the workreviewsdecides
The empty cell is deliberate: PartnerMCP never approves its own work.
PartnerMCP takes the repetitive work. You keep the judgment.
What clients pay an integrator for is the judgment. The weeks usually go somewhere else.
PartnerMCP takes on
- Reading API docs and metadata for both systems
- Drafting the mapping, with a confidence and a reason per field
- Writing the integration spec and its fixtures
- Running the fixtures in the sandbox on every change
- Watching production — retries, held records, schema drift
- Drafting each change request as a diff with its impact
Your team keeps
- Understanding how the client actually works
- Deciding who owns prices, customers and statuses
- Reviewing mappings and signing off changes
- The edge cases only domain experience catches
- The client relationship — and the change process
How a client project runs.
The client’s systems, the client’s approvals, your engineers leading — and PartnerMCP doing the drafting, testing and watching.
- 01
A workspace per client
Each client’s integrations live in the client’s own workspace — their connections, their credentials, their approvers. Your engineers work in it with the role the client gives them.
- 02
Describe it with the client
Write the intent with the client’s team, in their words. PartnerMCP restates what it understood and proposes the plan.
- 03
Make the judgment calls
PartnerMCP asks what the data can’t settle — which system owns pricing, how to recognise an existing customer, which statuses are final — and your engineers answer.
- 04
Prove it in their sandbox
Fixtures run against the client’s test instances: duplicates, missing data, rate limits, partial failures.
- 05
The client approves
Promotion to production waits for the people the client’s policy names. Every version stays deployable for rollback.
- 06
Operate and change
PartnerMCP watches production. Your team works the review queue and turns change requests into reviewed diffs.
# client: harbor-toolsenvironments: [sandbox, production]approvers: mapping-change: - partner-engineer - client-integration-owner production: - client-integration-ownerapply_then_report: # within your limits - retry-tuning - concurrency-reductionApprovals are policy, not habit: the client decides who signs off what, and your engineers work inside it.
An accelerator, not a replacement.
The enemy is complexity, not integrators. Here is what stays yours.
- 01
Your expertise
PartnerMCP drafts; your engineers decide. Every question it can’t answer from the systems is put to a person, not guessed.
- 02
Your client relationship
You lead the project. PartnerMCP works in the client’s workspace, under the access and approvals the client sets.
- 03
Your change process
Every change is a reviewed diff with its impact and test results — approved under the client’s policy, reversible by design.
- 04
The knowledge
The integration is a readable spec with its full history. Handover is a file and a log, not a person’s memory.
Partnering, during early access.
We work directly with each partner — alongside your engineers on the first client projects. There is no fixed programme to sign up to yet; partner terms are agreed individually.
Questions
Will PartnerMCP replace integrators?
No. It takes on the repetitive parts of integration work — reading documentation, drafting mappings, writing specs and tests, watching runs. The judgment, the review and the client relationship stay with you. The enemy is complexity, not people.
Who owns the client relationship?
You do. PartnerMCP works in the client’s workspace, with the access and approvals the client sets, and your engineers lead the project.
Which systems can we deliver on?
Anything with an API — ERPs such as Priority, SAP, NetSuite and Dynamics 365, CRMs, commerce, payments, data warehouses and custom systems. Systems behind a client’s firewall are reached through a path the client approves — a VPN or reverse proxy they already run, or the Edge Agent, an outbound-only architecture concept.
What does the client get at handover?
A readable, versioned spec with its fixtures and its full history: what the integration does, and why each change was made.
How does partnering work today?
During early access we work directly with each partner, alongside your engineers on the first client projects. Partner terms are agreed individually.
§06Partner
Bring your next client project.
Tell us about your practice and the systems your clients run. We’ll show you what a project looks like with PartnerMCP.