Bring Low Code
to Cursor
Learn how to connect Ninox 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.
What is the Ninox MCP Server?
Connect your Ninox account to any AI agent and take full control of your low-code database orchestration and business automation through natural conversation. Ninox provides a powerful platform for creating custom business apps, and this integration allows you to retrieve database schemas, manage records across tables, and execute native Ninox scripts directly from your chat interface.
What you can do
- Database & Table Orchestration — List all managed databases within your teams and retrieve detailed table schemas programmatically to ensure your data foundation is always synchronized.
- Record Lifecycle Management — Create, update, and delete records across any Ninox table with detailed field metadata directly from the AI interface to maintain high-fidelity business data.
- Script & Query Intelligence — Execute native Ninox scripts and complex queries via natural language to perform advanced data manipulation and custom calculations.
- Team & Workspace Control — List your organizational teams and monitor workspace access using simple AI commands to maintain a clear overview of your digital infrastructure.
- Operational Monitoring — Track system responses and manage data ingestion to ensure your business applications are always optimized.
How it works
1. Subscribe to this server
2. Enter your Ninox Personal Access Token and Team ID from your account settings
3. Start managing your custom databases from Claude, Cursor, or any MCP-compatible client
No more manual data entry in complex forms. Your AI acts as a dedicated database administrator or business operations lead.
Who is this for?
- Business Owners & Ops Leads — quickly retrieve project statuses and monitor business metrics without switching apps.
- Data Analysts — automate the retrieval of table records and execute custom scripts via natural conversation.
- Developers — integrate real-time database management and custom business logic directly within the chat.
Built-in capabilities (8)
Create or update records
Delete a record
Execute a Ninox script/query
Get database schema
Get details for a specific record
List all databases in the team
List records from a table
Update a specific record
Why Cursor?
Cursor's Agent mode turns Ninox into an in-editor superpower. Ask Cursor to generate code using live data from Ninox 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
Ninox in Cursor
Ninox and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Ninox 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 | 3,400+ 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 Ninox in Cursor
The Ninox 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
Ninox for Cursor
Every tool call from Cursor to the Ninox MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find my Team ID for me?
The Team ID is required during initial setup. You can find it in your browser URL when you are inside your Ninox workspace (e.g., app.ninox.com/team/ABC123XYZ).
How do I find my Ninox Personal Access Token?
Log in to your Ninox account at app.ninox.com, click the gear icon for Settings, and navigate to the API section to generate your unique secret token.
Can I run native Ninox scripts via the AI?
Yes! Use the execute_ninox_script tool. Provide your database ID and the script body, and the AI will perform the operation using Ninox's native server-side scripting engine.
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.