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.
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.
- 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
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.
One command plus a key — pip install didlogic_mcp, then supply credentials