VS Code CopilotIDE

BoxyHQ (Enterprise SSO) MCP Server

Bring Sso
to VS Code Copilot

Name: BoxyHQ (Enterprise SSO) MCP Server
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

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

GDPR Free for Subscribers

Add ConnectionCreate DirectoryDelete ConnectionGet ConnectionsGet Directory GroupsGet Directory UsersHealth CheckUpdate Connection

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

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_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 VS Code Copilot?

GitHub Copilot Agent mode brings BoxyHQ (Enterprise SSO) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

—
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
—
Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
—
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
—
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

BoxyHQ (Enterprise SSO) in VS Code Copilot

AI Agent→Vinkius

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 VS Code Copilot 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 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

Unlock for AI Agents View step-by-step setup guide for VS Code Copilot →

Enterprise Security

Why teams choose Vinkius for BoxyHQ (Enterprise SSO) in VS Code Copilot

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 VS Code Copilot 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.

Unlock for AI Agents View full BoxyHQ (Enterprise SSO) details →

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 VS Code Copilot

Every tool call from VS Code Copilot 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

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.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.