Bring Workshops
to Claude Desktop
Learn how to connect Howspace to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect Howspace to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 7 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Howspace in Claude Desktop
Howspace and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Howspace to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.