X (Twitter)LinkedInGitHubDiscordYouTube

How to connect Ninox to Claude

Connect Claude Web, Desktop and Cowork to Ninox MCP. List all databases in your marketing team, delete a customer record by id, and more using natural language, with authentication handled for you.

Get started for freeGet a demo
Ninox logoNinox
Api Key

Ninox is a low-code database platform for building custom business applications. It helps teams organize, automate, and collaborate on their data with ease.

4 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your Ninox account to Claude via Composio Connect, enabling it to list all databases in your marketing team, delete a customer record by ID, show all databases for your sales workspace, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate Ninox with

Claude CodeOpenAI Agents SDKClaude Agent SDKCodexOpenClawHermesAtomic AgentGoogle ADKLangChainVercel AI SDKMastra AILlamaIndexCrewAIPydantic AIAutoGen

Connecting Ninox to Claude Web, Desktop, and Cowork

Two ways to add the Composio connector. Pick whichever you prefer.

1. Add with one click

Click the button. Claude opens with the Composio connector filled in. Click Add, then go to step 2.

Add to Claude

Add manually

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

2. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

3. Connect your Ninox account

Back in Claude, ask it to connect to Ninox or give it any Ninox-related task.

For example, ask Claude to:

  • "List all databases in your marketing team"
  • "Delete a customer record by ID"
  • "Show all databases for your sales workspace"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your Ninox account is ready to use.

What is the Ninox Claude Connector, and what's possible with it?

The Ninox MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Ninox account. It provides structured and secure access to your custom database applications, so your agent can perform actions like listing databases, retrieving details, and deleting records—all without manual intervention.

  • Retrieve all team databases: Instantly ask your agent to fetch and list every database available within a specified Ninox team to streamline access and navigation.
  • Automated record deletion: Empower your agent to delete specific records from any table, given the correct workspace, database, table, and record IDs—keeping your data organized and up-to-date.
  • Database overview for project management: Have your agent quickly provide an overview of all databases for project tracking or auditing purposes within your team.
  • Simplified database administration: Let your agent automate repetitive admin tasks, like cleaning up obsolete records, so you can focus on building smarter workflows.

Troubleshooting

1. Why does Claude not use the Composio connector for Ninox?

The connector can show as connected, but Claude must use it in each Ninox conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to Ninox again.

2. Why does Claude show an MCP server error before Ninox connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for Ninox.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect Ninox.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the Ninox authorization link not work?

The Composio connector is one server. Your Ninox account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the Ninox connection.
  • Composio creates a fresh Ninox authorization link.
  • Open that link in your browser and finish the Ninox sign-in.

4. Why do Ninox actions fail after they worked before?

The Ninox connection can expire or lose permission.

  • Ask Claude to inspect the Ninox connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the Ninox account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in Ninox.
  • If the action still fails with a permission error, check that the connected account has that permission in Ninox itself.

5. How do I switch to a different Ninox account?

Claude can manage the Ninox connection for you.

  • Ask Claude to disconnect or delete the current Ninox account.
  • Ask Claude to connect Ninox again.
  • Open the new Composio authorization link for Ninox.
  • Sign in with the other Ninox account in the browser.
  • After the account connects, ask Claude to retry the Ninox task.

6. Why is my Ninox connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your Ninox connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click ⋮ and click Clear cache.
  • If Ninox tools still do not appear, click ⋮, disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect Ninox.
TOOLS

Supported Tools

Every Ninox action and event your agent gets out of the box.

Delete Record

Tool to delete a record from a specified table.

Get Databases

Retrieves all databases within a specific Ninox team.

Get Team

Retrieves data from a single team (workspace) by its ID.

List Teams

Retrieves all workspaces (teams) accessible to the authenticated user.

FRAMEWORKS

How to build Ninox MCP Agent with another framework

Claude Code logo

Claude Code

Use Ninox MCP with Claude Code

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Ninox MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Ninox MCP with Claude Agent SDK

Codex logo

Codex

Use Ninox MCP with Codex

OpenClaw logo

OpenClaw

Use Ninox MCP with OpenClaw

Hermes logo

Hermes

Use Ninox MCP with Hermes

Atomic Agent logo

Atomic Agent

Use Ninox MCP with Atomic Agent

Google ADK logo

Google ADK

Use Ninox MCP with Google ADK

LangChain logo

LangChain

Use Ninox MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Ninox MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Ninox MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Ninox MCP with LlamaIndex

CrewAI logo

CrewAI

Use Ninox MCP with CrewAI

Pydantic AI logo

Pydantic AI

Use Ninox MCP with Pydantic AI

AutoGen logo

AutoGen

Use Ninox MCP with AutoGen

FAQ

Frequently asked questions

With a standalone Ninox MCP server, the agents and LLMs can only access a fixed set of Ninox tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Ninox and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Ninox tools.

Yes, absolutely. You can configure which Ninox scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Ninox data and credentials are handled as safely as possible.

Start with Ninox.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Ninox tool your agent needs.Free to start.

Start building