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 24 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 and speech: discover image models, generate or edit images, and synthesize MP3 audio.
- Assets and account: upload, list, and delete assets; list avatar models; check credits.
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 at visionstory.ai/openapi (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.
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.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| visionstory_mcp-0.0.6.tar.gz | 8.2 kB | Without provenance | Details for visionstory_mcp-0.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| visionstory_mcp-0.0.6-py3-none-any.whl | Python 3 | none | any | Details for visionstory_mcp-0.0.6-py3-none-any.whl |
Total release size: 17.9 kB
Release files / visionstory_mcp-0.0.6.tar.gz
| Download URL | visionstory_mcp-0.0.6.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa5a3d5ffd978906fcee121a78588feeca1dd4bd4892ddb25d712d54dc29834f
|
|
BLAKE2b-256 checksum How to use checksums |
3be6cbc4f6a9d9d502d3ed1078ab2a6ed47c2961a046631a708025e0f1c55db4
|
| 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.6-py3-none-any.whl
| Download URL | visionstory_mcp-0.0.6-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84746dafa5209313ffd70b4903114cc969d81c7a7bd235c3671b26554fb86fd5
|
|
BLAKE2b-256 checksum How to use checksums |
0c3420e1376bdc2969e8c165338c5bd6f204d68735bdcfff94d453eae463bc19
|
| 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.6
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.