Datasheet
| Property / Parameter | Value / Detail | Explanation |
|---|---|---|
| Endpoints | ||
| Primary API URL | https://api.sistrix.com/mcp/ | Main end point for all requests. |
| Authentication | ||
| Environment Variable | Supported | Key is read from a env. variable. |
| Bearer Token | Supported | Key is sent in the Authorization: Bearer header. |
| Header Parameter | Supported | Key is sent in a custom HTTP header. |
| Direct Prompt | Supported | The user writes the key in the prompt. |
| Account access | ||
| Premium | Full | |
| Professional | Full | |
| Plus | Limited | |
| Start | - | |
Authentication
To access data via the MCP server, your chatbot or tool needs to authenticate using a valid SISTRIX API key. This API key ensures that all requests are securely attributed to your account and that credit usage can be properly tracked.
There are two main ways to provide authentication:
Bearer Tokens
The MCP server uses Bearer Tokens to authenticate API requests. This means your API key is sent in the HTTP header like this:
Authorization: Bearer <YOUR_API_KEY>Just replace <YOUR_API_KEY> with your SISTRIX API key. This allows the MCP server to securely access your data on your behalf.
Environment Variable
The MCP server can also read your API key from an environment variable. In this setup, the key is not passed directly in the header, but provided like this:
"env": {
"SISTRIX_API_KEY": "<API_KEY>"
}Replace <API_KEY> with your actual SISTRIX key. The server will use this variable to authenticate requests automatically.
Custom Header
In some cases, it’s better to use a custom HTTP header for authentication. The MCP server fully supports this method.
To enable it, simply use the header name X-API-Key and provide your SISTRIX API key as the value:
"X-API-Key": "<API_KEY>"Direct Prompt
You can also enter your API key directly into the prompt.
Simply paste your SISTRIX API key into your message. This allows the assistant to authenticate and access the MCP server on your behalf.
This method is quick and easy, especially for one-time queries or testing setups.
