LocalEngineering.McpServer

Name: LocalEngineering.McpServer
Author: rajitharx

by rajitharx

GitHub

No known CVEs

No license

Actively maintained

Last commit 18d ago

Works with most clients

Transport: sse, http

0 tools

Grade F

Edit this pageView history

Other

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopsse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "localengineering-mcpserver": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/localengineering-mcpserver)](https://mcppedia.org/s/localengineering-mcpserver)

Read me

What LocalEngineering.McpServer does

No description provided.

This server is thin — proceed with caution. Help improve this page →

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

28/100across 5 weighted dimensions

How we score →

0255075100

−72

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

No package registry to scan.

Help improve this page

This server is missing a description. Tools and install config are also missing.If you've used it, help the community.

Add information

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is LocalEngineering.McpServer safe to use?: LocalEngineering.McpServer has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install LocalEngineering.McpServer?: LocalEngineering.McpServer can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with LocalEngineering.McpServer?: LocalEngineering.McpServer is compatible with claude-desktop, cursor, claude-code. It uses sse and http transport.
Is LocalEngineering.McpServer actively maintained?: LocalEngineering.McpServer is actively maintained — last commit was 18 days ago.

Similar servers

Others in other

View all →

Pi Lean Ctx95

Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.

Apify MCP Server

97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server

507 6

Caveman Shrink93

MCP proxy that compresses prose fields (tool descriptions, etc.) using caveman rules. Same accuracy, fewer context tokens.

70.9k 4

MCP Security Weekly

Get CVE alerts and security updates for LocalEngineering.McpServer and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Tests

A test project has been added under tests/LocalEngineering.McpServer.Tests. It contains:

Unit tests for SystemTools (SystemToolsTests.cs).

A simple integration test that starts the app in-memory via WebApplicationFactory<Program> (IntegrationTests.cs).

Run the test suite from the repository root:

dotnet test tests/LocalEngineering.McpServer.Tests --verbosity normal

Notes:

Integration tests use an exposed partial Program type to support WebApplicationFactory (see src/Program.Partial.cs).

The current integration test sends a GET to /mcp and asserts the server does not return a 5xx. A 405 Method Not Allowed response was observed during test execution — this is expected because the MCP transport may require specific HTTP methods or payloads.

Files of interest

src/Program.cs — application startup and MCP registration

src/Program.Partial.cs — small partial type to enable WebApplicationFactory<Program> in tests

tests/LocalEngineering.McpServer.Tests/LocalEngineering.McpServer.Tests.csproj — test project manifest

tests/LocalEngineering.McpServer.Tests/SystemToolsTests.cs — unit tests

tests/LocalEngineering.McpServer.Tests/IntegrationTests.cs — integration test

Frequently Asked Questions

Is LocalEngineering.McpServer safe to use?

LocalEngineering.McpServer has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install LocalEngineering.McpServer?

LocalEngineering.McpServer can be installed by cloning its GitHub repository and following the setup instructions in the README.

What AI clients work with LocalEngineering.McpServer?

LocalEngineering.McpServer is compatible with claude-desktop, cursor, claude-code. It uses sse and http transport.

Is LocalEngineering.McpServer actively maintained?

LocalEngineering.McpServer is actively maintained — last commit was 18 days ago.

LocalEngineering.McpServer

Lightweight MCP (Model Context Protocol) server used for local engineering and testing. This repository hosts a minimal ASP.NET Core application that exposes an MCP endpoint and a few helper tools.

Overview

The web app is in src/ and targets .NET 8.0.
The server registers MCP tools (see Program.cs) and exposes the MCP HTTP transport at /mcp.

Prerequisites

.NET 8 SDK
dotnet CLI available on PATH

Run the application

From the repository root you can run the server with:

dotnet run --project src

The server listens on http://0.0.0.0:5050 by default.

Tests

A test project has been added under tests/LocalEngineering.McpServer.Tests. It contains:

Unit tests for SystemTools (SystemToolsTests.cs).
A simple integration test that starts the app in-memory via WebApplicationFactory<Program> (IntegrationTests.cs).

Run the test suite from the repository root:

dotnet test tests/LocalEngineering.McpServer.Tests --verbosity normal

Notes:

Integration tests use an exposed partial Program type to support WebApplicationFactory (see src/Program.Partial.cs).
The current integration test sends a GET to /mcp and asserts the server does not return a 5xx. A 405 Method Not Allowed response was observed during test execution — this is expected because the MCP transport may require specific HTTP methods or payloads.

Files of interest

src/Program.cs — application startup and MCP registration
src/Program.Partial.cs — small partial type to enable WebApplicationFactory<Program> in tests
tests/LocalEngineering.McpServer.Tests/LocalEngineering.McpServer.Tests.csproj — test project manifest
tests/LocalEngineering.McpServer.Tests/SystemToolsTests.cs — unit tests
tests/LocalEngineering.McpServer.Tests/IntegrationTests.cs — integration test

Next steps

Add integration tests that call MCP endpoints with the correct method/payload to exercise registered tools.
Expand unit tests as new logic is added.