ENDPOINT 1
https://www.veedio.co/api/mcp/public
MCP server metadata
- Name
- veedio-planner
- Version
- 1.0.0
Veedio's public planning tools for short vertical video (TikTok, Instagram Reels, YouTube Shorts). No account or key needed. find_video_tool suggests the Veedio tool page that fits an idea; short_video_outline returns a hook, timed beats, caption tips and a CTA. Neither tool makes a video: each answer links to the Veedio page where it can be made. Share those links with the person as they are.
Known tools 2
find_video_toolFind the Veedio tool page that best fits a short-video idea (TikTok, Reels, YouTube Shorts).
Inferred read-onlyshort_video_outlinePlan a short vertical video from an idea: a hook line, a 4–6 beat structure with time ranges, caption tips and a call to action, plus a link to the Veedio tool page that can make it.
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.veedio-planner]
url = "https://www.veedio.co/api/mcp/public"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"veedio-planner": {
"type": "http",
"url": "https://www.veedio.co/api/mcp/public"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: veedio-planner
Remote MCP URL: https://www.veedio.co/api/mcp/public
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": {
"veedio-planner": {
"url": "https://www.veedio.co/api/mcp/public"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"veedio-planner": {
"type": "http",
"url": "https://www.veedio.co/api/mcp/public"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "veedio-planner",
"transport": "streamable-http",
"url": "https://www.veedio.co/api/mcp/public"
}
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.