Bring Sso
to Cursor
Learn how to connect BoxyHQ (Enterprise SSO) to Cursor 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 SubscribersCompatible with every major AI agent and IDE
Gemini
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 Cursor?
Cursor's Agent mode turns BoxyHQ (Enterprise SSO) into an in-editor superpower. Ask Cursor to generate code using live data from BoxyHQ (Enterprise SSO) and it fetches, processes, and writes. all in a single agentic loop. 8 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
BoxyHQ (Enterprise SSO) in Cursor
BoxyHQ (Enterprise SSO) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect BoxyHQ (Enterprise SSO) to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Mattermost (Secure Team Collaboration)
10 toolsManage team collaboration via Mattermost — send messages, search channels, and audit team activities.
Clientify
10 toolsGrow your sales pipeline with a CRM that combines lead capture, email marketing, and deal tracking for Spanish-speaking markets.
Snapchat Ads
8 toolsEquip your AI agent with direct access to Snapchat Ads — manage campaigns, track ad performance, and optimize spend without opening Snapchat Ads Manager.
CM.com
11 toolsReach customers on WhatsApp, SMS, RCS, and voice with a unified messaging platform built for conversational commerce.