Skip to main content
Set Security Type when you create or edit a server.

​
Public

Anyone with the URL can call the server. Use it for public data.

​
Unlisted

Copy the full endpoint from the server page. Keep it private. Anyone with this URL can call the server.
Regenerating the secret key changes the URL your clients need.

​
API Key

Copy the API Key from the server form. Send it in the Authorization header:
The server validates the generated key. After regenerating it, update your clients.

​
OAuth

Enter your OAuth Authorization Server URL. This is a metadata URL, such as:
The form checks for issuer, authorization_endpoint, token_endpoint, registration_endpoint, and jwks_uri. Configure your authorization server first. TryMCP uses its metadata to verify access tokens. Use a client that supports the provider’s OAuth flow.

​
Connect

The Integration tab generates client configs for your server. API Key configs include the Authorization header. Unlisted configs include the secret URL. Treat copied configs as credentials when they contain a key.