Bring Low Code
to Claude Desktop
Learn how to connect Ninox to Claude Desktop 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 Claude Desktop?
Claude Desktop is the definitive way to connect Ninox to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 8 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Ninox in Claude Desktop
Ninox and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Ninox to Claude Desktop 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 Claude Desktop
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 Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.