Compatible with every major AI agent and IDE
What is the BoxyHQ (Enterprise SSO) MCP Server?
Connect your BoxyHQ instance to any AI agent to streamline enterprise authentication and user lifecycle management through natural language.
What you can do
- SSO Connections — Add, update, and manage SAML and OIDC connections for specific tenants and products.
- Directory Sync (SCIM) — Create and configure SCIM 2.0 directories to automate user provisioning and de-provisioning.
- Connection Auditing — Retrieve detailed connection metadata using tenant IDs, product IDs, or client IDs.
- Metadata Management — Configure IdP metadata via raw XML (Base64) or direct metadata URLs for rapid deployment.
- Lifecycle Control — Update existing security configurations or delete stale connections to maintain a clean security posture.
How it works
- Subscribe to this server
- Enter your BoxyHQ Instance URL and API Key
- Start managing enterprise identity workflows from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Security Engineers — quickly audit and update SSO configurations across multiple tenants without manual dashboard navigation.
- DevOps & SREs — automate the creation of SCIM directories and SAML connections during customer onboarding.
- Product Managers — verify the status of enterprise integrations and connection health directly from the chat interface.
Built-in capabilities (8)
Add a new SAML or OIDC connection
0 protocol. Create a Directory Sync (SCIM) connection
Delete an SSO connection
Get SSO connections
List all groups for a tenant/product directory
List all users for a tenant/product directory
Check BoxyHQ service health
Update an existing SSO connection
Why CrewAI?
When paired with CrewAI, BoxyHQ (Enterprise SSO) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call BoxyHQ (Enterprise SSO) 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
BoxyHQ (Enterprise SSO) in CrewAI
BoxyHQ (Enterprise SSO) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect BoxyHQ (Enterprise SSO) 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 | 4,000+ 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 BoxyHQ (Enterprise SSO) in CrewAI
The BoxyHQ (Enterprise SSO) 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 8 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
BoxyHQ (Enterprise SSO) for CrewAI
Every tool call from CrewAI to the BoxyHQ (Enterprise SSO) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I configure a SAML connection using just the metadata URL?
Yes! Use the add_connection tool and provide the metadataUrl. The server will fetch and process the IdP configuration automatically.
How do I find the clientID for an existing connection?
You can use the get_connections tool by providing the tenant and product IDs. It will return all matching connections including their unique clientIDs.
Does this support SCIM for automated user provisioning?
Absolutely. Use the create_directory tool to set up a SCIM 2.0 directory for providers like Okta, Azure AD, or Google, including webhook support for events.
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.
Explore More MCP Servers
View all →
Road511
8 toolsAccess real-time US and Canada traffic data via Road511 — track incidents, monitor cameras, check road conditions, and analyze trends from any AI agent.

Workato
7 toolsMonitor automation recipes, manage job executions, and audit app connections on Workato — the leading enterprise iPaaS platform.

Rollbar
10 toolsConnect your AI assistant to Rollbar to identify active bugs, review stack traces, trace code deployments, and manage error lifecycles without leaving the chat.

Freshsales
10 toolsClose deals faster with AI-powered lead scoring, visual deal pipelines, and built-in phone and email in one sales CRM.
