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: ReadsREADME.mdfrom the specified path.update_all: Overwrites/updatesREADME.mdwith new content provided by the client.- Arguments:
path(string, optional) - Absolute path to project root.content(string, required forupdate_all) - The new content forREADME.md.
2. Test Management
The agent can manage the project's tests in a unified workflow.
- Tool:
test - Action:
test - Functionality:
- Writes the provided test
codetotest_path. - Runs the project's test suite (
npm test). - Reports output and errors to
test.md.
- Writes the provided test
- 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.
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": ["/home/mc/Desktop/mcpserver/dist/index.js"]
}
}
}
{
"mcpServers": {
"my-job-server": {
"command": "node",
"args": ["/home/mc/Desktop/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": "/home/mc/Desktop/ServiceApp",
"test_path": "tests/login.test.js",
"code": "describe('Login', () => { ... });"
}
}
The server will:
- Save
tests/login.test.js. - Run
npm test. - Report full results to
test.md.
Troubleshooting
- Path Issues: Always provide the
pathargument. - npm test: The
testaction requires a validtestscript in the project'spackage.json.