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. |
| OAuth | Supported | Authentication is handled via the OAuth 2.0 protocol. |
| 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 | Full | |
| Start | Full | |
Authentication
To access data via the MCP server, your chatbot or tool needs to authenticate. This ensures that all requests are securely attributed to your account. While traditional API requests consume credits, using the SISTRIX MCP server does not consume any of your API credits.
There are two main ways to provide authentication:
Please note: Authentication with a raw SISTRIX API key is being phased out. From 31 August 2026, the MCP server will only accept connections that are authorised via OAuth 2.0. If your MCP client is still configured with an API key, you will find a notice at the end of every answer. See Switching from API key to OAuth below.
1. OAuth 2.0 (Recommended)
The most modern and secure way to connect. Instead of handling sensitive keys, you simply authorize the connection via your SISTRIX login.
- User-Friendly: No manual copying of long strings.
- Secure: Access is managed through secure tokens rather than static keys.
2. SISTRIX API Key (deprecated)
For tools or custom setups that do not yet support OAuth, you can use a valid SISTRIX API key until 31 August 2026. After that date, requests authenticated with a raw API key will no longer be answered, regardless of whether the key is passed as an api_key parameter, in a Bearer header, in a custom header or via an environment variable. Existing keys remain valid for all other uses of the SISTRIX API, only access to the MCP server is affected. Please switch your setup to OAuth 2.0 in good time. There are several ways to provide this key:
Switching from API key to OAuth
Changing your setup takes less than a minute and does not affect your data or your API credits:
- Open the MCP or connector settings of your client (for example Claude or ChatGPT) and remove the SISTRIX server together with the API key stored in its configuration, this includes the api_key parameter, the Authorization: Bearer header, the X-API-Key header and the SISTRIX_API_KEY environment variable.
- Add the server again using the URL https://api.sistrix.com/mcp/ and select OAuth as the authentication method.
- Your client will now guide you through the SISTRIX Toolbox login. Confirm the access request with Allow.
- That’s it, your client reconnects, the list of available endpoints appears, and the notice at the end of your answers disappears.
Step-by-step instructions for the two most common clients can be found under Setting up Claude and Setting up ChatGPT.
The notice in your answers
As long as your client authenticates with a raw API key, the MCP server appends the following notice to every answer:
NOTICE: this call authenticated with a raw SISTRIX API key (api_key parameter,
Bearer or X-API-Key header). Raw-key access to this MCP server is being phased
out and will stop working on 2026-08-31. To keep access, remove the API key from
your MCP client configuration and re-add the server — your client will then guide
you through the SISTRIX Toolbox login (OAuth). This notice has no effect on the
result above.
The notice is purely informational. The data above it is complete and correct, and neither the request nor your credits are affected. It is no longer shown once your connection is authorised via OAuth.
