- Endpoint
- Enforces policy
Qastel MCP Gateway
Govern what your developers' AI agents send to and receive from MCP servers, without changing the agent or the server.
Why agent tool calls are the newest blind spot
An AI agent with MCP servers attached can read files, query internal systems and send what it finds to a model, and none of it crosses a proxy, an identity provider or a managed browser. The Qastel MCP gateway sits between the agent and each server, so every tool call is checked against your policies and every decision is recorded.
Coding agents and desktop assistants now come with tools. A developer adds an MCP server for the file system, the ticket tracker or a production database, and the agent starts moving data between them and a model. It is the most capable AI in the building, and the least visible.
A wrapper, not a rewrite
The gateway is a small command-line program that wraps each server entry in the agent's configuration. The agent still speaks ordinary MCP and the server launches exactly as before, with the same arguments and environment. It works with Claude Code, Claude Desktop, Cursor, VS Code and Windsurf.
What you get
Discover, assess, control, comply.
What the Qastel MCP Gateway adds, at each of the four stages.
Discover
Tool calls between developers' agents and their MCP servers, on a channel no proxy or identity provider sees.
Assess
Each server checked before it connects, so one your policies exclude never starts a session.
Control
Allow, redact, warn or block on every tool call, with the policies you already wrote for every other channel.
Comply
Every decision recorded on the policy's activity: blocked, redacted, warned or allowed.
The same policies, one more channel
Each tool call is checked twice (the arguments on the way out, the result on the way back) by the same policies and the same decision service as the browser and the desktop. Every decision is recorded, whether it blocked, redacted, warned or allowed.
What Qastel reads
From Qastel MCP Gateway
- Each MCP server, before it connects
- Every tool call's arguments, on the way out
- Every tool result, on the way back
Your policies decide what passes, in and out. Every decision is recorded.
Deploy the Qastel MCP Gateway
The gateway package is available from Qastel Support. Each developer machine enrols once with an install code, and the gateway then stands in for each MCP server in the agent's configuration.
What you need before you start
- Developer machines with Node.js 20.11 or later
- An agent that supports MCP: Claude Code, Claude Desktop, Cursor, VS Code or Windsurf
In Qastel, create an install code, and get the gateway package from Qastel Support.
On each developer machine, enrol once with the code, then run the gateway's install command to wrap the agent's MCP servers.
See what your AI is doing, wherever it runs.
Your policies, applied where the AI runs. Every decision recorded.