4,000+ servers built on vurb.ts
Vinkius
LangChainFramework
BoxyHQ (Enterprise SSO) MCP Server

Bring Sso
to LangChain

Learn how to connect BoxyHQ (Enterprise SSO) to LangChain and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Add ConnectionCreate DirectoryDelete ConnectionGet ConnectionsGet Directory GroupsGet Directory UsersHealth CheckUpdate Connection

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
BoxyHQ (Enterprise SSO)

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

  1. Subscribe to this server
  2. Enter your BoxyHQ Instance URL and API Key
  3. 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_connection

Add a new SAML or OIDC connection

create_directory

0 protocol. Create a Directory Sync (SCIM) connection

delete_connection

Delete an SSO connection

get_connections

Get SSO connections

get_directory_groups

List all groups for a tenant/product directory

get_directory_users

List all users for a tenant/product directory

health_check

Check BoxyHQ service health

update_connection

Update an existing SSO connection

Why LangChain?

LangChain's ecosystem of 500+ components combines seamlessly with BoxyHQ (Enterprise SSO) through native MCP adapters. Connect 8 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 BoxyHQ (Enterprise SSO) 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 BoxyHQ (Enterprise SSO) queries for multi-turn workflows

See it in action

BoxyHQ (Enterprise SSO) in LangChain

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

BoxyHQ (Enterprise SSO) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect BoxyHQ (Enterprise SSO) 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.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for BoxyHQ (Enterprise SSO) in LangChain

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 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.

BoxyHQ (Enterprise SSO)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

The Vinkius Advantage

How Vinkius secures BoxyHQ (Enterprise SSO) for LangChain

Every tool call from LangChain to the BoxyHQ (Enterprise SSO) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

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.

02

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.

03

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.

04

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.

05

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.

06

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.

07

MultiServerMCPClient not found

Install: pip install langchain-mcp-adapters

Explore More MCP Servers

View all →