YOUR CODE
Workspace
A project directory under an explicitly configured allowed root.
C# · .NET 10 · Model Context Protocol
Give your AI tools. Keep your code local.
LocalCodingMcp gives ChatGPT, Grok, and other MCP clients controlled access to your workspace: files, search, git, shell, history, and reusable skills — behind explicit local guardrails.
Your workspace to your AI client, with the MCP boundary visible.No cloud code store required by LocalCodingMcp.
/workspace/project
LOCALCODINGMCP
Sandboxed tools
Path checks, sensitive-file filtering, command timeout, history, and skill state.
HTTPS
Tunnel
Expose the MCP endpoint through your chosen HTTPS tunnel, such as ngrok.
AI CLIENT
ChatGPT / Grok
The connected model discovers MCP tools and can invoke them for your request.
For coding work, server instructions direct the client to load enabled skills before using LocalCodingMcp coding tools.Local-first control plane
Tool surface
A small surface with real leverage.
The server exposes focused tools instead of pretending to be a full remote IDE. The client chooses what to call; the server enforces the local boundaries.
- Workspace
- Open approved project roots and keep subsequent calls scoped to a workspace identifier.
- Files
- List, read, write, patch, move, create, and delete files inside the sandbox.
- Search
- Search repository text without handing the model unrestricted filesystem access.
- Git
- Inspect status, diff, and log from the workspace the model is already operating in.
- Shell
- Run commands with the workspace as the working directory and a configured timeout.
- History
- Persist sanitized tool-call history so activity can be inspected without retaining sensitive arguments.
- Skills
- Create, read, update, enable, disable, and load reusable local instructions for compatible MCP clients.
01
02
03
04
05
06
07
Skill-aware MCP
The workflow can arrive with the tools.
Enabled skills are persisted locally. The server advertises how they should be loaded; actual host/model compliance is not guaranteed by the server alone.
Request
User asks for work
Coding, debugging, design, planning, or review.
Load
LoadEnabledSkills
The MCP tool returns complete content for every enabled skill.
Apply
Relevant enabled skills
superpowershallmarkcavemanponytail
If superpowers is enabled, its process-selection rules are applied first.
Act
Coding tools
Workspace, files, search, git, shell, and history remain sandboxed.
Built-ins start disabled.Opt into the instructions you want instead of silently changing model behavior.
State persists.Enable/disable metadata survives normal process, Docker, and Termux restarts when the data directory is persisted.
Custom skills stay local.Each skill lives as
<skills>/<name>/SKILL.md under the configured skills directory.Guardrails
Local access, explicitly bounded.
The boundary is implemented in the server, not left as a prompt suggestion.
AllowedRoots
Workspace paths must stay beneath configured roots.
Traversal + symlinks
Path resolution rejects traversal and symlink escape outside approved roots.
Sensitive files
Configured patterns block files such as environment files, credentials, keys, and certificates.
Shell timeout
Commands run in the workspace with a configurable execution timeout.
Sanitized history
Persisted call history redacts sensitive argument fields and truncates oversized values.
Constrained skill names
Skill names use a restricted character set and cannot escape the configured skill directory.
Run it
Clone. Start. Connect.
Docker is the shortest path on a desktop. TermuxHost packaging is available for Android/ARM64 hosting.
Docker + ngrok
git clone https://github.com/dhhieu113pro/local-coding-mcp.git
cd local-coding-mcp
docker compose up -d
docker compose --profile ngrok up -d