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

Local serverstdioPython

What is the Didlogic MCP MCP server?

Didlogic MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Didlogic MCP directly instead of describing what you should do. 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.

What you get

  • 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

What the assistant can call

Once Didlogic MCP is connected, these are the calls the assistant has available:

Configuration and credentials

You will need 4 environment variables: DIDLOGIC_API_KEY, YOUR_DIDLOGIC_KEY, DIDLOGIC_API_URL, YOUR_DIDLOGIC_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

didlogic_mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Didlogic MCP's toolset — PORT, DIDLOGIC_API_URL — is a fair guide to whether it matches your workflow. It is maintained by UserAd; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the didlogic mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
PORTServer port (default: 8000)
DIDLOGIC_API_URLDidlogic API base URL (default: https://app.didlogic.com/api)

How to install the Didlogic MCP MCP server

#### Using pip installation

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

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
DIDLOGIC_API_KEYCredential the server authenticates with.Yes
YOUR_DIDLOGIC_KEYCredential the server authenticates with.Yes
DIDLOGIC_API_URLEndpoint or connection string the server talks to.Yes
YOUR_DIDLOGIC_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Didlogic MCP to PORT.
  • Use Didlogic MCP to DIDLOGIC API URL.

Frequently asked questions

It connects Didlogic MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (PORT, DIDLOGIC_API_URL) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Didlogic MCP directly.