MCP NLX Node.js Server
Description
# MCP NLX Node.js Server ## Project Description This project is a Node.js server implementation for the Model Context Protocol (MCP) using the NLX framework. It provides a server that can handle tool requests and communicate with an NLX application via API calls. ##…
About
# MCP NLX Node.js Server ## Project Description This project is a Node.js server implementation for the Model Context Protocol (MCP) using the NLX framework. It provides a server that can handle tool requests and communicate with an NLX application via API calls. ## Configuration ### Claude Desktop 1. Open your Claude…
Details
- Author
- nlxai
- Downloads
- 117
- Categories
- Other
Jump to
- Implements Model Context Protocol (MCP) server via NLX framework
- Communicates with NLX application through API calls
- Uses standard input/output transport for MCP
- Supports Claude Desktop integration
- Requires Node.js version 18 or later
- Uses semantic-release for automated versioning
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
MCP NLX Node.js ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
Install dependencies with npm install, set the NLX_APP_URL and NLX_API_KEY environment variables, then start the server with npm run start. For Claude Desktop, add the provided JSON configuration to claude_desktop_config.json.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mcp nlx node.js server": {
"nlx": {
"command": "npx",
"args": [
"-y",
"@nlxai/mcp-nodejs-server"
],
"env": {
"NLX_API_KEY": "",
"NLX_APP_URL": ""
}
}
}
}
}McpServers
{
"nlx": {
"command": "npx",
"args": [
"-y",
"@nlxai/mcp-nodejs-server"
],
"env": {
"NLX_API_KEY": "",
"NLX_APP_URL": ""
}
}
}MCP NLX Node.js Server
Project Description
This project is a Node.js server implementation for the Model Context Protocol (MCP) using the NLX framework. It provides a server that can handle tool requests and communicate with an NLX application via API calls.
Configuration
Claude Desktop
1. Open your Claude Desktop configuration:
open ~/Library/Application\ Support/Claude/claude_desktop_config.json
2. Add the NLX Application configuration:
{
"mcpServers": {
"nlx": {
"command": "npx",
"args": ["-y", "@nlxai/mcp-nodejs-server"],
"env": {
"NLX_API_KEY": "",
"NLX_APP_URL": ""
}
}
}
}
Setup
Prerequisites
- Node.js (version 18 or later)
- npm (Node Package Manager)
Installation
1. Clone the repository:
git clone <repository-url>
2. Navigate to the project directory:
cd nlx-mcp-server
3. Install the dependencies:
npm install
Usage
Environment Variables
- NLX_APP_URL: The base URL of your NLX application.
- NLX_API_KEY: The API key for authenticating requests to your NLX application.
Running the Server
To start the server, run the following command:
npm run start
The server will start and listen for requests via standard input/output.
Troubleshooting
Common Issues
- Module Not Found Errors: Ensure that all dependencies are correctly installed and that the paths in the import statements are correct.
- Environment Variables: Make sure that NLX_APP_URL and NLX_API_KEY are set correctly in your environment.
Linter Errors
- Cannot find module: Verify that the module paths are correct and that the modules are installed.
- Implicit 'any' type: Consider adding TypeScript type definitions to avoid implicit 'any' types.
Release Management
Automated Releases with Semantic Release
This project uses semantic-release to automate the versioning and release process. Semantic Release ensures that the version number and changelog are automatically updated based on the commit messages.
Commit Message Format
Semantic Release uses the Angular commit message conventions. Here is a brief overview of the format:
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing or correcting existing tests
- chore: Changes to the build process or auxiliary tools and libraries such as documentation generation
How to Release
To create a new release, simply push your changes to the main branch. The CI/CD pipeline will automatically run semantic-release to determine the next version number, update the changelog, and publish the release.
Ensure your commit messages follow the Angular conventions to trigger the correct version updates.
In dire cicd situations, you can manually trigger a release by running the following command:
npx semantic-release --no-ci
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
