Bring Virtual Office
to VS Code Copilot
Learn how to connect WorkAdventure to VS Code Copilot and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the WorkAdventure MCP Server?
Connect your WorkAdventure virtual world to any AI agent and simplify how you manage your digital office or event space through natural conversation.
What you can do
- Member Management — List, create, and delete world members to control access to your virtual spaces.
- World Exploration — Query maps and active rooms to understand your virtual layout and current occupancy.
- Room Control — Get and update room variables to change environmental settings or interactive elements on the fly.
- World Insights — Retrieve comprehensive metadata and configuration details about your virtual environment.
How it works
1. Subscribe to this server
2. Enter your WorkAdventure Admin API Key
3. Start managing your virtual world from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Virtual Office Managers — quickly update office settings, manage team access, and monitor virtual occupancy.
- Event Organizers — automate the registration of attendees and change interactive room elements during live sessions.
- Developers & Designers — query map metadata and test room variables directly from your workspace via AI.
Built-in capabilities (10)
Add a new member to the world
Remove a member from the world
Get details of a specific map
Get details of a specific member
Get variables for a room
Get virtual world information
List world maps
List world members in WorkAdventure
List active rooms
Update a room variable
Why VS Code Copilot?
GitHub Copilot Agent mode brings WorkAdventure data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 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
WorkAdventure in VS Code Copilot
WorkAdventure and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect WorkAdventure 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 WorkAdventure in VS Code Copilot
The WorkAdventure 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 10 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
WorkAdventure for VS Code Copilot
Every tool call from VS Code Copilot to the WorkAdventure MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I change a sign's text in a room using the AI?
Yes! If the sign is controlled by a room variable, you can use the update_room_variable tool to change its value and update the text in real-time.
How do I see who is currently in my virtual world?
You can use the list_members query to get a directory of all registered members, and list_rooms to see active instances and potentially occupancy data.
Is it possible to grant specific access tags to a new member?
Absolutely. When using the create_member tool, you can provide a comma-separated list of tags to define their permissions and visibility in the world.
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.