Loading...
Didlogic MCP server provides LLMs access to Didlogic API for managing SIP accounts, call history, and transactions, with varying transport modes.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
Didlogic MCP server provides LLMs access to Didlogic API for managing SIP accounts, call history, and transactions, with varying transport modes.
The Didlogic MCP server offers valuable functionality but requires careful management of the API key. While IP restrictions add a layer of security, the potential for unintended actions by the LLM necessitates thorough testing and monitoring. Running in read-only mode where possible will greatly reduce risk.
Performance depends on the Didlogic API's responsiveness and the network connection. Consider optimizing prompts for efficiency.
Cost is primarily determined by Didlogic API usage. Monitor API call volume to avoid unexpected charges.
pip install didlogic_mcpDIDLOGIC_API_KEYBalance management toolsTools to manage the balance of Didlogic accounts.
Modifying account balances carries financial risk.
SIP account (sipfriends) managementTools to manage SIP accounts, including creation, modification, and deletion.
Improper management can disrupt communication services.
IP restriction managementTools to manage IP restrictions for enhanced security.
Incorrect configuration can block legitimate access.
Purchases managementTools to manage purchases made through the Didlogic API.
Managing purchases involves financial transactions.
Call history accessTools to access and retrieve call history data.
Read-only access to call history.
Transaction history accessTools to access and retrieve transaction history data.
Read-only access to transaction history.
API Key
hybrid
The Didlogic MCP server offers valuable functionality but requires careful management of the API key. While IP restrictions add a layer of security, the potential for unintended actions by the LLM necessitates thorough testing and monitoring. Running in read-only mode where possible will greatly reduce risk.
The server provides full access to the Didlogic API, so autonomy should be carefully managed through prompt engineering and access controls. There is no built-in sandboxing or rollback support.
Production Tip
Monitor API usage and error rates to detect potential issues early.
API key authentication via environment variable or Bearer token.
Use the provided JSON snippets in your Claude settings, ensuring the correct API key is set.
STDIO, HTTP, and SSE are supported, each with different use cases.
Use the PORT environment variable or the --port command-line argument.
Rate limiting is likely enforced by the underlying Didlogic API, but is not explicitly documented in the MCP server.
Use the `--log-level DEBUG` command-line argument.
Yes, using HTTP or SSE transport modes and specifying the host and port.