LABSCO SUMMARY
Three transports, two credential models.
The distinction matters more than it looks: over stdio the server holds one account's key for its lifetime, while over HTTP or SSE each request carries its own bearer token — so one running instance can serve several accounts without any of them sharing a credential. Choose the transport by who is going to use it, not by what your client prefers.
What it is
A server for the Didlogic voice API. It covers the account-management side of running SIP telephony: what you have bought, what is connected, what it has cost and who is allowed to connect.
What you get
- Balance management
- SIP account administration
- IP restriction rules, which is where you control who may register against the account
- Purchases management
- Call history and transaction history
- Prompts for the common operations, so the frequent tasks are not reconstructed from scratch each time
Requirements
The PyPI package didlogic_mcp, version 1.0.4, run through uvx or installed with pip. In stdio mode the credential is DIDLOGIC_API_KEY in the environment. In HTTP and SSE modes the key travels as a bearer token in the Authorization header on every request instead, which is what makes a shared deployment possible. PORT defaults to 8000 and DIDLOGIC_API_URL to the Didlogic production API.
Setup effort
One command plus a key — pip install didlogic_mcp, then supply credentials
USE CASES
01
Checking what the account is spending
Read the balance and the transaction history in one conversation rather than logging into a portal.
02
Adding or auditing a SIP account
Manage the SIP accounts directly, including which IP addresses are allowed to register.
03
Investigating a call that failed
Pull the call history for the period and look at what was actually attempted.
BEFORE YOU INSTALL
What to know first
Requires
- pip on PATH
- DIDLOGIC_API_KEY in your environment
Where it runs
All 3 documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install didlogic_mcpMCP Clients
Claude Desktop — uvx
CLAUDE DESKTOP — UVX · JSON
{
"mcpServers": {
"didlogic": {
"command": "uvx",
"args": [
"didlogic_mcp"
],
"env": {
"DIDLOGIC_API_KEY": "<YOUR_DIDLOGIC_API_KEY>"
}
}
}
}Claude Desktop — pip
CLAUDE DESKTOP — PIP · JSON
{
"mcpServers": {
"didlogic": {
"command": "python",
"args": [
"-m",
"didlogic_mcp"
],
"env": {
"DIDLOGIC_API_KEY": "<YOUR_DIDLOGIC_API_KEY>"
}
}
}
}Claude Code — SSE
CLAUDE CODE — SSE · TERMINAL
claude mcp add didlogic --transport sse http://localhost:8000/sse --header "Authorization: Bearer <YOUR_DIDLOGIC_API_KEY>"