The Didlogic MCP Server provides a standardized interface for Large Language Models to comprehensively manage DIDLogic telephony services and VoIP operations.
Core Capabilities:
• Account Management - Check account balance, create/manage SIP accounts with full CRUD operations, and configure IP whitelisting for security
• Phone Number (DID) Operations - Search, purchase, and remove DIDs across multiple countries/regions, configure call routing destinations, and manage SMS-enabled numbers
• Call & Transaction Monitoring - Access detailed inbound/outbound call history with analytics, view comprehensive transaction records including fees and charges
• Advanced Telephony Features - Configure number rewriting rules, set call restrictions (duration, cost, concurrent channels), manage SIP codecs, and handle geographic-specific activation requirements
The server supports flexible integration through three transport modes (STDIO, HTTP, SSE) and provides global coverage for DID services with area-based searching capabilities.
Didlogic MCP Server
A Model Context Protocol (MCP) server implementation for the Didlogic API. This server allows Large Language Models (LLMs) to interact with Didlogic services through a standardized interface.
Features
Full access to Didlogic API through MCP tools
Specialized prompts for common operations
Balance management tools
SIP account (sipfriends) management
IP restriction management
Purchases management
Call hisory access
Transaction history access
Related MCP server: Phabricator MCP Server
Installation
Using uv (recommended)
When using uv no specific installation is needed. We will
use uvx to directly run didlogic_mcp.
Using PIP
Alternatively you can install didlogic_mcp via pip:
After installation, you can run it as a script using:
Transport Modes
The server supports three transport modes:
STDIO Mode (Default)
For local integration with Claude Desktop or similar tools. Uses the DIDLOGIC_API_KEY environment variable for authentication.
HTTP Mode
For remote access and web clients. Requires Bearer token in Authorization header for each request.
Environment Variables:
PORT- Server port (default: 8000)DIDLOGIC_API_URL- Didlogic API base URL (default: https://app.didlogic.com/api)
Note: In HTTP mode, clients must provide their API key as a Bearer token in the Authorization header.
SSE Mode (Server-Sent Events)
For streaming communication with persistent connections. Ideal for real-time updates and streaming scenarios. Requires Bearer token in Authorization header for each request.
Environment Variables:
PORT- Server port (default: 8000)DIDLOGIC_API_URL- Didlogic API base URL (default: https://app.didlogic.com/api)
Note: In SSE mode, clients must provide their API key as a Bearer token in the Authorization header for persistent streaming connections.
Configuration
Configure for Claude.app
Add to your Claude settings:
Using uvx
Using pip installation
Configure for Claude Code
For Claude Code, you can connect to a running SSE server instance:
Prerequisites:
Start the server in SSE mode:
python -m didlogic_mcp --transport sseRun the above command, replacing
YOUR_DIDLOGIC_API_KEYwith your actual API keyThe server must be running and accessible at the specified URL
Custom configuration:
To use a different port: Change
http://localhost:8000/sseto match your server's PORT settingTo connect to a remote server: Replace
localhostwith the server's hostname or IP address
License
MIT