
Nexora
io.github.felixbaumannkontakt-techPublished by GitHub account felixbaumannkontakt-techv1.0.0Updated Oct 24, 2026
NEXORA: Tools fuer Vertrieb, Website-Verwaltung und Holding-Verwaltung (LiveRelay Group).
Overview
Nexora is a local MCP server from LiveRelay Group that gives an assistant tools for sales, website management and holding administration.
- What you can do
- Work with sales data such as leads, projects and companies stored in local JSON files under a configurable data directory, according to the description and environment variable notes. Manage website-related tasks and holding administration through the same server. The manifest lists no individual tools, so the exact operations available are not documented in the supplied material.
- When to use it
- Consider it if you want an assistant to work with LiveRelay Group's sales, website and holding data on your own desktop, and you are prepared to inspect the package to learn what its tools actually do.
- Requirements
- Runs as a local process over stdio, installed from the npm package @liverelaygroup/nexora-mcp-server, so a Node.js runtime is needed. Desktop only; no web execution. Optionally set NEXORA_DATA_DIR to point at the data directory; the default is ./data. No authentication is declared.
Installation
In SourceWeft
- Open Nexora 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 20, 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.