← All integrations

Ninox MCP server

19 operations0 webhooks

Read a Ninox workspace and its modules, create and delete tables and fields, read, create, update, upsert and delete records with a row-level change feed, list views, and run Ninox script.

Try Ninox with your agent

Connect Ninox, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Ninox on my account, then run one read-only example and show me the result.

Runs once, when you ask

Ninox tools and triggers

Tools are what your agent can do in Ninox through Corsair's MCP server. Triggers are the Ninox events a routine can start from.

Records

  • ChangesRead-only

    Poll a table’s row-level change feed since a timestamp, which needs history tracking enabled on that table

    records.changes

  • CreateWrite

    Create rows in one transaction, so a single bad record rolls the whole batch back

    records.create

  • DeleteDestructive

    Delete rows in one transaction, rolling the whole set back if any id is wrong; there is no restore call

    records.delete

  • GetRead-only

    Read one row by id, which is the only way to fetch a known record because the id is not filterable

    records.get

  • ListRead-only

    Read rows from a table with a field filter, sort order and offset paging; only columns the table marks filterable are accepted

    records.list

  • UpdateWrite

    Update rows in one transaction, optionally rejecting a write when a field no longer holds the value the caller read

    records.update

  • UpsertWrite

    Create or update rows matched by one unique field, refusing an ambiguous match rather than picking a row

    records.upsert

Tables

  • CreateWrite

    Create a table in a module; add its fields with fields.create

    tables.create

  • DeleteDestructive

    Delete a table and every record in it

    tables.delete

  • GetRead-only

    Read one table with all of its field definitions

    tables.get

  • ListRead-only

    List the tables inside one module

    tables.list

Fields

  • CreateWrite

    Add a field to a table: text, number, choice, date, reference and the other Ninox types

    fields.create

Connect Ninox to Claude, ChatGPT or Cursor

  1. 1

    Connect Ninox in Corsair

    Add your Ninox API key once in Corsair. Corsair stores the credential encrypted and makes the Ninox API calls for your agent, so it never goes into a prompt or a config file. Connect Ninox

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Ninox. On a ChatGPT personal plan, connect Ninox here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Ninox's read and write operations run right away and its 4 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/ninox, add the Ninox plugin, and connect with an API key. Then call methods like corsair.ninox.api.fields.create() from your app. Corsair keeps each tenant isolated.

Yes. Ninox requires an API key from your Ninox account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Ninox, GitHub, Notion, Stripe, and the rest. Trigger Ninox from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for read a Ninox workspace and its modules, create and delete tables and fields, read, create, update, upsert and delete records with a row-level change feed, list views, and run Ninox script. Common builds include sync jobs, admin tooling, and agents that call Ninox APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Ninox API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/ninox in the open repo. When Ninox ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Ninox data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Ninox data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Ninox on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 4 destructive Ninox operations. You can change a link's mode at hub.corsair.dev/me.