Bring Ai Avatars
to VS Code Copilot
Learn how to connect Spiritme to VS Code Copilot and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Spiritme MCP Server?
Connect your Spiritme account to any AI agent and take full control of your automated video avatar generation and high-fidelity personalized media workflows through natural conversation.
What you can do
- Avatar Portfolio Orchestration — List and manage your entire high-fidelity portfolio of digital avatars programmatically, retrieving detailed technical metadata and SKU IDs
- Video Generation Intelligence — Programmatically trigger and monitor high-fidelity video generation jobs using custom scripts and voice selections
- Asset & Media Architecture — Access your complete directory of high-fidelity hosted video assets to oversee your organizational resource allocation in real-time
- Engagement Monitoring — Access real-time status updates for video processing and track generation results directly through your agent for instant reporting
- Operational Monitoring — Verify account-level API connectivity and monitor video orchestration volume directly through your agent for perfectly coordinated service scaling
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Spiritme dashboard (Settings > API)
3. Start orchestrating your video growth from Claude, Cursor, or any MCP client
No more manual recording of video updates or missing critical avatar generation status. Your AI acts as your dedicated media coordinator and video architect.
Who is this for?
- Content Marketers — instantly trigger personalized video messages and monitor job status using natural language commands
- Training Teams — verify individual avatar metadata and track training video generation without leaving your creative workspace
- Developers — integrate high-speed Spiritme avatar data into custom automated video pipelines through simple AI queries
Built-in capabilities (12)
Verify connectivity
Delete a video
Generate audio
Generate a video
Get avatar details
Get video job status
Get template details
Get voice details
List avatars
List templates
List videos
List voices
Why VS Code Copilot?
GitHub Copilot Agent mode brings Spiritme data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 12 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Spiritme in VS Code Copilot
Spiritme and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Spiritme to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Spiritme in VS Code Copilot
The Spiritme MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 12 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Spiritme for VS Code Copilot
Every tool call from VS Code Copilot to the Spiritme MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Spiritme API Key?
Log in to your account, navigate to Settings > API, and copy your unique access token from the credentials section.
Can I check the status of a video job via AI?
Yes! The get_spiritme_job_status tool allows your agent to poll the high-fidelity real-time status of any generation request.
How do I list my available avatars?
Use the list_spiritme_avatars tool to retrieve your complete high-fidelity directory along with the unique identifiers for all managed digital actors.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.