Bring Workshops
to VS Code Copilot
Learn how to connect Howspace to VS Code Copilot and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Howspace MCP Server?
Connect your Howspace account to any AI agent and manage your collaborative workspaces through natural conversation.
What you can do
- Workspace Management — List all workspaces, create new ones, and inspect individual workspace details and settings
- Participant Management — Browse participants in any workspace and add new members by email with optional name fields
- Campaign Management — List all campaigns configured for engagement and communication
- Profile Access — Retrieve information about the authenticated API user
How it works
1. Subscribe to this server
2. Enter your Howspace Base URL and API Key
3. Start managing workspaces from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Facilitators — create workspaces, add participants, and manage collaborative sessions without opening the dashboard
- HR & L&D Teams — onboard new employees into training workspaces and track campaign engagement
- Change Management Consultants — manage large-scale workshops and stakeholder engagement through AI
Built-in capabilities (7)
Add a participant to a workspace
Create a new workspace
Get current user info
Get details of a specific workspace
List all campaigns
List participants in a workspace
List all workspaces in Howspace
Why VS Code Copilot?
GitHub Copilot Agent mode brings Howspace data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 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
Howspace in VS Code Copilot
Howspace and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Howspace 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 Howspace in VS Code Copilot
The Howspace 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 7 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
Howspace for VS Code Copilot
Every tool call from VS Code Copilot to the Howspace MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I create a workspace and add participants through the AI agent?
Yes. Use create_workspace with a name to create a new collaborative workspace. Then use add_participant with the workspace ID, participant email, and optional first/last name to invite members. Use list_workspaces to see all existing workspaces and list_participants to review who is already in a workspace.
Does Howspace require a custom Base URL in addition to the API Key?
Yes. Howspace instances are hosted on custom subdomains, so you need to provide your Base URL (e.g., https://your-org.howspace.com) along with the API Key. The API Key is sent as a Bearer token, and all requests are routed to your specific Howspace instance.
Can I view all campaigns running in my Howspace account?
Yes. The list_campaigns tool retrieves all campaigns configured in your account, including engagement campaigns, communication sequences, and notification triggers. Use get_me to verify your authenticated identity and permissions.
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.