
Nex
io.github.nex-crmPublished by GitHub account nex-crmv1.0.0Updated Oct 24, 2026
Organizational context & memory for AI agents. Connect 100+ tools into one knowledge graph.
Overview
Nex gives an assistant organizational context and memory by connecting many tools into a single knowledge graph.
- What you can do
- Nex is an MCP server that provides organizational context and memory for AI agents. It is described as connecting over 100 tools into one knowledge graph, so an assistant can draw on linked information across those tools. The manifest does not list individual tools, so the exact operations are not documented here.
- When to use it
- Consider it when an assistant needs shared organizational memory or context spanning many connected tools, rather than access to a single system. It is a desktop-only local process, so it suits individual desktop setups.
- Requirements
- Runs as a local process over stdio, installed from the npm package @nex-ai/nex, so Node.js and npm are needed. It requires an API key supplied through the environment variable NEX_API_KEY; the description says you can sign up with the provider or use a register tool to obtain one. Network access is implied by the hosted service.
Installation
In SourceWeft
- Open Nex in the dashboard and add it to a workspace.
- 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
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
25% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.