Skip to main content
Every application on the MCP plane has one URL. What connects to it decides which of two paths you take.

​
An agent that already speaks MCP

Claude Code, Claude, Cursor, Codex, Gemini, VS Code — anything with an MCP client — is pointed at the application’s URL and nothing else. The Connect tab has the exact snippet for each; they all reduce to one of these shapes:
How the agent authenticates follows from the application: The Employee portal has its own URL and its own rule: a person signs in there with their NeuralTrust login, or sends their own personal key. No application key opens it. With a per-person sign-in, the agent sees the application’s servers — the same set every caller of that application sees — and each person connects their own upstream accounts on first use. Claude’s organisation connector, Copilot Studio and Windsurf have their own pages under Integrations.

​
Your own code: the TrustGate SDK

When you are writing the agent yourself, the URL is the easy part. MCP does not carry who a call runs as, which credential it travels with, or what to do when an upstream account is not connected, and the TrustGate SDK exists to answer those three. It needs the application’s key and nothing else: the gateway is found from the key.
connect() checks the run before it starts: the tools you need are there, and every server has an account. From there, hand agent.mcp to a framework that brings its own MCP client, or translate the tools for a model call.