sync_nei_projectLABSCO SUMMARY
Three search modes because the thing you have in hand varies.
Sometimes you have a URL path, sometimes a Chinese interface name, and sometimes just a link someone pasted in chat — and each of those wants a different lookup. Splitting them into separate tools means the client picks correctly rather than fuzzy-matching a URL. The cache is per process, so after a colleague publishes a change, sync_nei_project is the thing to reach for before assuming the definition is wrong.
What it is
A FastMCP server for the NEI interface-management platform, aimed at the moment you are writing code against a backend contract and need to find the right definition. It pulls the project's data once, keeps it in memory for the life of the process, and offers three different ways of searching it plus a manual refresh for when a colleague has just changed something.
What you get
search_interfaces_by_urimatches loosely on the interface pathsearch_interfaces_by_namematches loosely on the interface namesearch_interfaces_by_urlresolves a NEI detail link exactly, using itspidandid— so pasting a link from a colleague finds the interfacesearch_groups_by_namefinds the business groups a project is divided intosync_nei_projectforces a pull from the remote platform and refreshes the cache, for when a definition changed minutes ago- In-memory caching, so repeat lookups within one session do not hit the NEI server again
Requirements
Two environment variables: SERVER_URL for your NEI instance and PROJECT_ID for the project you are working in. Run it through npx from the published @leila329/nei-mcp-server package, or point at the source with tsx during development. Package @leila329/nei-mcp-server, version 0.0.17. Node.js v20 or higher is recommended. This assumes your team already runs NEI — it is not useful without one.
Setup effort
Add the configuration to your client
USE CASES
01
Writing a call against an endpoint you half-remember
Search by path fragment and read back the definition rather than opening the NEI web UI.
02
Following a link someone pasted
Give the detail URL directly and get the exact interface, no guessing.
03
Getting oriented in an unfamiliar project
List the business groups first to see how the interfaces are organised.
04
Working right after a backend change
Force a sync so the in-memory cache reflects what was just published.
5 tools
Listed in project docs. Your client may show a different list.
search_interfaces_by_urisearch_interfaces_by_urlsearch_interfaces_by_namesearch_groups_by_nameBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Requires
npx on PATH
INSTALLATION
Connect your client
This one is configured rather than run — your client needs the configuration block, not a command.
Server setup
JSON
{
"mcpServers": {
"nei-mcp-server": {
"command": "npx",
"args": [
"-y",
"@leila329/nei-mcp-server"
],
"env": {
"SERVER_URL": "<YOUR_SERVER_URL>",
"PROJECT_ID": "<YOUR_PROJECT_ID>"
}
}
}
}In the configuration, SERVER_URL is the address of your NEI platform and PROJECT_ID is the id of your NEI project.
