Bring Workshops
to CrewAI
Learn how to connect Howspace to CrewAI 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 CrewAI?
When paired with CrewAI, Howspace becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Howspace tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Howspace in CrewAI
Howspace and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Howspace to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.