Aide Mcp Server

io.github.NetApp由 GitHub 帳號 NetApp 發布v1.0.0更新於 Oct 24, 2026

MCP server for NetApp AI Data Engine

發布方自己的服務:Aide

概覽

AI 產生的概覽

本機 MCP 伺服器,讓助理透過 NetApp AI Data Engine 的 RAG 介面進行語意檢索並回傳相關文件。

可以做什麼
  • 檢索文件:向 NetApp AI Data Engine 的 RAG API 送出查詢,由其向量式語意相似度搜尋回傳相關文件。
  • 首次呼叫時驗證:第一次工具呼叫會啟動 OAuth 登入,可選瀏覽器 PKCE 流程或裝置代碼流程。
適用情境
適用於組織已部署 NetApp AI Data Engine、希望助理在對話中從該已索引文件庫取用內容的情境,尤其是同一台電腦上的桌面 MCP 用戶端。
執行需求
以 Python 套件 netapp-aide-mcp 透過 uvx 在本機以 stdio 執行,需要 Python 3.10 以上與 uv。家目錄下的 .netapp JSON 檔需填寫 RAG 檢索 API 位址、SSL 驗證設定、驗證流程、Microsoft Entra 權杖端點、client_id、redirect_uri 與 scope。完成登入需要瀏覽器或另一台裝置。未宣告任何環境變數或標頭。
安裝前請注意
設定檔 .netapp 含 client_id、租用戶端點與 scope,README 建議將其權限限制為僅本人可讀。登入會開啟瀏覽器或在伺服器日誌中列印裝置代碼,能存取日誌者可能看到。查詢內容與檢索結果會送往所設定的 AIDE 端點與 Microsoft 身分平台。僅支援 stdio 傳輸的桌面用戶端可用。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Aide Mcp Server,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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

來源:README.md,提交 d37b591

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v1.0.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Aide 整合