Bring Workshops
to LangChain
Learn how to connect Howspace to LangChain 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 LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Howspace through native MCP adapters. Connect 7 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Howspace MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Howspace queries for multi-turn workflows
Howspace in LangChain
Howspace and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Howspace to LangChain 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 LangChain
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 LangChain 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 LangChain
Every tool call from LangChain 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 LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters