Skip to main content

visionstory-mcp

MCP server for the VisionStory API — task-oriented tools that let AI agents (Claude Desktop, Cursor, and any Model Context Protocol client) generate AI talking-avatar videos without writing code.

It exposes all 26 public API operations, kept in sync with the visionstory SDK and visionstory CLI:

  • Talking-avatar videos: generate, get, list, and delete.
  • Avatars and voices: create or clone, list, and delete.
  • AI Video: discover models, estimate cost, generate, get one or many, list, and delete.
  • Images, speech, and audio: discover image models, generate or edit images, synthesize localized MP3 audio, transcribe speech, and align known text with word timestamps.
  • Assets and account: upload, list, and delete assets; list avatar models; check credits.

On startup, the local server checks the shared release manifest and writes an upgrade notice to stderr when a newer package is available. Agents can read visionstory://release for the installed and latest versions, feature highlights, release notes, and the upgrade command. Set VISIONSTORY_UPDATE_CHECK=0 to disable the check.

Delete tools require confirm=true after explicit user confirmation. The local stdio server keeps direct local-file support for avatar, voice, talking-video, and asset workflows.

Install & run

Requires an API key — create one on the VisionStory API keys page (Pro plan and up) and set it as VISIONSTORY_API_KEY.

Add it to Claude Desktop (or any MCP client):

{
  "mcpServers": {
    "visionstory": {
      "command": "uvx",
      "args": ["visionstory-mcp"],
      "env": { "VISIONSTORY_API_KEY": "sk-vs-xxxxxxxxxxxxxxxxxxx" }
    }
  }
}

generate_video and generate_ai_video submit and poll to completion, returning the final video URL — one call in, one result out. create_speech returns standard MCP audio content plus usage metadata. transcribe_audio and align_audio accept a local WAV/MP3 file, public URL, or reusable asset ID.

The visionstory://contract MCP resource reports the same contract version, SHA-256 fingerprint, and operation count as visionstory.get_contract_info() and visionstory contract.

Run standalone

Verify that the package and all public tools load, then exit:

uvx visionstory-mcp --check

Run the stdio server for an MCP client:

export VISIONSTORY_API_KEY="sk-vs-xxxxxxxxxxxxxxxxxxx"
uvx visionstory-mcp          # or: python -m visionstory_mcp

The normal server command waits silently for MCP messages. Use --check when testing it directly in a terminal.

License

MIT

Metadata

Release files for visionstory-mcp 0.0.8

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

Source distribution (sdist)

Source distribution for visionstory-mcp 0.0.8
File Size Uploaded Provenance Actions
visionstory_mcp-0.0.8.tar.gz 9.1 kB Without provenance Details for visionstory_mcp-0.0.8.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for visionstory-mcp 0.0.8
File Interpreter ABI Platform Actions
visionstory_mcp-0.0.8-py3-none-any.whl Python 3 none any Details for visionstory_mcp-0.0.8-py3-none-any.whl

Total release size: 19.7 kB

Release files / visionstory_mcp-0.0.8.tar.gz

Download URL visionstory_mcp-0.0.8.tar.gz
Size 9.1 kB
Tags Source
SHA-256 checksum
How to use checksums
368dbb60691918f3e4bf154a143d44fa14d5a7b8cddb450f2ad4375fab1f4d18
BLAKE2b-256 checksum
How to use checksums
57a53242a785826065414a44122c63e275c2ff1eed415215af3b85cc3321ecbf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.13

Release files / visionstory_mcp-0.0.8-py3-none-any.whl

Download URL visionstory_mcp-0.0.8-py3-none-any.whl
Size 10.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
48067f423d59bcf32c009673bbb62af50efbfbd13880ab414dc5379426dee71f
BLAKE2b-256 checksum
How to use checksums
e4efa5ddffa7a43e66e990ba32ab7351abe8d2e0e9d2aa73caa670c8fae69f9f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.13

Security for visionstory-mcp 0.0.8

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