MCP Server: Toolsets
Toolsets
The Magic Suite MCP Server groups the actions it offers into toolsets. Every toolset is available to every client; what a given caller can actually do is decided by the Magic Suite API, based on the rights of the user who owns the API Token.
Available toolsets
| Toolset | Tools | Purpose |
|---|---|---|
| OData | odata_entity_sets, odata_query, odata_create,
odata_update, odata_delete |
Read and change any entity the Magic Suite API exposes. |
| Diagnostics | health_check |
Confirm the server can reach the Magic Suite API, and report the authenticated user and tenant. |
Diagnostics
health_check takes no arguments and returns the state of the connection along with the user and
tenant your API Token resolves to. It is the quickest way to confirm a client is connected as the identity you
intended.
Connection-specific toolsets
Toolsets that act on a configured Connection - Jira, for instance - are not yet available. They will follow the same principle as the OData toolset: the MCP Server holds no permissions of its own, and every call is carried out by the Magic Suite API on behalf of the API Token's user.