NEI MCP Server is an MCP server that integrates AI assistants with the NEI interface management platform to query project resources and API definitions. Built on fastmcp, this server connects developers and software teams directly to their NEI projects from MCP-compatible clients. It enables users to look up API specifications, inspect data models, and locate business groups without switching back and forth between their code editor and the browser interface. The server provides tools to search interfaces by path, name, or specific URL parameters, as well as locate project groups. It includes an internal memory cache to minimize redundant requests to the remote NEI server during runtime, while supporting explicit project synchronization whenever specifications are updated on the backend. This setup allows developers to reference accurate API contracts during planning, coding, and debugging workflows.
Category: Project & Task Management
Tags: nei, project-resources, resource-management
claude_desktop_config.json). 3. Add nei-mcp-server to the mcpServers section using either the local source or the published npm package: json { "mcpServers": { "nei-mcp-server": { "command": "npx", "args": [ "-y", "@leila329/nei-mcp-server" ], "env": { "SERVER_URL": "<YOUR_NEI_SERVER_URL>", "PROJECT_ID": "<YOUR_PROJECT_ID>" } } } } 4. Replace <YOUR_NEI_SERVER_URL> and <YOUR_PROJECT_ID> with your specific NEI deployment address and project identifier. 5. Save the configuration and restart your MCP client.Part of MCP Servers
NEI MCP Server allows AI clients to interact with the NEI interface management platform. It exposes tools to synchronize project metadata, search interfaces by URI path, search by interface name, lookup endpoints using NEI detail URLs, and search business groups within a designated project.
You can configure NEI MCP Server in your MCP client configuration file by invoking npx with the package @leila329/nei-mcp-server. You must supply your NEI platform endpoint and project ID under the environment variables SERVER_URL and PROJECT_ID.
The server stores retrieved project data in an in-memory cache during its execution to prevent redundant network calls to the NEI platform. The cache resets when the server restarts. Users can also call the sync_nei_project tool to manually refresh data from the remote server.
NEI MCP Server works with any client supporting the Model Context Protocol, including Claude Desktop, Cursor, and the FastMCP inspect developer tool used for local testing.