Aide Mcp Server

io.github.NetAppPublished by GitHub account NetAppv1.0.0Updated Oct 24, 2026

MCP server for NetApp AI Data Engine

The publisher's own server: Aide

Overview

AI-generated overview

Local MCP server that lets an assistant run semantic RAG searches against NetApp AI Data Engine and return relevant documents.

What you can do
  • Search documents: run a query against the NetApp AI Data Engine RAG API, which performs vector-based semantic similarity search and returns the relevant documents.
  • Authenticate on first use: the server starts an OAuth sign-in (browser PKCE flow or device code flow) when the first tool call is made.
When to use it
Use it when your organization runs NetApp AI Data Engine and you want an assistant to retrieve answers from that indexed document corpus during a conversation, especially in a desktop MCP client on the same machine.
Requirements
Runs locally over stdio as the Python package netapp-aide-mcp, launched with uvx; needs Python 3.10 or newer and uv. A .netapp JSON file in the home directory must hold the RAG search API endpoint, SSL verification setting, auth flow, Microsoft Entra token endpoints, client_id, redirect_uri and scope. A browser or a second device is needed to complete sign-in. No environment variables or headers are declared.
Before you install
The .netapp file holds your client_id, tenant endpoints and scope, and the README advises restricting it to owner-only permissions. Sign-in opens a browser or prints a device code in the server logs, so anyone with log access could see it. Queries and retrieved content go to your configured AIDE endpoint and Microsoft identity platform. Only desktop clients that support stdio transport work.

Installation

In SourceWeft

  1. Open Aide Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

NetApp AI Data Engine (AIDE) MCP Server

Description

netapp-aide-mcp is an MCP server (Python package) that exposes the NetApp AI Data Engine's RAG (Retrieval-Augmented Generation) search functionality via MCP. The server exposes a tool named netapp_data_engine_search, which provides the ability to search for documents using AIDE's RAG API. This RAG API implements a vector-based semantic similarity search engine that retrieves relevant documents based on the provided query.

[!NOTE] This MCP server uses the stdio transport, making it a "local MCP server".

Quick start

Prerequisites

  • Python >= 3.10
  • uv (manages all installations automatically)

Configuration

Before running the server, you need to create a .netapp file in your home directory with the necessary configuration.

  1. Create the .netapp file:

    • Open a terminal or file explorer.
    • Navigate to your home directory (e.g., ~ on Unix-like systems or C:\Users\YourUsername on Windows).
    • Create a new file named .netapp.
  2. Add the JSON configuration:

    • Open the .netapp file in a text editor.
    • Add the following JSON configuration, replacing the example values with your own:

    For PKCE flow: (Recommended if you have a browser available on your machine)

    json
    {  "rag_search_api_endpoint_url": "https://example.com/api",  "verify_ssl": true,  "auth_flow": "pkce",  "token_request_endpoint_url": "https://login.microsoftonline.com/<tenant>/oauth2/v2.0/authorize",  "token_exchange_endpoint_url": "https://login.microsoftonline.com/<tenant>/oauth2/v2.0/token",  "token_request_params": {    "client_id": "your_client_id",    "redirect_uri": "http://localhost:8888",    "scope": "api://your-app/.default",    "use_pkce": true,    "auth_timeout_seconds": 300  }}

    For device code flow: (Use this if you do not have a browser on your machine. A short code will be printed in the logs — copy it, open the provided verification URL on any device, and enter the code to complete authentication.)

    json
    {  "rag_search_api_endpoint_url": "https://example.com/api",  "verify_ssl": true,  "auth_flow": "device_code",  "device_code_endpoint_url": "https://login.microsoftonline.com/<tenant>/oauth2/v2.0/devicecode",  "token_request_endpoint_url": "https://login.microsoftonline.com/<tenant>/oauth2/v2.0/token",  "token_request_params": {    "client_id": "your_client_id",    "scope": "api://your-app/.default"  }}

    Only PKCE (web-based) and Device Code flows are supported.

  3. Set file permissions:

    • Ensure that the .netapp file is not readable by other users/groups for security reasons.

    • On Unix-like systems, you can set the permissions using the following command:

      sh
      chmod 600 ~/.netapp
    • On Windows, you can set the file permissions through the file properties dialog.

[!TIP] There is an Examples folder in the repository that contains a .netapp.example file. This file provides examples of how your .netapp file should look. You can use this as a reference when creating your own .netapp file.

Running with uvx

You can run the MCP server instantly, without installing anything globally.

[!NOTE] Authentication is initiated on the first tool call, not at server startup. When the first tool call is initiated: if you are using the PKCE flow, a browser window will open; if you are using the device code flow, the device code details will be printed to the MCP server's console logs.

Run pre-built package from PyPI
sh
# Run the latest stable versionuvx --from netapp-aide-mcp server
# Run a specific versionuvx --from netapp-aide-mcp==1.0.0 server
  • server script launches the MCP server
Build and run from source
sh
# Clone the repogit clone https://github.com/NetApp/aide-mcp-servercd aide-mcp-server
# Optional: check out a specific release# git checkout tags/release-v1.0.0
# Retrieve the directory path for the cloned repoexport AIDE_MCP_REPO_PATH=$(pwd)
uvx --from $AIDE_MCP_REPO_PATH server
  • server script launches the MCP server
Example JSON config

To use this MCP server with an MCP client, you need to configure the client to use this server. For many clients (such as VS Code, Claude Desktop, and LMStudio), this requires editing a config file in JSON format (often named mcp.json). Below is an example. Refer to the documentation for your MCP client for specific formatting details.

[!NOTE] Most MCP clients will take care of starting the MCP server. You typically do not need to start the server yourself. As always, it's best to refer to the documentation for your MCP client for details on how it handles MCP servers.

json
{	"servers": {		"netapp-aide-mcp": {			"type": "stdio",			"command": "uvx",			"args": [				"--from",				"netapp-aide-mcp",				"server"			]		}	}}

Troubleshooting

  • Ensure your .netapp file is present and correctly formatted.
  • Check that Python 3.10+ and uv are installed.
  • Ensure that your MCP client is compatible with the stdio transport; most desktop clients (e.g. VS Code, Claude Desktop, LMStudio) are, but some hosted clients are not.
  • If you are using the device code auth flow, check the MCP server console logs for the device code details. The device code details will be printed to the logs when the first tool call is initiated.
  • If your client is not invoking an MCP tool, try adding "Be sure to use NetApp AIDE" to your prompt.

MCP Registry metadata

mcp-name: io.github.NetApp/aide-mcp-server

License

Distributed under the terms of the BSD 3-Clause License (see the LICENSE file in the repository).

Source: README.md at commit d37b591

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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
  • License10 pts

Other Aide integrations