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 Playground API Documentation
Welcome to the MCP Playground API documentation. The Playground APIs let you test and debug MCP servers directly — verifying connectivity, listing the tools an MCP server exposes, and invoking those tools with arbitrary arguments.Base URL
The MCP Playground APIs are served from a different host than the rest of the Enkrypt AI APIs:apikey header — your existing Enkrypt AI API key works against this host without any additional setup.
Purpose
Use the Playground APIs to validate a registered MCP server end-to-end before wiring it into a gateway. They are ideal for:- Verifying that a server’s configuration (command, args, OAuth) actually connects.
- Discovering which tools a server exposes and inspecting their input schemas.
- Invoking specific tools with custom arguments to debug behavior.
Offered APIs
Our API suite includes the following endpoints:- test-server: Connect to an MCP server and confirm it responds. Returns the count of tools available on success.
- get-tools: Connect to an MCP server and return the full list of tools it exposes, including each tool’s input JSON Schema.
- call-tool: Invoke a specific tool on an MCP server with the provided arguments. Returns the tool’s result content (or any error details).
Required Headers
apikey(orapi_key): API key for authentication. Required on every call.X-Enkrypt-MCP-Registry-Server: Required on every Playground call. Set to the registry server’ssaved_name.X-Enkrypt-MCP-Registry-Server-Version: Optional. Defaults tov1.
Obtaining an API Key
To get started with the MCP Playground API, you need to obtain an API key. Follow these steps:- Login: Access your account at app.enkryptai.com.
- Get API Key: Navigate to the API section to get your unique API key.
- Authentication: Use this API key in the
apikeyheader of your API calls.

