NEXS MCP Server - Model Context Protocol server for portfolio management with NPM distribution
Most knowledge and memory work still happens through a UI a human drives. Nexs MCP MCP server moves it into the conversation instead. NEXS MCP Server - Model Context Protocol server for portfolio management with NPM distribution.
📦 NPM Package: https://www.npmjs.com/package/@fsvxavier/nexs-mcp-server
The server publishes 1 tool. What each one is for:
Installation — The Installation tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at @fsvxavier/nexs-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: NEXS_DATA_DIR, NEXS_STORAGE_TYPE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Nexs MCP's toolset — Installation — is a fair guide to whether it matches your workflow. It is maintained by fsvxavier; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Nexs MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Installation | The Installation tool exposed by this server. |
{
"mcpServers": {
"nexs-mcp": {
"command": "nexs-mcp",
"args": [],
"env": {
"NEXS_DATA_DIR": "/path/to/your/elements",
"NEXS_STORAGE_TYPE": "file"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| NEXS_DATA_DIR | Filesystem location the server is allowed to use. | Optional |
| NEXS_STORAGE_TYPE | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.