---
title: "Build your own integrations: MCP, API and custom development"
description: "Configure an existing integration or connect your own system through MCP, an API or custom development: what you do, where we help and what to consider."
source_name: "Gen8"
source_url: "https://gen8.app/en/bouwers/koppelingen/"
site_home: "https://gen8.app/"
source_description: "Managed AI service for SMEs. We set up, connect and manage; you stay in control."
locale: "en"
copyright: "© 2026 Gen8 VOF · Dutch Chamber of Commerce 92978789 · Delft"
published_at: "2026-09-25T09:42:11.273Z"
modified_at: "2026-10-21T18:02:57.994Z"
---

# Build your own integrations: MCP, API and custom development

## Connect your own systems through *the right route*

Many systems already have a Gen8 integration. For your own order system, industry software or database, we choose a route together: an MCP server, API integration or custom development.

[Book an introductory meeting](<https://gen8.app/en/contact/>)[View the integrations](<https://gen8.app/integraties/>)

- Least permissions
- Encrypted credentials
- Processing in the EU

## Five routes to a system

Routes differ in maturity and effort. The site states the route for each integration; for a system without one, we choose the route during guidance.

| Route | When | What to consider |
| --- | --- | --- |
| Native | The platform has its own tools for the system | Configure with the least permissions the work allows |
| Configured | Existing tools configured for your environment | Record fields, permissions and exceptions |
| MCP | An external MCP server makes the system's functions available | Who runs the server and where; the server determines what is possible |
| API | The system has a documented API | Full control of fields, but more development work |
| Custom development | No API: only files, a database or a portal | Agree on maintenance, or the integration will eventually break |

## What you do and where we help

Configuring an existing integration needs no programming. A route that does not exist yet does require technical knowledge or our help.

During guidance, we first check whether a route already exists. If not, we weigh MCP, API and custom development together and record who maintains the integration afterwards.

The full considerations for each route are under [MCP, API and custom development](<https://gen8.app/en/integraties/mcp-api-maatwerk/>).

Access belongs to the organisation

- Credentials are encrypted at rest and are not included in workflow text.
- Integrations and permissions belong to the organisation where the workflow runs, not the workflow itself.
- A workflow receives the least access it needs to do its job.

## Frequently asked questions about your own integrations

Is an MCP server secure?

It depends on who runs it and where. A server run by the vendor is different from one run by an unknown party. Your administrator must assess that, and we explicitly raise the question.

Who maintains the integration afterwards?

We agree and record that upfront. Maintenance is a real cost for custom development: an integration no one maintains eventually breaks.

Can we start without an API?

Often yes. File exchange or a read connection is less elegant, but works and can be checked.

## Which system do you want to connect?

Name it in an introductory meeting. We explain which route fits, what it requires and who maintains it.

[Book an introductory meeting](<https://gen8.app/en/contact/>)[All building topics](<https://gen8.app/en/bouwers/>)

- Response within one business day
- Starts with a conversation