Register an MCP server

Register an approved target and verify it reaches runtime.

Before you start

Have the endpoint, owning team, required transport, network route, and upstream authentication requirements available. Choose a non-production target for your first registration.

Procedure

1. Open the server registry in the console and begin a new registration. Give the server a stable name and an accountable owner.

2. Enter the endpoint and choose the supported transport and route. Keep credential material out of the server definition; use the approved credential reference or binding.

3. Run the available connection and compatibility checks. Review the discovered tool set and any security or transport warnings.

4. Continue to Access. Under Clients → Amelfi, select the authorization server that signs in callers and enter its configured OAuth API audience. A saved workspace default fills these fields for new servers. Save client access. This selection does not create an API in your identity provider.

5. Under Amelfi → Server, choose the authentication required by the upstream server. Use a service account for shared server credentials or delegated access when each caller must authorize their own upstream account. A server that requires no upstream credentials still needs its client access configured.

6. Set Rate limits, review Access policy, then continue to Publish. Complete any approval required by your workspace. Publishing saves the reviewed configuration and waits for the gateway to accept it.

For hosted workspaces, gateway setup starts automatically. You can continue configuring access while setup runs. If setup fails, use Retry gateway setup. Check gateway status refreshes progress; reloading the page preserves the selected setup step.

Verify the result

When Published appears, open Test call and choose a read-only operation. Review its arguments, then select Send test call. If the operation requires an explicit read-only review, complete that review before sending it.

The test runs through the deployed gateway. Wait for Your gateway is ready, which requires the audit receipt for that exact invocation. If the call has finished but its receipt is pending, use Check receipt to observe its status. This check does not send another tool call.

Published configuration alone does not complete verification. The gateway must remain ready and the test receipt must match the current publication.

If it does not work

If publication is waiting for runtime, check gateway setup progress. For a rejected upstream credential, return to Access, correct Amelfi → Server, and publish the updated configuration before testing again. Review the test’s technical details when you need the failure reason.

Read the related concept or consult the Admin API for exact request fields.

Implementation reference

Read the source contract.