MCP servers

Private and shared servers

Learn how the CLI saves tested servers to your private list, and how to share a server with your organization or stop sharing it.

The MCP Servers page has two tables. Shared Servers lists the servers everyone in your organization can use. My Servers lists the servers only you can see. This article explains how a server lands in My Servers and how to move a server between the two.

A server you add with Add new on the page also lands in My Servers. The exceptions are a stdio server and a save that matches a server that is already shared. Both stay in Shared Servers, and the page says so after you save.

Servers the CLI saves for you

After you run guardian test on an http server and the result uploads to Guardian, the CLI saves that server to My Servers. There is no prompt. This applies to a server you pass with --target-url, with --config, or that comes from an http entry in your MCP client config.

  • What is saved. The full URL, including its path and query, and the header values, after any ${env:...} references and --header-env values are filled in. They are stored encrypted, and only you can see them.
  • Running it again. Testing the same server again updates the same entry instead of adding another one.
  • What it needs. A role that can run tests: Admin, Manager or Engineer. The CLI prints a line saying the server was saved.
  • When it does not save. Never for guardian scan, a stdio server (--stdio), a run of your CLI default, or a --plan run. Never when the run was not uploaded (--no-upload, or guardian config set upload false). Never when the URL still has ${ in its path or query.
  • Limit. Up to 50 servers in My Servers per person.

There is no separate switch to stop saves. Turn off uploads instead: pass --no-upload for one run, or run guardian config set upload false for all runs. Put tokens in headers, not in the URL. If you don't want a server stored, run it with --no-upload.

Share a server with everyone

Select Share with everyone on a row in My Servers. Admins, Managers, Engineers and Security members can do this.

The server moves to Shared Servers and follows the usual shared-server rules (see Before you start): teammates who can run scans and tests use your saved credentials without seeing them, and you still see the secrets you typed.

Sharing can fail for these reasons:

  • A shared server with the same Label already exists. Rename your server, then share it.
  • Your organization has reached its limit of 100 shared servers.
  • The server is blocked, so Guardian won't run it.

Stop sharing a server

Select Stop Sharing on a row in Shared Servers. Admins, Managers, Engineers and Security members can do this on any shared server.

The server goes back to My Servers of the person who entered its credentials, which may not be the person who selected the button. Everyone else no longer sees it. Their CLI default and Safe mode setting for that server are removed. Run history is kept.

Stopping can fail when:

  • The person who entered the credentials is no longer an active member with one of those roles.
  • The server is a stdio server.
  • That person already has a private server with the same address.

If that person already has a private server with the same Label, the returned server gets " (2)" added to its Label.

Delete your own server

You can always delete servers in My Servers, whatever your role. Admins can't see or delete other people's private servers. They are removed when that person is removed from the organization.