How ricardoshuree/mcp-local works
mcp-local-erp is a local MCP server that gives Claude Desktop scoped read, directory-listing, and controlled write access to a configured project. The main workflow is: Claude requests project reads or proposes a change; a human reviews and approves or rejects the plan; an approved, in-scope write is validated, annotated, persisted, and audited. The harness keeps plan state and its audit log in the server folder, separate from the managed project. The map follows the README and sampled server and harness code; registration-script internals are not mapped.
Main entry points: server.py MCP server · change_control.py Change-control logic · config.yaml Project config
Components 8
Project access
- MCP server
server.py - Project config
config.yaml - Managed project files
Change control
- Change-control logic
change_control.py
Harness records
- Plan state
change_control.py - Audit log
change_control.py
Other components
- Human reviewer
- Claude Desktop
Connections 9
- Claude Desktop → MCP server: calls MCP tools
- MCP server → Project config: loads settings
- MCP server → Managed project files: reads and lists
- MCP server → Change-control logic: delegates harness tools
- MCP server → Change-control logic: checks write authorization
- Change-control logic → Plan state: loads and saves plans
- Change-control logic → Audit log: appends events
- Human reviewer → Claude Desktop: reviews plan
- MCP server → Managed project files: writes approved file