Ninox
Ninox is a low-code platform that enables users to create custom database applications tailored to their specific needs.
Verdict
Common use cases
- Audit all databases in a Ninox workspace
- Remove test records after QA runs
- Clean up duplicate entries from imports
- List available databases before migration
- Delete archived project records in bulk
Integration
- Vendor
- Ninox
- Category
- other
- Auth
- API_KEY
- Tools
- 2
- Composio slug
ninox
Tools
- Delete Recorddestructive
Tool to delete a record from a specified table. use after confirming workspace, database, table, and record ids.
- Get Databases
Tool to retrieve all databases in a specific ninox team. use after confirming the team id is correct.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP integrations section. 2. Select 'Add Integration' and choose Ninox from the list. 3. You'll need a Ninox API key — generate one by logging into your Ninox account, going to Account Settings, then API Keys, and creating a new key with read and delete permissions. 4. Paste the API key into Switchy's connection form and save. 5. To test, open any Space and type '@Ninox get databases for team [your-team-id]' — replace the placeholder with your actual Ninox team ID, which you can find in your Ninox workspace URL. 6. If the connection works, you'll see a list of databases returned in the chat. 7. To delete a record, you'll need the workspace ID, database ID, table ID, and record ID — use '@Ninox delete record from table [table-id] in database [database-id]' after confirming those identifiers.
What teammates see: by default, memories from Ninox are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Team Databases
@Ninox get all databases for team ID 12345. Show me the database names and IDs in a table.Open in a Space →
Delete Test Record
@Ninox delete record ID 67890 from table 'Orders' in database 54321. Confirm the deletion was successful.Open in a Space →
Audit Database Structure
@Ninox retrieve all databases for team 12345, then create a summary of which ones were last modified in the past 90 days.Open in a Space →
Clean Up Import Errors
@Ninox show me databases for team 12345, then delete record 99999 from the 'Contacts' table in database 54321 if it exists.Open in a Space →
Pre-Migration Inventory
@Ninox get all databases for team 12345 and list their names, IDs, and any metadata available for migration planning.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Ninox show me all databases in team ID 'acme-corp' so I can see what data sources are available
Found 4 databases in the acme-corp team: 'Customer CRM' (ID: db_9x2k), 'Inventory Tracker' (ID: db_4p7m), 'Project Timesheets' (ID: db_1n8q), and 'Vendor Contacts' (ID: db_5r3w). Each database contains multiple tables with records you can query or modify. To explore a specific database's structure, you'll need to use additional tools with the database ID.
This example shows the MCP's ability to list available databases within a Ninox team workspace. You must know your team ID in advance — the MCP cannot discover it automatically. Useful for orienting yourself before querying specific tables or records.
@Ninox delete record ID 'rec_8k4j' from the 'Archived Leads' table in database 'db_9x2k' after I confirm it's safe to remove
Record rec_8k4j has been permanently deleted from the 'Archived Leads' table in database db_9x2k. This action cannot be undone through the MCP. If you need to restore this record, you'll need to use Ninox's native interface or check if your workspace has backup/versioning enabled.
Demonstrates the MCP's write capability with a destructive action. Always verify workspace, database, table, and record IDs before deletion — there's no undo mechanism exposed through this tool. Consider implementing a confirmation step in your Space workflow to prevent accidental data loss.
@Ninox list all databases in team 'acme-corp', then help me identify which one likely contains customer support tickets based on naming patterns
Retrieved 4 databases from acme-corp: 'Customer CRM', 'Inventory Tracker', 'Project Timesheets', and 'Vendor Contacts'. Based on naming conventions, 'Customer CRM' (ID: db_9x2k) is the most likely candidate for support ticket data, as CRM systems typically track customer interactions and issues. However, I'd need to inspect the table structure within that database to confirm it contains ticket-related fields like status, priority, or assignee.
Shows how the MCP's database listing combines with AI reasoning to narrow down data sources. The MCP itself only returns database names and IDs — the AI infers purpose from naming. You'll need additional Ninox API calls (not shown here) to inspect table schemas and confirm the database's actual contents.
Use-case deep-dives
When Ninox MCP makes sense for recurring data hygiene
A 6-person field service team logs completed jobs in Ninox tables, but duplicate or test records pile up weekly. The Ninox MCP is the right call here if your cleanup workflow is predictable: you identify bad records in Ninox's UI, then delete them in batch from Switchy without switching contexts. The two-tool scope (list databases, delete records) means you can script a weekly purge routine that runs in under a minute. The trade-off: if you need to create or update records, this MCP won't help—you're stuck toggling back to Ninox. If your team spends more time entering data than cleaning it, skip this integration and use Ninox's native interface. But for teams doing monthly audits or post-migration cleanup, the MCP saves the round-trip.
Where this MCP wins for cross-workspace visibility
A 3-person operations team manages inventory across four separate Ninox databases (one per warehouse). The Ninox MCP shines when you need to confirm which databases exist in a workspace before running a delete operation—common during quarterly audits when you're archiving old records. You call Get Databases once, see the full list with IDs, then target the correct table for cleanup. This two-step pattern works well for teams under 10 people who touch Ninox sporadically and need a quick reference without logging into the web app. The limitation: you can't read or search records, so if your audit requires comparing values across tables, you'll need Ninox's native query builder. Use this MCP when your workflow is 'find the right database, delete known bad records'—not exploratory analysis.
When API key auth makes this MCP safe for contractors
A 2-person startup hires a contractor to clean up test data left over from a Ninox trial. The Ninox MCP is the safe play here because it uses API key auth—you generate a key with delete-only permissions, share it in Switchy, and the contractor can purge records without accessing your full Ninox account. The two-tool limit means they can't accidentally modify live data or export sensitive tables. This setup works for one-off projects where you need scoped access for 1-3 days. The boundary: if the contractor needs to verify record contents before deleting, they'll have to ask you to screenshot the Ninox UI, since the MCP can't read records. For teams doing a single cleanup sprint with external help, this MCP delivers controlled access without the risk of a full login.
Frequently asked
What does the Ninox MCP do in Switchy?
The Ninox MCP lets your team read databases and delete records from Ninox workspaces directly in Switchy conversations. You can pull database lists from a team workspace, then remove specific records from tables once you've confirmed the workspace, database, table, and record IDs. It's useful for cleaning up test data or managing records without opening the Ninox web app.
Do I need admin access to connect Ninox?
You need a Ninox API key with permissions to read databases and delete records in the target team workspace. Ninox doesn't use OAuth—you generate the API key in your Ninox account settings and paste it into Switchy. If your Ninox role restricts deletions, the MCP will fail when trying to remove records, so confirm your permissions before connecting.
Can the Ninox MCP create or update records?
No. This MCP only retrieves database lists and deletes records. If you need to create or update Ninox records, use Ninox's REST API directly or ask your team to build a custom MCP with those endpoints. The current integration is read-and-delete only, which limits its usefulness for data entry workflows.
Why use this MCP instead of the Ninox web interface?
The MCP saves clicks when you're already in a Switchy conversation and need to confirm a database structure or bulk-delete records based on AI-generated filters. You skip logging into Ninox separately. That said, for complex queries or record creation, the Ninox UI or API is faster—this MCP shines for quick lookups and deletions tied to other workflow steps.
Who on the team should connect the Ninox MCP?
Whoever owns your team's Ninox API key and understands which databases and tables exist. Since the delete tool is destructive, limit access to team members who know Ninox's schema and won't accidentally remove production records. One shared connection per workspace is typical—Switchy doesn't count MCP connections against user seats.