Didlogic

Provides programmatic access to Didlogic services via MCP tools, including balance, SIP, IP restrictions, purchases, and history data.

python

4

GitHub Stars

python

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

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

You can run the Didlogic MCP Server to let Large Language Models interact with Didlogic services through a standardized interface. It exposes tools for common Didlogic operations, manages authentication, and supports multiple transport modes for local, HTTP, or streaming usage.

How to use

Connect your MCP client to the Didlogic MCP Server using either a local (stdio) or remote (HTTP/SSE) transport. In local mode, you run the server process directly and your client talks to it through the standard input/output channels. In HTTP or SSE modes, you expose the server over a network and authenticate each request with a Bearer token.

How to install

Prerequisites you need before starting: Python (for the Python module) and a runtime that can execute the uvx runner or Python module as shown.

Choose one installation path and follow the exact commands.

Option A: Install via uvx (recommended) and run the Didlogic MCP Server locally.

Install the Python package (if you haven’t yet).
Run the server with uvx using the Didlogic MCP entry point and provide your API key via an environment variable.

Additional configuration and usage notes

Configure your Claude app to connect to the Didlogic MCP Server using one of the supported runtime configurations. You can use either uvx for local operation or a Python command to run the module directly, each with the required environment variable for authentication.

When running in HTTP or SSE modes, supply Bearer tokens in the Authorization header for every request.

Security and environment variables

The Didlogic MCP Server requires an API key to access Didlogic services. Pass this key through environment variables when starting the server.

Example env var used in all included configurations: DIDLOGIC_API_KEY with a value of your actual API key.

Tools and capabilities

The server provides tools to perform common Didlogic operations and account management tasks, including balance checks, SIP account management, IP restrictions, purchases, and access to call and transaction histories.

Available tools

balance

Retrieve and manage your Didlogic balance, including checking credits and applying balance-related actions.

sip_account

Manage SIP accounts (sipfriends), including creation, listing, updating, and deletion.

ip_restrictions

Set and enforce IP-based access restrictions for enhanced security.

purchases

View and manage Didlogic purchases and related transactions.

call_history

Access and query call history records for auditing and review.

transaction_history

Access detailed transaction histories for accounting and reconciliation.

special_prompts

Utilize specialized prompts tailored for common Didlogic operations to streamline interactions.

general_api_access

Full access to the Didlogic API through MCP tools for versatile operations.