Build your own integrations: MCP, API and custom development
About this source
Gen8
Source: Build your own integrations: MCP, API and custom development
Managed AI service for SMEs. We set up, connect and manage; you stay in control.
© 2026 Gen8 VOF · Dutch Chamber of Commerce 92978789 · Delft
Builders · integrations
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.
- Least permissions
- Encrypted credentials
- Processing in the EU
Routes
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 |
Build together
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.
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.