Didlogic MCP Server is a Model Context Protocol (MCP) server implementation for the Didlogic API, with the goal of enabling large language models (LLMs) to interact with Didlogic services through a standardized interface.
Main capabilities include: full access to the Didlogic API through MCP tools; special prompts for common operations; balance management tools; SIP account (sipfriends) management; IP restriction management; purchase management; call history access; transaction history access.
Usage: running with uv is recommended, no specific installation is required, and didlogic_mcp can be run directly via uvx; didlogic_mcp can also be installed with pip and then run as a script. The server supports three transport modes. STDIO mode (default) is suitable for local integration with Claude Desktop or similar tools, and uses the DIDLOGIC_API_KEY environment variable for authentication. HTTP mode is suitable for remote access and web clients, and requires each request to provide a Bearer token in the Authorization header; related environment variables include PORT (server port, default 8000) and DIDLOGIC_API_URL (Didlogic API base URL, default https://app.didlogic.com/api），注意在 In HTTP mode, the client must provide the API key as a Bearer token in the Authorization header. SSE mode (Server-Sent Events) is suitable for streaming communication over persistent connections, and is suitable for real-time updates and streaming scenarios; it requires each request to provide a Bearer token in the Authorization header. Note that in SSE mode, the client must provide a Bearer token in the Authorization header for persistent streaming connections.
For Claude.app, the configuration can be added to Claude settings. For Claude Code, you can connect to a running SSE server instance: first start the server in SSE mode (python -m didlogic_mcp --transport sse), then run the corresponding command and replace YOUR_DIDLOGIC_API_KEY with the actual API key; the server must be running and accessible at the specified URL. For custom configuration, if you need to use a different port, you can change http://localhost:8000/sse to match the server PORT setting; if you need to connect to a remote server, replace localhost with the server's hostname or IP address.
Use cases: local or remote integration where an LLM needs to manage Didlogic communication service resources through the MCP interface (such as SIP accounts, balance, IP restrictions, purchases, call and transaction history). Limitations: HTTP and SSE modes must use Bearer token authentication; specific tool call details, the list of special prompts, and the complete API mapping are not expanded in the given material and are not currently provided.
