Skip to main content
An MCP entry exposes a server’s tools and resources to the agents behind your gateway. What distinguishes one entry from another is who supplies the credential.

Three kinds, by who signs in

The choice is not really about convenience. A shared credential gives every caller the same upstream permissions and one line in the destination’s audit log; per-user accounts give each person their own permissions and their own line. For anything that reads or writes real data — issues, repositories, customer records — that difference is usually the whole decision.

Registering your own server

A custom entry points at either an MCP endpoint or an HTTP API. An MCP server URL is an http(s) streamable-HTTP endpoint. Name it, point at it, choose how it authenticates. An OpenAPI document is how you get tools out of an API that has never heard of MCP. Give TrustGate a URL to an OpenAPI 3.x document and it compiles the operations into tools. Validation runs before you can save and fails at a named stage — fetch, parse or compile — and on success reports how many tools it produced. That count is the number to read: a document that compiles to far fewer tools than the API has operations usually describes them too loosely for them to be exposed safely, and the fix is in the spec, not here. An API base URL overrides servers[0] from the spec, for the common case where the document is published with a placeholder host.

Authentication modes

Manual OAuth registration also takes optional scopes, an RFC 8707 resource indicator, and whether the token endpoint expects the secret as basic auth or as a form field. When you edit an entry, blank secret fields mean keep what is stored. You will not clear a credential by not retyping it. An entry that forwards the caller’s own token cannot be switched to another mode after the fact.

What people can install for themselves

A gateway’s Portal is either open — anyone may install anything in it — or curated, where each person installs from the resources assigned to them. On a curated gateway, wanting something outside that assignment produces a request rather than a refusal. Approving it grants the server to the person who asked, or to one of their groups; the second turns a one-off into a standing rule and is usually what you want the third time the same request appears. Requests and their history live under Access, which is also where the assignments themselves are set.

Tools are exposed here, governed elsewhere

An entry exposes whatever tools its server advertises. Which of them a given application may actually call is a policy question — see tool governance.

Every server

TrustGate ships connection details for 198 MCP servers, which makes adding one a credential decision rather than an integration project. Anything not here is a custom server: an MCP URL, or an HTTP API described by an OpenAPI document.

Reading the table

Authentication is the column that decides how much work an entry is: You supply marks servers that are per-tenant rather than one global URL — your subdomain, your workspace, your region. Two things this list does not tell you. Whether a person may install any of these is Access. What an application may call once it is installed is tool governance.

Cloud platforms

Developer tools and source control

Observability and incidents

Data and analytics

Project and product management

Productivity and docs

Communication

Customer support and ITSM

Sales, CRM and marketing

Finance and payments

Security and identity

Web, CMS and commerce

AI, search and automation