Who opens it
People enter with their NeuralTrust login or your identity provider. From code
or a client that cannot sign in, a person uses their own
personal key instead — it opens their portal and nothing else.
An application key cannot open it: the portal is a person’s, and a key that runs
as an application is refused.
What a person sees
Two sections, MCP Catalog and Models Catalog. A Hybrid gateway has no models through the portal, so there it is the MCP Catalog alone. The Personal key button in the header serves both. In the MCP Catalog, the filter beside the search switches between All — everything they may install, each card showing whether it is installed, waiting on their account, or outside their access — and My access: what they hold, with the state of their own account on each, and a Connections list of the servers that want a personal account. Opening a server shows what it does, how many tools it brings, and one Next step line — connect, reconnect, finish setup, request access, or nothing to do. That line is the whole instruction; there is nothing else to read. The Models Catalog is covered in Models below.Installing
Installing a catalogue server creates or reuses one registry entry per catalogue code on the gateway. What is per person lives elsewhere: their account on a forwarded-auth server, vaulted under their identity, and any per-user setup values a server’s URL is built from. An install answer is a state, not a success flag:
The same states name the badges in the portal: Installed, Connect,
Reconnect needed, Pending, Needs admin setup.
Disconnecting an account
A person can take back an account they linked. On the server, under Connections, Disconnect deletes the account TrustGate holds for them: its tools stop working for them until they connect again, and the server stays installed. A server that uses one account shared by everyone shows no Disconnect — that account is an administrator’s, and is disconnected from the registry.Models
The Models Catalog has a card for each LLM provider the gateway has, and one for each provider of TrustGate’s catalog it has not connected yet. Each says what it serves (Chat, Embeddings, …) and where the person stands:
Opening a provider they have shows How to call them: the base URL, a model
picker, and a snippet for the language they pick. Any OpenAI-compatible client
works — point it at the base URL and send the personal key.
Request access asks for one provider, with a reason in the person’s own
words, and lands in Approvals
next to the MCP requests. Approving gives them that provider’s models, all of
them. A provider the gateway has not connected yet can be asked for too: the
admin connects it, then approves.
Which models a person reaches follows their Access
level, and it is enforced on every call: a model outside it is refused before
the gateway calls the provider, however many other people use it.
Personal key
One key per person and gateway, for their models and their MCP tools, on a SaaS gateway (a Hybrid one has none). The Personal key button in the header creates it, rotates it or revokes it:- It is shown once, when it is created or rotated. Afterwards only its first and last characters are, and losing it means rotating it.
- It lasts up to 90 days. A rotation keeps what the key reaches; the old secret stops working at once.
- Use it has a ready snippet for the TrustGate SDK, the OpenAI SDK and an MCP client.
/store/mcp (send it as X-AG-API-Key, x-api-key or
Authorization: Bearer) and their models through the gateway, and nothing an
application holds. From code, the TrustGate SDK takes
it as is. An admin sees whether someone has one in Access, and can revoke it
there.
From an MCP client
Everything a person installs is on one fixed URL —/store/mcp on the gateway’s
MCP host, the same address for everyone. Pointing Claude Code, Cursor or any
other MCP client at it runs an OAuth sign-in the first time; a client that only
sends headers uses the person’s personal key instead. After
that the client sees that person’s own catalogue, and a tools changed
notification whenever they install, connect or lose a server.
It is an MCP endpoint like any other, so the client also gets the gateway’s own
tools — the inventory, and
these:
An agent with no tool for what it was asked is meant to search here first.
Installing through the portal is what keeps the new server governed, instead of
the person wiring an upstream MCP URL into their client.
Every request a tool files carries the person’s own words. The tools take no
reason: an agent asked for one would write it from its own task and an approver
would read it as the person’s, so the link opens a form the person fills in.
The page a connect link opens ends with Close and go back to the app the
link came from. Some clients only re-read their tool list when asked to, or when
a conversation starts: if the new tools do not appear, refresh the connector’s
tools in the client.
Open or curated
A gateway’s default access decides what the Employee portal offers everyone who has no level of their own:
A level set on a person or a group overrides the default. The effective level is
evaluated on every request, so a change lands immediately.
Curated is the setting most organisations end at. It is not a refusal of
everything else — it turns “I need this” into a request with a reason attached,
decided by an admin, and approving a group instead of a person is how the same
request stops arriving.