NinoxNet

ar.com.ninoxPublished by ninox.com.arOfficial publisherv2.1.0Updated Oct 24, 2026

Ninox ERP by NinoxNet: manage inventory, sales, HR and goals, and build in-app dashboards.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

NinoxNet is a remote MCP server for the Ninox ERP system, letting an assistant manage inventory, sales, HR and goals and build in-app dashboards.

What you can do
Manage inventory records and stock data in the Ninox ERP system. Handle sales information and related business records. Work with HR data and goal tracking. Build and adjust in-app dashboards. No individual tools are listed, so exact operations are not documented.
When to use it
Useful when an assistant should work directly with a Ninox ERP instance covering inventory, sales, HR and goals, or help assemble dashboards from that business data.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's host. OAuth authentication is required, so a Ninox account authorized through that flow is needed. No environment variables or headers are declared.
Before you install
The server is authorized through OAuth and can act on business records such as inventory, sales and HR data, so changes may be written to the live ERP. HR and sales data are sensitive; confirm what the assistant may read or modify before connecting.

Installation

In SourceWeft

  1. Open NinoxNet in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ar.com.ninox%2Fninoxnet/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ninoxnet": {
      "type": "http",
      "url": "https://mcp.ninox.com.ar/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.1.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.