Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.enkryptai.com/llms.txt

Use this file to discover all available pages before exploring further.

​
MCP Registry Servers API Documentation

Welcome to the MCP Registry Servers API documentation. This guide describes how to whitelist, configure, and manage MCP (Model Context Protocol) servers that can later be referenced by MCP Gateways.

​
Purpose

The MCP Registry Servers API lets you maintain a project-scoped catalog of approved MCP servers. Each registry server captures the underlying MCP configuration (command, arguments, OAuth, denied tools, tool guardrails) along with optional source metadata. Once a server is registered, it can be referenced by one or more MCP Gateways without re-declaring its base configuration. Registry servers belong to a project’s default registry. The registry is auto-created on the first server insert, so you do not need to manage it explicitly.

​
Gateway Overrides

The values you set on a registry server are defaults — when the server is referenced by an MCP Gateway, the gateway can override the following four fields per-server (without mutating the registry server itself):
  • input_guardrails_config
  • output_guardrails_config
  • tool_guardrails_config
  • enable_server_info_validation
Anything you do not override at the gateway is inherited verbatim from the registry server. This lets the same server be reused across dev/staging/prod gateways with progressively stricter guardrail policies. See the MCP Gateways API for the override surface and the expanded-config view that shows what the runtime actually consumes.

​
Offered APIs

Our API suite includes the following endpoints:
  • add-server: Whitelist a new MCP server with its base MCP configuration.
  • bulk-add-servers: Insert up to 100 servers in a single atomic batch (all-or-nothing).
  • get-server: Retrieve a registered server by saved_name and version.
  • modify-server: Update an existing registry server. Only provided fields are updated.
  • delete-server: Soft delete a registry server.
  • list-servers: List all registry servers in the project with pagination and an optional is_active filter.
  • list-gateways-by-server: Discover which gateways reference a specific registry server.

​
Required Headers

  • apikey (or api_key): API key for authentication. Required on every call.
  • X-Enkrypt-MCP-Registry-Server: Required for get-server, modify-server, delete-server, and list-gateways-by-server. Set to the server’s saved_name.
  • X-Enkrypt-MCP-Registry-Server-Version: Optional. Defaults to v1.

​
Obtaining an API Key

To get started with the MCP Registry Servers API, you need to obtain an API key. Follow these steps:
  1. Login: Access your account at app.enkryptai.com.
  2. Get API Key: Navigate to the API section to get your unique API key.
  3. Authentication: Use this API key in the apikey header of your API calls.
Let’s ensure safer AI together!