Frequently asked
questions.

No. CodeMCP operates 100% on your local machine. All filesystem searches, reads, and edits occur over local stdio or localhost loopback HTTP (port 4173). There is zero cloud indexing or vector sync.

CodeMCP automatically denies tool access to patterns matching .env*, **/*.pem, **/*.key, and .git directories. Any attempt by an AI assistant to inspect or overwrite these files fails immediately with ACCESS_DENIED.

By default, command execution is disabled unless explicitly enabled via --allow-exec. Even when enabled, interactive approval prompts display the proposed command in your terminal for human keypress approval before execution.

No. You can launch CodeMCP on demand using npx codemcp, pnpm dlx codemcp, or bunx codemcp inside your target project directory. It runs in milliseconds without permanent global installation.

Claude Desktop launches MCP server processes in an isolated user daemon environment where the current working directory may not be your repository. Providing an absolute path (--project /path/to/repo) guarantees reliable root binding.

Yes. You can run multiple instances of CodeMCP on different local ports (e.g. --port 4173, --port 4174) or register distinct entries in your client configuration targeting separate project paths.

write_file creates a new file or completely replaces the contents of a target file. edit_file performs surgical find-and-replace on exact contiguous text blocks, drastically reducing model hallucinations and preserving surrounding code.

CONTEXT.md should be placed in the root of your project directory. CodeMCP automatically injects its contents during MCP protocol initialization, providing the AI assistant with coding guidelines, stack details, and constraints.

Run npx codemcp doctor in your terminal. This diagnostic command validates your Node.js version (must be >= 18), verifies stdio pipe responsiveness, checks port 4173 availability, and audits your codemcp.json syntax.

Pass the --verbose (or -v) flag when launching CodeMCP (npx codemcp -v). This streams all raw JSON-RPC 2.0 frames and tool invocation payloads to stderr for inspection.