Bring Internal Tools
to Cursor
Learn how to connect Superblocks to Cursor and start using 7 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 Superblocks MCP Server?
Connect your Superblocks organization to any AI agent to streamline the management of your internal applications and automated workflows. This server allows you to orchestrate your low-code ecosystem through natural language.
What you can do
- Application Management — List all organizational applications, fetch detailed configurations, and create or update apps programmatically.
- Workflow Orchestration — Retrieve a comprehensive list of all active workflows to monitor your backend logic and scheduled jobs.
- Secure Embedding — Generate authenticated session tokens for Embedded Apps, enabling seamless SSO integration for your end-users.
- Lifecycle Control — Perform maintenance by updating application payloads or deleting obsolete resources directly from your chat interface.
How it works
- Subscribe to this server
- Enter your Superblocks API Key
- Start managing your internal tooling infrastructure from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Internal Tools Engineers — quickly audit application configurations and manage resource lifecycles without leaving the terminal or IDE.
- DevOps Teams — monitor active workflows and automate the deployment or update of Superblocks applications.
- Product Managers — list available internal tools and generate embed tokens for stakeholder reviews or client integrations.
Built-in capabilities (7)
Create a new Superblocks application
Used to request session tokens for users when embedding Superblocks applications via SSO. Create an authenticated session token for Embedded Apps
Delete a Superblocks application
Retrieve details for a specific application
Supports pagination. List all applications in the organization
List all workflows in the organization
Update an existing Superblocks application
Why Cursor?
Cursor's Agent mode turns Superblocks into an in-editor superpower. Ask Cursor to generate code using live data from Superblocks and it fetches, processes, and writes. all in a single agentic loop. 7 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
Superblocks in Cursor
Superblocks and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Superblocks 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 Superblocks in Cursor
The Superblocks 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 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
Superblocks for Cursor
Every tool call from Cursor to the Superblocks MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I see all the internal tools currently built in my organization?
You can use the list_applications tool. It retrieves a paginated list of all Superblocks applications, allowing your AI to browse through your entire internal tool library.
Is it possible to generate a login token for a user to view an embedded app?
Yes, the create_embed_token tool is designed specifically for this. Provide the user's email and optional metadata to receive a secure session token for Embedded Apps.
Can I check the status of my backend workflows and scheduled jobs?
Absolutely. Use the list_workflows tool to get a full inventory of all workflows in your organization, which helps in monitoring your automated processes.
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 →
Wolfram Alpha Solver
1 toolsEmpower your AI with the world's most powerful computational engine. Solve complex calculus, extract exact scientific facts, and eliminate mathematical hallucinations.
Sentry Alternative
15 toolsMonitor errors and application health via Sentry — query issues, inspect events, audit releases and check alert rules directly from any AI agent.
Medium
10 toolsPublish and manage content on Medium — create posts and manage publications directly from any AI agent.
American Airlines
3 toolsAI flight tracking: check flight status, schedules, and airport info via agents.