Memory MCP Server
Persistent memory using a knowledge graph
{
"mcpServers": {
"io-github-netapp-aide-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}No install config available. Check the server's README for setup instructions.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP server for NetApp AI Data Engine
Is it safe?
No package registry to scan.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Commit history unknown.
Will it work with my client?
Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
No automated test available for this server. Check the GitHub README for setup instructions.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationNo known vulnerabilities.
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Pre-build reality check. Scans GitHub, HN, npm, PyPI, Product Hunt — returns 0-100 signal.
Hash-verified file editing MCP server with token efficiency hook. 11 tools for AI coding agents.
MCP Security Weekly
Get CVE alerts and security updates for io.github.NetApp/aide-mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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".
Before running the server, you need to create a .netapp file in your home directory with the necessary configuration.
Create the .netapp file:
~ on Unix-like systems or C:\Users\YourUsername on Windows)..netapp.Add the JSON configuration:
.netapp file in a text editor.For PKCE flow: (Recommended if you have a browser available on your machine)
{
"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.)
{
"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.
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:
chmod 600 ~/.netapp
On Windows, you can set the file permissions through the file properties dialog.
[!TIP] There is an
Examplesfolder in the repository that contains a.netapp.examplefile. This file provides examples of how your.netappfile should look. You can use this as a reference when creating your own.netappfile.
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 the latest stable version
uvx --from netapp-aide-mcp server
# Run a specific version
uvx --from netapp-aide-mcp==1.0.0 server
server script launches the MCP server