mcp-node

MCP server from Akhildas-ts/mcp-node-server

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio akhildas-ts-mcp-node-server node server.js \
  --env PORT="Port for MCP server (default 3000)" \
  --env MCP_TOKEN="Optional authentication token for securing MCP endpoints"

How to use

This MCP server (mcp-node) provides a Node.js implementation of the MCP protocol for processing model context requests. It exposes an MCP-compatible RPC interface that clients can connect to in order to load models, initialize contexts, run inference or transformation tasks, and retrieve results. The server is configured via environment variables and runs as a standalone process, listening on a configurable port. Typical usage involves starting the server, establishing a connection with MCP clients, and issuing requests to create or reuse a model context, then sending task requests and aggregating the returned context or results. If an authentication token is configured, clients must provide the token to authenticate requests.

Once running, you can interact with the server using the MCP client tooling supported by this repository (or any MCP-compatible client). Typical capabilities include: loading or registering models or data contexts, creating and managing model contexts, submitting tasks, monitoring progress, and fetching results. Ensure your client targets the server URL and port defined by the PORT environment variable, and supply MCP_TOKEN if required by the server configuration.

How to install

Prerequisites:

Node.js (recommended LTS) and npm/yarn installed
Basic familiarity with MCP client tooling or HTTP/WebSocket RPC

Steps:

Clone the repository: git clone https://github.com/akhildas-ts-mcp-node-server.git cd akhildas-ts-mcp-node-server
Install dependencies: npm install

or

yarn install
Configure environment variables (example):

On Linux/macOS

export PORT=3000 export MCP_TOKEN=your-secure-token

On Windows (PowerShell)

$env:PORT=3000 $env:MCP_TOKEN="your-secure-token"
Start the server: node server.js

or, if a start script exists in package.json, use:

npm start
Verify the server is running by hitting the configured port or using a MCP client to connect and issue a simple ping or health check request.

Additional notes

Notes and tips:

If PORT is already in use, either stop the other process or choose a different port via the PORT environment variable.
If MCP_TOKEN is set, ensure your MCP clients include the token in requests for authentication.
Check server logs for startup messages, connection attempts, and error details to diagnose issues quickly.
If deploying with Docker or other orchestrators, map ports and pass environment variables accordingly (e.g., -e PORT=3000 -e MCP_TOKEN=...).
Ensure that you have the correct MCP client tooling compatible with this server version to avoid protocol mismatches.

Related MCP Servers

zen

1.1k

Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage

MCP -Deepseek_R1

A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)

mcp-fhir

A Model Context Protocol implementation for FHIR

mcp

Inkdrop Model Context Protocol Server

mcp-appium-gestures

This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..

dubco -npm

The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.