This checklist helps you review a local MCP server’s command, permissions, transport, and failure behavior before enabling it. That matters because the process can often act with the same filesystem and credential access as its host.
Checklist
- Read the configured command, arguments, and working directory.
- Pin or verify the package or executable you are launching.
- Keep JSON-RPC messages on standard output; route diagnostics to standard error.
- Pass only the environment variables the server needs.
- Prefer read-only tools and narrow path allow-lists.
- Validate tool arguments and cap output size.
- Require confirmation for writes, commands, or external side effects.
- Confirm how the host stops orphaned or unresponsive processes.
- Inspect logs for secrets before sharing diagnostics.
Links
Closing thought
A short local MCP configuration can launch a highly capable process, so its review should be proportional to the capability—not to the number of lines.