3,400+ MCP servers ready to use
Vinkius

Ninox MCP Server for VS Code CopilotGive VS Code Copilot instant access to 8 tools to Create Records, Delete Record, Execute Ninox Script, and more

Built by Vinkius GDPR 8 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Use with Your AI Agent

Ask AI about this App Connector for VS Code Copilot

Open in ChatGPT Open in Claude Open in Perplexity

The Ninox app connector for VS Code Copilot is a standout in the Industry Titans category — giving your AI agent 8 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Ninox and 3,400+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "ninox": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Ninox
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About 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.

GitHub Copilot Agent mode brings Ninox data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 8 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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.

The Ninox MCP Server exposes 8 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 8 Ninox tools available for VS Code Copilot

When VS Code Copilot connects to Ninox through Vinkius, your AI agent gets direct access to every tool listed below — spanning low-code, relational-database, business-apps, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

create_records

Create or update records

delete_record

Delete a record

execute_ninox_script

Execute a Ninox script/query

get_database_schema

Get database schema

get_record

Get details for a specific record

list_databases

List all databases in the team

list_records

List records from a table

update_record

Update a specific record

Connect Ninox to VS Code Copilot via MCP

Follow these steps to wire Ninox into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using Ninox

Ask Copilot: "Using Ninox, help me...". 8 tools available

Why Use VS Code Copilot with the Ninox MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Ninox through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Ninox + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Ninox MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Ninox in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Ninox immediately.

01

"List all tables in my Ninox database ID 'db123'."

02

"Show me the schema and field definitions for the Customers table in database db_main."

03

"Create a new record in the Orders table with customer Acme Corp, amount 4500, and status Pending."

Troubleshooting Ninox MCP Server with VS Code Copilot

Common issues when connecting Ninox to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Ninox + VS Code Copilot FAQ

Common questions about integrating Ninox MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.