ilkergonenc/mcp-local-dev
If you are the rightful owner of mcp-local-dev and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to dayong@mcphub.com.
A minimal local Model Context Protocol (MCP) server for AI-assisted development environments.
MCP Local Dev
A minimal local Model Context Protocol (MCP) server for AI-assisted development environments. It allows you to expose your local codebases, configuration files, and reference documentation as structured resources accessible through tools like Cursor or VS Code AI.
🌱 Overview
This project is designed to serve as a template for developers who want to:
- Create a local MCP server quickly.
- Reference existing projects and best practices.
- Provide contextual data to AI coding environments.
It includes:
- A lightweight STDIO-based server.
- A simple TypeScript configuration.
- Example resource directory support.
🚀 Quick Start
# Clone and install dependencies
git clone https://github.com/ilkergonenc/mcp-local-dev.git
cd mcp-local-dev
npm install
# Start development mode
npm run server:dev
🔗 Connecting mcp-local-dev to Cursor & VS Code
Your local MCP server can be connected to both Cursor and VS Code MCP extension. The configuration format is the same JSON structure, but they’re stored in different locations.
🧩 For VS Code MCP Extension
Create (or update) .vscode/mcp.json in your workspace:
{
"servers": {
"mcp-local-dev": {
"type": "stdio",
"command": "node",
"args": ["build/server.js"],
"cwd": "${workspaceFolder}",
"dev": {
"watch": "build/**/*.js",
"debug": { "type": "node" }
}
}
}
}
VS Code uses ${workspaceFolder} automatically,
so this setup will work regardless of your local directory path.
💬 For Cursor IDE
Open Settings → MCP Servers → Add Server and enter the following configuration manually:
{
"name": "mcp-local-dev",
"type": "stdio",
"command": "node",
"args": ["build/server.js"],
"cwd": "."
}
💡 In Cursor,
${workspaceFolder}is not needed — use"cwd": "."instead to default to the project root.
🧠 Notes
-
Use the
build/server.jsversion for stability (already compiled). -
If you’re actively editing the MCP code, you can temporarily switch to:
"command": "npm", "args": ["run", "server:dev"] -
Both environments (Cursor and VSCode) will automatically detect the server once it’s started and list available tools and resources.
📁 Project Structure
mcp-local-dev/
│
├── src/
│ └── server.ts # Main MCP server
│
├── resource/ # Place your reference files here
│ └── readme.md # Example resource file
│
├── tsconfig.json
├── package.json
└── .gitignore
🧠 Use Case Example
You can connect this server to your development tools and query local project data like:
- Tech stack summaries
- Config or dependency insights
- Best practices from markdown documentation
- File or folder-level references
⚖️ License
MIT © İlker Gönenc