Viseon icon against clear background in webp format

VISEON MCP Gateway

Zero Trust MCP gateway · Secured by identity

One controlled door between your AI and your business systems.

VISEON MCP Gateway turns your AI policy into something that is enforced on every call: internal use only, least-privilege access, a full audit trail, and approval before any data flows.

AI assistants such as Claude reach your CRM, your service desk and your other systems through MCP servers. VISEON MCP Gateway sits between them. Every request carries the person’s own Microsoft Entra ID sign-in, every call is checked against that person’s current role, and every call is written to a tamper-evident audit log. The gateway has no public address, and the MCP servers behind it can be reached by nothing else.

  • No public address
  • Microsoft Entra ID sign-in
  • Default-deny, role by role
  • Tamper-evident audit log
  • OpenZiti Zero Trust network

0

public addresses. The gateway and the MCP servers behind it are dark services.

1 min

for a removed role to stop working. Role assignments are read from Entra every minute.

Every

call re-authorised and written to the audit log, with who made it.

0

system credentials on the user’s device or in the gateway. They stay with the MCP servers.

Why a gateway

An AI policy is only as strong as what enforces it.

Most organisations now have an AI policy with a clause on agentic AI and MCP servers. Without a gateway, that clause is a promise. An assistant connected straight to an MCP server acts with the server’s own system credentials, sees everything those credentials can see, and leaves no record of which person asked for what.

The gateway makes the clause enforceable

  • Internal use only. Only enrolled devices can reach the gateway at all.
  • Least-privilege access. Each role sees only the tools it has been granted.
  • Full audit. Every call is logged with the person who made it.
  • Approval before data flows. A system is connected only after approval and a data protection impact assessment (DPIA).

Architecture

Dark by default. Reachable only by identity.

The gateway runs on an OpenZiti Zero Trust network from NetFoundry. It is published as a dark service: no public address, no open inbound port, and reachable only from enrolled devices.

  • Two dark services, not one. The MCP servers sit behind a second dark service that only the gateway can dial. Nothing else can reach them.
  • Credentials stay put. The system credentials for your CRM and service desk never leave the MCP servers.
  • Your token stays with you. The gateway checks the person’s sign-in and vouches for who is asking; the person’s own token is never passed on.
  • Traced end to end. Trace IDs and timings follow each call across the gateway and the MCP servers.

Design

Every call checked. Nothing assumed.

Your own sign-in

Every request carries the person’s Microsoft Entra ID sign-in, and the gateway validates it before anything else happens.

Roles kept current

Role assignments are read from Entra every minute, whether given directly or through groups, so a removed role stops working within a minute.

Default-deny

Each role sees only the tools it has been granted, and every call is authorised again, not just the first.

Read-only by design

Everything is read-only except one deliberate case: people enter their own timesheets, confirmed in two steps, with the gateway vouching for who is asking.

Assurance

Proof of who asked for what.

When an auditor, a data protection officer or a director asks what the AI did, the answer is in the log, not in anyone’s memory.

A tamper-evident audit log

A hash-chained log names who made every call, with trace IDs and timings across the gateway and the MCP servers. A changed or deleted entry breaks the chain.

A separate admin console

A web console on its own dark service, with Entra sign-in, manages versioned configuration and shows the audit trail and performance.

Getting connected

Your people keep the AI tools they already use

Enrol the device

The device joins the Zero Trust network, which is what makes the gateway reachable at all.

Add the gateway

In Claude Code, add the gateway’s address. In Claude Desktop’s chat, a small VISEON extension on the device makes the connection.

Sign in

People sign in with their Microsoft Entra ID account and see the tools their role allows, nothing more.

Proof, in use

We run it first. On our own systems.

Differentia Consulting’s own AI assistants reach its business systems through VISEON MCP Gateway.

  • In front of the MCP servers for SuiteCRM and osTicket.
  • Used from Claude Code and Claude Desktop, with Microsoft Entra ID sign-in.
  • Read-only, except people entering their own timesheets.

The gateway governs access

Which identities may reach which MCP server, and which tools each role may use.

VISEON for Enterprise governs meaning

What each server’s data means, in one canonical ontology. The VISEON for Enterprise MCP hub sits behind the gateway.

Questions

What people ask first

What is VISEON MCP Gateway?

VISEON MCP Gateway is the single, controlled door between your AI assistants and your business systems. AI assistants reach your systems through MCP servers, and the gateway sits in front of them: it checks who is asking, allows only the tools that person’s role has been granted, and logs every call.

Can anyone on the internet reach the gateway?

No. The gateway is a dark service on an OpenZiti Zero Trust network from NetFoundry, with no public address. Only enrolled devices can reach it, and only the gateway can reach the MCP servers behind it.

How quickly does removing someone’s access take effect?

Within a minute. The gateway reads role assignments from Microsoft Entra ID every minute, whether they are given directly or through groups, and authorises every call again.

Can the AI change data in our systems?

Only where you decide it may. Access is read-only by default. The one write case in use today is people entering their own timesheets, confirmed in two steps, with the gateway vouching for who is asking.

Which AI tools work with the gateway?

Claude Code connects by adding the gateway’s address and signing in. Claude Desktop’s chat connects through a small VISEON extension on the device.

Put your MCP servers behind one controlled door

Tell us which systems your AI assistants need to reach, and we will scope the gateway with you.

Or email [email protected] · Built by Differentia Consulting, enterprise data specialists since 2002.