Vinkius
Spiritme logo
Vinkius
Vinkius runs on VS Code Copilot

How to Use the Spiritme MCP in VS Code Copilot

Team-wide video automation with Spiritme for VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Spiritme MCP on Cursor AI Code Editor MCP Client Spiritme MCP on Claude Desktop App MCP Integration Spiritme MCP on OpenAI Agents SDK MCP Compatible Spiritme MCP on Visual Studio Code MCP Extension Client Spiritme MCP on GitHub Copilot AI Agent MCP Integration Spiritme MCP on Google Gemini AI MCP Integration Spiritme MCP on Lovable AI Development MCP Client Spiritme MCP on Mistral AI Agents MCP Compatible Spiritme MCP on Amazon AWS Bedrock MCP Support
MCP Servers — Included with Plan
Vinkius runs on VS Code Copilot

Connect Spiritme MCP to VS Code Copilot

Create your Vinkius account to connect Spiritme to VS Code Copilot — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Key Capabilities

Centralized Video Generation via MCP Server

The team sets up the connection using `.vscode/mcp.json`. When a developer needs to create content, they can call `generate_video` directly within Copilot Chat. This makes video creation part of the shared workflow. Every person on the engineering team gets access to this powerful functionality without manual setup.

Managing Assets Across Teams

Developers can use `list_templates` and `list_voices` to pull in necessary configuration data right into their code. This ensures that all videos generated follow the same brand guidelines. Checking these lists keeps your team aligned on available assets, which is huge for large-scale marketing campaigns.

Verifying Content Status

After a video job starts, you use `get_job_status` to check if it's done. This function lets the team write reliable code that waits for confirmation before proceeding. It prevents errors by making sure no developer assumes content is ready when it’s still rendering on the backend.

Setup guide

Set up Spiritme MCP in VS Code Copilot

Prerequisites

  • VS Code 1.99 or later with GitHub Copilot extension
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Open MCP configuration

    Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.

  2. 2

    Add the Spiritme MCP

    Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.

  3. 3

    Switch to Agent mode

    Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.

  4. 4

    Verify the connection

    In the Copilot Chat input, type # to list available tools. You should see the Spiritme tools listed. Try asking: "List my recent Spiritme transactions" and Copilot will invoke them automatically.

.vscode/mcp.json
{
  "mcpServers": {
    "spiritme-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Spiritme. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Spiritme MCP in VS Code Copilot

The team configures the MCP Server in `.vscode/mcp.json`. This allows every developer to access Spiritme's tools automatically when using Copilot Chat in Agent mode.
The configuration lives in the repository, meaning all developers share the same toolset and endpoints. This eliminates setup drift across a wide engineering team.
Yes, you use `get_job_status`. You write code that polls this function to confirm the rendering job is finished before moving on to deployment.
It is. The team-wide configuration model via `.vscode/mcp.json` makes it perfect for SOC 2 compliant, IT-managed, organization-wide rollouts.
The core data revolves around Video and Template metadata. You're dealing with structured information like job status codes and pre-defined content structures.

Start using the Spiritme MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 12 tools

We've already built the connector for Spiritme. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 12 tools are live and waiting. You're up and running in seconds.

Vinkius runs on Claude Claude
Vinkius runs on ChatGPT ChatGPT
Vinkius runs on Cursor Cursor
Vinkius runs on Gemini Gemini
Vinkius runs on Windsurf Windsurf
Vinkius runs on VS Code VS Code
Vinkius runs on JetBrains JetBrains
Vinkius runs on Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.