MCP.so
ログイン

Didlogic MCP Server

@UserAd

Didlogic MCP Server について

概要はまだありません

基本情報

カテゴリ

その他

ライセンス

MIT

ランタイム

python

トランスポート

stdio

公開者

UserAd

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Didlogic MCP Server?

Didlogic MCP Server is a Model Context Protocol (MCP) server that provides LLMs with a standardized interface to the Didlogic API. It offers tools and prompts for managing Didlogic services, including balances, SIP accounts, IP restrictions, purchases, call history, and transactions.

How to use Didlogic MCP Server?

Install via uvx (recommended) or pip, then run with your Didlogic API key set as the DIDLOGIC_API_KEY environment variable. The server supports three transport modes: STDIO (default), HTTP, and SSE. For HTTP and SSE modes, clients must pass the API key as a Bearer token in the Authorization header.

Key features of Didlogic MCP Server

  • Full Didlogic API access through MCP tools
  • Specialized prompts for common operations
  • Balance management tools
  • SIP account (sipfriends) management
  • IP restriction management
  • Purchases, call history, and transaction history access

Use cases of Didlogic MCP Server

  • An LLM assistant checking account balance and transaction history
  • Automating SIP account creation and IP restriction updates
  • Querying call history and purchase records via natural language
  • Integrating Didlogic management into a Claude-powered workflow

FAQ from Didlogic MCP Server

What does Didlogic MCP Server do?

It exposes Didlogic API functionality as MCP tools and prompts, allowing large language models to manage Didlogic services programmatically.

How do I authenticate?

Provide your Didlogic API key via the DIDLOGIC_API_KEY environment variable. In HTTP and SSE modes, pass it as a Bearer token in the Authorization header.

What transport modes are supported?

Three modes: STDIO (default, for local Claude Desktop integration), HTTP (remote access with Bearer token), and SSE (streaming communication with persistent connections).

How do I set it up for Claude?

For Claude.app, add a didlogic entry in mcpServers with command uvx or python and the API key in environment variables. For Claude Code, run claude mcp add didlogic --transport sse pointing to an SSE server instance.

Are there any runtime dependencies?

The server requires Python and can be run via uvx (no explicit install) or installed with pip install didlogic_mcp. No other runtime dependencies are mentioned.

コメント

「その他」の他のコンテンツ