Bring Workshops
to Cursor
Learn how to connect Howspace to Cursor 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 Cursor?
Cursor's Agent mode turns Howspace into an in-editor superpower. Ask Cursor to generate code using live data from Howspace and it fetches, processes, and writes. all in a single agentic loop. 7 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Howspace in Cursor
Howspace and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Howspace to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
