FAQs
The Digi Remote Manager REST API
Application Programming Interface is a traditional programmatic interface that requires customers to write and maintain custom integration code. The MCP
Model Context Protocol server provides a standardized, AI-native interface that allows AI
Artificial Intelligience assistants and AI Agents to discover and invoke Digi Remote Manager capabilities without custom wrapper development.
No. The Digi Remote ManagerMCP
Model Context Protocol server is fully hosted and managed by Digi. Users only configure their AI
Artificial Intelligience client to connect to the MCP endpoint.
Available capabilities depend on the tools exposed by the platform. The MCP
Model Context Protocol server includes query, analytics, monitoring, and supported operational tools. Tool availability is automatically discoverable by the MCP client.
While technically possible, it is recommended to generate separate API
Application Programming Interface keys for each user, assistant, or environment (for example, development and production) to improve security, auditing, and access control.
API
Application Programming Interface keys inherit the permissions of the Digi Remote Manager user account that created them. Role-based access control within Digi Remote Manager determines which tools and data the AI
Artificial Intelligience assistant can access.
No. The MCP
Model Context Protocol bridge proxies requests securely over HTTPS
Hypertext Transfer Protocol Secure to Digi Remote Manager. Device data is not persistently stored by the bridge.
Delete the API
Application Programming Interface key in Digi Remote Manager and then create a new one.
Yes. Partners and MSP
Managed Service Providers can generate API
Application Programming Interface keys within each authorized account and build AI
Artificial Intelligience Agents that operate within the permissions and scope of those accounts.
Any client or framework that supports the MCP
Model Context Protocol can connect to the Digi Remote Manager MCP server. See the Prerequisites for a list of MCP-compatible AI clients.
After configuration, submit a simple query such as "How many devices are in my DRM account?" A valid response confirms successful authentication and tool invocation.