// With request headers
curl -X GET https://api.zatomic.ai/v1/mcp \
-H "X-Api-Key: {API key}"
curl -X GET https://api.zatomic.ai/v1/mcp \
-H "X-Api-Key: {API key}" \
-H "X-Api-Client: {API client ID}"
// With querystring parameters
GET https://api.zatomic.ai/v1/mcp?api-key={API key}
GET https://api.zatomic.ai/v1/mcp?api-key={API key}&api-client={API client ID}
Authentication
An API key is required to authenticate all requests to the MCP server. You can view and manage your API keys in your Zatomic account.
Authentication to the MCP server is handled by setting the X-Api-Key request header or by using the api-key querystring parameter. If both are given, the api-key querystring parameter will be used.
You may also require users of the MCP server to make requests with an API client ID. Similar to an API key, an API client ID is a unique identifier that grants its user access to the MCP server, thus allowing account admins the ability to track who or what is using the MCP server on their behalf.
If API client IDs are required for your account, in addition to your API key, you must make MCP calls by setting the X-Api-Client request header or by using the api-client querystring parameter. If both are given, the api-client querystring parameter will be used.
Requiring API clients is managed in your Zatomic account.
Authenticated Request