Mcplocalserver

Provides a local MCP server that enables seamless tool integration and read/write of local guides and prompts.

typescript

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "michalpawlik93-mcplocalserver": {
      "command": "node",
      "args": [
        "C:\\pathToMcpLocalServerProjectInYourPC\\build\\index.js"
      ],
      "env": {
        "PROMPT_DIR": "C:\\pathToYourProject\\mcpLocalServer\\data\\prompts",
        "GUIDE_FILES_DIR": "C:\\pathToYourProject\\mcpLocalServer\\data"
      }
    }
  }
}

MCP Server is a local Node.js tool for Windows that acts as a middleware bridge between large language model tools and your development environment. Run it locally alongside your IDE to simplify communication with Copilot Agents and similar tooling, without exposing you to remote endpoints. This server uses the MCP SDK to enable browser-based inspection and testing of its capabilities.

How to use

You interact with the MCP Server through an MCP-compatible client. Start your local MCP server, then connect your IDE’s Copilot-like agent or client to the local endpoint. Once connected, you can list available guides and prompts, read local files, and ask the agent to generate code or guidance using the content you’ve prepared in your local data folders.

How to install

Prerequisites you need before installing: Node.js installed on Windows and a modern shell (PowerShell or Command Prompt). You should also have a suitable editor or IDE ready if you plan to test through an integrated Copilot-like experience.

Install dependencies by running the package manager in your project directory.

npm install

Build the project to generate the runtime artifacts used by the server.

npm run build

Start browser testing support by running the Inspector tool against the built entry point.

npx @modelcontextprotocol/inspector build/index.js

Additional configuration and usage notes

Environment variables help the server locate local guide and prompt files. You set them in a .env file or in the terminal when you start the server.

Examples of required environment variables include the paths to your local guide files and prompts.

If you use the Microsoft Visual Studio Code Copilot integration, you can wire up a local MCP server entry in your project configuration to point to the built runtime.

Available tools

ListAvailableFilesTool

Lists all .txt guide files located in the data directory, helping you discover the available guides you can load.

ListPromptsTool

Lists all prompt files located in the data/prompts directory, enabling you to choose which prompts to load for guidance.

ReadLocalFileTool

Reads and returns the content of a file from either data or data/prompts, depending on the file prefix used.

Built by

VeilStrat

AI signals for GTM teams