Skip to main content
Glama
Node.js MCP Server

Node.js MCP Server

by mustafa-can

MAIN ASPECTS

The ai is not human, we should simplify it and we can make it understand the prompt clearly for some regular tasks. Managing human behavior is not easy. We should not let the ai to behave like a human and to make the prompt processing difficult. We should let the ai to do its job and to make it understand the prompt clearly in regular cases. We must reduce the token usage. Otherwise it will be expensive.

Node.js MCP Server

A specialized MCP server focused on 3 Core Jobs for agentic workflows.

The 3 Jobs

1. Context Management & Learning

The agent can manage the project's documentation and "learn" the entire context.

  • Tool: md

  • Actions:

    • read_all: Reads README.md from the specified path.

    • update_all: Overwrites/updates README.md with new content provided by the client.

    • Arguments:

      • path (string, optional) - Absolute path to project root.

      • content (string, required for update_all) - The new content for README.md.

2. Test Management

The agent can manage the project's tests in a unified workflow.

  • Tool: test

  • Action: test

  • Functionality:

    1. Writes the provided test code to test_path.

    2. Runs the project's test suite (npm test).

    3. Reports output and errors to test.md.

  • Arguments:

    • path (string, optional) - Absolute path to project root.

    • test_path (string, required) - Relative path to the test file (e.g., tests/api.test.js).

    • code (string, required) - Content of the test file.

3. Build & Run

  • Tool: deploy

  • Actions:

    • dev: Runs the project in development mode.

    • prod: Builds the project and runs it.

    • Arguments:

      • path (string, optional) - Absolute path to project root.

Related MCP server: MCP Playground Server

Installation & Usage

1. Build the Server

cd /home/mc/Desktop/mcpserver
npm install
npm run build

2. Configuration (Claude / Antigravity)

Add to your MCP configuration file:

Location: ~/.config/Claude/claude_desktop_config.json (Linux)

{
  "mcpServers": {
    "job-server": {
      "command": "node",
      "args": ["path/to/mcpserver/dist/index.js"]
    }
  }
}
{
  "mcpServers": {
    "my-job-server": {
      "command": "node",
      "args": ["path/to/mcpserver/dist/index.js"]
    }
  }
}

3. Usage Examples

Manage Tests

To create a test, update it, or simply run existing tests (by re-submitting the code), use the test tool.

{
  "name": "test",
  "arguments": {
    "action": "test",
    "path": "path/to/ServiceApp",
    "test_path": "tests/login.test.js",
    "code": "describe('Login', () => { ... });"
  }
}

The server will:

  1. Save tests/login.test.js.

  2. Run npm test.

  3. Report full results to test.md.

Troubleshooting

  • Path Issues: Always provide the path argument.

  • npm test: The test action requires a valid test script in the project's package.json.

Available Tools

2 tools
calculateD

Inputs: operation (required), a (required), b (required).

get_system_infoD

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    D1.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: 'calculate' likely performs mathematical or computational operations, while 'get_system_info' retrieves system-related data. There is no overlap or ambiguity between these functions, making them easy for an agent to differentiate.

    Naming Consistency2/5

    The naming is inconsistent: 'calculate' uses a bare verb with no noun, while 'get_system_info' follows a verb_noun pattern. This mixing of conventions lacks a predictable pattern, though the names are still readable.

    Tool Count2/5

    With only 2 tools, this server feels too thin for a general-purpose Node.js domain, which typically involves many operations like file handling, networking, or process management. The count is insufficient to cover the implied scope effectively.

    Completeness1/5

    The tool surface is severely incomplete for a Node.js server, lacking basic operations such as file I/O, module management, or process control. The two tools provided do not offer meaningful coverage, leaving significant gaps that will cause agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers