Skip to main content

MCP Digital Human Server

A Model Context Protocol (MCP) server for the AceDataCloud Digital Human API.

Features

  • Create lip-synced digital human videos from a source face video or image
  • Clone voices from short reference audio samples
  • Poll, batch-retrieve, or delete Digital Human tasks

Connect locally

Use the local stdio package and an AceDataCloud API token. The public hosted HTTPS endpoint could not be verified, so this README does not offer it as a connection option. The local MCP process still calls AceDataCloud's API; it does not run the underlying service offline.

  1. Open Ace Data Cloud → Applications. Sign in, or register an account first.
  2. Find General application. If it has not been created, choose Initialize General Application. A general key can use the services available to your account; a dedicated application's key is limited to its service. Check the required service/model access and current pricing.
  3. Copy the API Key from the application card, or open Keys / Manage Keys → Create to create a separate key for this integration. Give it a recognizable name so you can revoke or rotate it independently.
  4. When creating a key, review Expiration Time, Set Usage Limitation, and Allowed APIs. Enable only the restrictions you need, allow the operations you will call, then click Create and copy the token from the key list. Task lookup does not grant permission to submit a generation. Confirm the application's balance can cover your first request; any trial allowance is whatever your account currently displays.
  5. Copy only the token value, without quotation marks, spaces, or Bearer . An API Key / API Token field expects this raw value; only a manually configured HTTP Authorization header needs the Bearer prefix. A platform-... account-management token cannot replace a generation API key.

Copy an application API key or open Manage Keys

Create a separately named key with optional restrictions

Save the key in the client's credential store or the environment variable shown below. Never put it in a prompt, shared workflow, screenshot, or Git commit. If authentication fails, check the full copied value, application/service access, expiration, usage limit, and balance before creating another key.

Local stdio

Install the package and give the local process an API token:

python -m pip install mcp-digitalhuman
export ACEDATACLOUD_API_TOKEN='YOUR_API_TOKEN'
mcp-digitalhuman

For Claude Desktop local MCP, merge this entry into the file opened by its developer settings (~/Library/Application Support/Claude/claude_desktop_config.json on macOS). uvx requires uv on PATH:

{
  "mcpServers": {
    "digitalhuman": {
      "command": "uvx",
      "args": ["mcp-digitalhuman"],
      "env": {"ACEDATACLOUD_API_TOKEN": "YOUR_API_TOKEN"}
    }
  }
}

Keep this user-level file private. Self-hosted HTTP uses mcp-digitalhuman --transport http --port 8000; expose it only with suitable network and TLS controls. Local execution still calls the AceDataCloud API.

Check the connection

Confirm that the MCP client loads its tools. For an existing task ID, digitalhuman_get_task makes an authenticated query; loading the tool alone does not prove downstream API access. A real service request can be billed. If it returns 401, check the API token; if it returns 403 or an account/balance error, read that response before retrying.

Development

pip install -e ".[dev,test]"
pytest -q
ruff check .

Documentation

Documentation

API parameter behavior

digitalhuman_get_tasks_batch retrieves exactly the supplied IDs in input order using authenticated single-task requests. It does not list recent history. A failed retrieval is reported as an error rather than replaced with unrelated tasks.

Metadata

Release files for mcp-digitalhuman 2026.11.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mcp-digitalhuman 2026.11.1.0
File Size Uploaded Provenance Actions
mcp_digitalhuman-2026.11.1.0.tar.gz 20.4 kB Without provenance Details for mcp_digitalhuman-2026.11.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for mcp-digitalhuman 2026.11.1.0
File Interpreter ABI Platform Actions
mcp_digitalhuman-2026.11.1.0-py3-none-any.whl Python 3 none any Details for mcp_digitalhuman-2026.11.1.0-py3-none-any.whl

Total release size: 40.8 kB

Release files / mcp_digitalhuman-2026.11.1.0.tar.gz

Download URL mcp_digitalhuman-2026.11.1.0.tar.gz
Size 20.4 kB
Tags Source
SHA-256 checksum
How to use checksums
df36a0020ff72936a08f18996758de023be60fc8357d16383efc747530aabe8f
BLAKE2b-256 checksum
How to use checksums
3dba396d16f05b8aceab35adbfc288212de0f4758f0806e2bd6ddfce42b8c710
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4

Release files / mcp_digitalhuman-2026.11.1.0-py3-none-any.whl

Download URL mcp_digitalhuman-2026.11.1.0-py3-none-any.whl
Size 20.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ca15f69dc35ee708da4d96801deb8d4f073ea3a4a6590039b57428ea71a82e1c
BLAKE2b-256 checksum
How to use checksums
8cb068dc11b1971d2676d29d80157b86f2d647567d5801e3876dbbb7b66cbf7d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.14.4

Security for mcp-digitalhuman 2026.11.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page