Didlogic MCP Server
Standardized MCP interface for Didlogic API services
Key Features
Use Cases
README
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 services through a standardized interface.
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 hisory access
- Transaction history access
Installation
Using uv (recommended)
When using uv no specific installation is needed. We will
use uvx to directly run didlogic_mcp.
Using PIP
Alternatively you can install didlogic_mcp via pip:
pip install didlogic_mcp
After installation, you can run it as a script using:
DIDLOGIC_API_KEY=YOUR_DIDLOGIC_KEY python -m didlogic_mcp
Transport Modes
The server supports three transport modes:
STDIO Mode (Default)
For local integration with Claude Desktop or similar tools. Uses the DIDLOGIC_API_KEY environment variable for authentication.
# Using uvx (recommended)
DIDLOGIC_API_KEY=your_key uvx didlogic_mcp
# Using uv run
DIDLOGIC_API_KEY=your_key uv run didlogic_mcp
# As Python module
DIDLOGIC_API_KEY=your_key python -m didlogic_mcp --transport stdio
HTTP Mode
For remote access and web clients. Requires Bearer token in Authorization header for each request.
# Using default port (8000)
python -m didlogic_mcp --transport http
# Custom port via environment variable
PORT=9000 python -m didlogic_mcp --transport http
# Custom host and port
python -m didlogic_mcp --transport http --host 0.0.0.0 --port 9000
# With debug logging
python -m didlogic_mcp --transport http --log-level DEBUG
Environment Variables:
PORT- Server port (default: 8000)DIDLOGIC_API_URL- Didlogic API base URL (default: https://app.didlogic.com/api)
Note: In HTTP mode, clients must provide their API key as a Bearer token in the Authorization header.
SSE Mode (Server-Sent Events)
For streaming communication with persistent connections. Ideal for real-time updates and streaming scenarios. Requires Bearer token in Authorization header for each request.
# Using default port (8000)
python -m didlogic_mcp --transport sse
# Custom port via environment variable
PORT=9000 python -m didlogic_mcp --transport sse
# Custom host and port
python -m didlogic_mcp --transport sse --host 0.0.0.0 --port 9000
# With debug logging
python -m didlogic_mcp --transport sse --log-level DEBUG
Environment Variables:
PORT- Server port (default: 8000)DIDLOGIC_API_URL- Didlogic API base URL (default: https://app.didlogic.com/api)
Note: In SSE mode, clients must provide their API key as a Bearer token in the Authorization header for persistent streaming connections.
Configuration
Configure for Claude.app
Add 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"
}
}
}
Configure for Claude Code
For Claude Code, you can connect to a running SSE server instance:
claude mcp add didlogic --transport sse http://localhost:8000/sse --header "Authorization: Bearer YOUR_DIDLOGIC_API_KEY"
Prerequisites:
- Start the server in SSE mode:
python -m didlogic_mcp --transport sse - Run the above command, replacing
YOUR_DIDLOGIC_API_KEYwith your actual API key - The server must be running and accessible at the specified URL
Custom configuration:
- To use a different port: Change
http://localhost:8000/sseto match your server's PORT setting - To connect to a remote server: Replace
localhostwith the server's hostname or IP address
License
MIT
Star History
Repository Owner
User
Repository Details
Programming Languages
Tags
Join Our Newsletter
Stay updated with the latest AI tools, news, and offers by subscribing to our weekly newsletter.
Related MCPs
Discover similar Model Context Protocol servers
Model Context Protocol Server for Home Assistant
Seamlessly connect Home Assistant to LLMs for natural language smart home control via MCP.
Enables integration between a local Home Assistant instance and language models using the Model Context Protocol (MCP). Facilitates natural language monitoring and control of smart home devices, with robust API support for state management, automation, real-time updates, and system administration. Features secure, token-based access, and supports mobile and HTTP clients. Designed to bridge Home Assistant environments with modern AI-driven automation.
- ⭐ 468
- MCP
- tevonsb/homeassistant-mcp
Databricks MCP Server
Expose Databricks data and jobs securely with Model Context Protocol for LLMs.
Databricks MCP Server implements the Model Context Protocol (MCP) to provide a bridge between Databricks APIs and large language models. It enables LLMs to run SQL queries, list Databricks jobs, retrieve job statuses, and fetch detailed job information via a standardized MCP interface. The server handles authentication, secure environment configuration, and provides accessible endpoints for interaction with Databricks workspaces.
- ⭐ 42
- MCP
- JordiNeil/mcp-databricks-server
APISIX Model Context Protocol Server
Bridge LLMs with APISIX for natural language API management.
APISIX Model Context Protocol (MCP) Server enables large language models to interact with and manage APISIX resources via natural language commands. It provides a standardized protocol for connecting AI clients like Claude, Cursor, and Copilot to the APISIX Admin API. The server supports a range of operations including CRUD for routes, services, upstreams, plugins, security configurations, and more. Installation is streamlined via Smithery, npm, or direct source setup with customizable environment variables.
- ⭐ 29
- MCP
- api7/apisix-mcp
CircleCI MCP Server
Enable LLM-driven automation for CircleCI with the Model Context Protocol.
CircleCI MCP Server is an implementation of the Model Context Protocol (MCP) designed to bridge CircleCI with large language models and AI assistants. It supports integration with tools like Cursor IDE, Windsurf, Copilot, and VS Code, allowing users to interact with CircleCI using natural language. The server can be deployed locally via NPX or Docker and remotely, making CircleCI workflows accessible and manageable through standardized protocol operations.
- ⭐ 69
- MCP
- CircleCI-Public/mcp-server-circleci
MCP Server for Iaptic
A Model Context Protocol server for accessing and managing Iaptic data with AI agents.
MCP Server for Iaptic implements the Model Context Protocol to enable AI models, such as Claude, to securely and efficiently interact with Iaptic's customer, purchase, transaction, and statistics data. The server provides a standardized interface and command set for querying and managing information related to customers, purchases, transactions, events, and application management. Designed for integration with Claude Desktop and similar AI clients, it offers both automated and manual installation options.
- ⭐ 5
- MCP
- iaptic/mcp-server-iaptic
NWC MCP Server
Bridge your Bitcoin Lightning wallet with LLMs using Nostr Wallet Connect.
NWC MCP Server enables users to connect Bitcoin Lightning wallets to language models through Nostr Wallet Connect (NWC) and NIP-47 protocols. It leverages the official Model Context Protocol (MCP) TypeScript SDK and supports various transport modes such as STDIO, HTTP streamable, and SSE. The solution can be integrated with platforms like N8N, Claude Desktop, Goose, and Cline, and allows authentication and context management using NWC connection secrets. Although now deprecated in favor of Alby MCP, it provides tooling for leveraging Lightning payment workflows within AI agent interactions.
- ⭐ 12
- MCP
- getAlby/nwc-mcp-server
Didn't find tool you were looking for?