DIDLogic VoIP MCP server

The Didlogic MCP Server implements the Model Context Protocol, allowing Large Language Models to interact with Didlogic's telecommunications API through a standardized interface. It enables LLMs to manage accounts, handle balance operations, and access call histories via structured tools.

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 history access
• Transaction history access

Installation

You can install the Didlogic MCP server using either uv or pip.

Using uv (recommended)

When using uv, no specific installation is needed. The server can be run directly with uvx:

uvx didlogic_mcp

You'll need to set your Didlogic API key as an environment variable when running the server.

Using PIP

Alternatively, you can install didlogic_mcp via pip:

pip install didlogic_mcp

After installation, run it as a module with your API key:

DIDLOGIC_API_KEY=YOUR_DIDLOGIC_KEY python -m didlogic_mcp

Configuration

To use the server with Claude, you need to add specific configuration to your Claude settings.

Configure for Claude.app

Add one of the following configurations to your Claude settings:

Using uvx

"mcpServers": {
  "didlogic": {
    "command": "uvx",
    "args": ["didlogic_mcp"],
    "env": {
      "DIDLOGIC_API_KEY": "YOUR_DIDLOGIC_KEY"
    }
  }
}

Using pip installation

"mcpServers": {
  "didlogic": {
    "command": "python",
    "args": ["-m", "didlogic_mcp"],
    "env": {
      "DIDLOGIC_API_KEY": "YOUR_DIDLOGIC_KEY"
    }
  }
}

Remember to replace YOUR_DIDLOGIC_KEY with your actual Didlogic API key in both configurations.

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "didlogic" '{"command":"uvx","args":["didlogic_mcp"],"env":{"DIDLOGIC_API_KEY":"YOUR_DIDLOGIC_KEY"}}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "didlogic": {
            "command": "uvx",
            "args": [
                "didlogic_mcp"
            ],
            "env": {
                "DIDLOGIC_API_KEY": "YOUR_DIDLOGIC_KEY"
            }
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json
• Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "didlogic": {
            "command": "uvx",
            "args": [
                "didlogic_mcp"
            ],
            "env": {
                "DIDLOGIC_API_KEY": "YOUR_DIDLOGIC_KEY"
            }
        }
    }
}

3. Restart Claude Desktop for the changes to take effect