Content Tools
texting.video
Creates editable texting-story videos from fictional or staged conversations, with tools for listing chat themes and retrieving draft JSON schemas.
ENDPOINT 1
https://texting.video/mcp
MCP server metadata
- Name
- texting.video
- Version
- 1.3.0
Author a text-message conversation, then call create_texting_video to get a link the user opens to review, render, and export the video. If your client supports OAuth, connecting a texting.video account saves created drafts to it; Creator Pro accounts also unlock device status-bar and clock controls plus watermark-free export.
Known tools 3
create_texting_videoCreate an editable texting-story video from a fictional, comedic, educational, or clearly staged conversation.
Potential side effectslist_themesList the available chat themes and which ones support the on-screen keyboard / human typing.
Inferred read-onlyget_specGet the full draft JSON schema, an example, and a ready-to-use system prompt for authoring texting.video drafts.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.texting-video]
url = "https://texting.video/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"texting-video": {
"type": "http",
"url": "https://texting.video/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: texting-video
Remote MCP URL: https://texting.video/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"texting-video": {
"url": "https://texting.video/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"texting-video": {
"type": "http",
"url": "https://texting.video/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "texting-video",
"transport": "streamable-http",
"url": "https://texting.video/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.