For ChatGPT, use the custom MCP server at https://mcp.safeguard.sh/mcp with OAuth unless you have a reason not to. A Custom GPT Action that imports Safeguard's OpenAPI schema also works, but it exposes a smaller set of tools and sends one shared key for everyone who uses that GPT.
The two routes side by side
| Custom MCP server | Custom GPT Action | |
|---|---|---|
| Address | https://mcp.safeguard.sh/mcp | https://mcp.safeguard.sh/openapi.json |
| Sign in | OAuth, each user | One MCP key, pasted once |
| Tool set | Full enabled set for your workspace | Smaller set from the schema |
| Acts as | The signed in user | The person who created the key |
Safeguard's documentation names the MCP server as the recommended path and the Action as the alternative.
Route one: custom MCP server
- Create or sign in to your Safeguard account at app.safeguard.sh.
- In ChatGPT, open Plugins, select the plus button, then Add custom MCP server.
- Enter a name such as Safeguard Security and a description.
- Under Connection, enter
https://mcp.safeguard.sh/mcp. - Choose OAuth. ChatGPT registers itself with Safeguard, so there is no client ID or key to copy.
- Review the risk warning, select I understand and want to continue, then Create as a plugin.
- When ChatGPT sends you to Safeguard, check the app name and the host the authorization code goes to, then click Authorize access.
Account and workspace policies apply to adding custom MCP servers. If you do not see the option, ask your ChatGPT workspace administrator.
Route two: Custom GPT Action
- Create a Custom GPT, open Configure, then Actions, then Create new action.
- Choose Import from URL and enter the OpenAPI schema address above.
- Under Authentication choose API Key with Auth Type Bearer, and paste a Safeguard MCP key.
- Save the GPT.
The key is created in Safeguard under Settings, then Developer, with the key type MCP key.
The risk in route two
The Action uses the one key you paste for everyone who can use that GPT, and the key acts as you across the workspace. If you share the GPT, you share your access. Keep the GPT private, and revoke the key under Settings, then Developer, if the GPT ever leaves your control. Revocation takes effect within a minute. Our MCP key safety checklist has the details.
Which to choose
Pick the MCP server when several people will use it, when you want actions tied to individual identities, or when you want the full set of tools your administrator has enabled. Pick the Action only when your ChatGPT setup cannot add a custom MCP server and a private, single user GPT is enough.
Either way, tools are gated per workspace. A new workspace starts with six read-only tools. See why only six tools show up.
Quick check
Does either route need a package install?
No. Safeguard hosts the server and publishes no npm package or local bridge for it.
Can two people share one Custom GPT Action safely?
Not in the sense of separate identities. Everyone using it acts through the one key, which acts as its creator.
Sources
Last reviewed: 19 October 2026.
