MCP server for reading/writing macOS defaults (settings)
list-domains:- equivalent to running
defaults domains
- equivalent to running
find:- equivalent to running
defaults find <word>
- equivalent to running
defaults-read:- equivalent to running
defaults read <domain> <key> - if
keyis not provided, the entire domain is read
- equivalent to running
defaults-write:- equivalent to running
defaults write <domain> <key> <value>
- equivalent to running
On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
Development/Unpublished Servers Configuration
``` "mcpServers": { "mcp-server-macos-defaults": { "command": "uv", "args": [ "--directory", "/path/to/mcp-server-macos-defaults", "run", "mcp-server-macos-defaults" ] } } ```Published Servers Configuration
``` "mcpServers": { "mcp-server-macos-defaults": { "command": "uvx", "args": [ "mcp-server-macos-defaults" ] } } ```To prepare the package for distribution:
- Sync dependencies and update lockfile:
uv sync- Build package distributions:
uv buildThis will create source and wheel distributions in the dist/ directory.
- Publish to PyPI:
uv publishNote: You'll need to set PyPI credentials via environment variables or command flags:
- Token:
--tokenorUV_PUBLISH_TOKEN - Or username/password:
--username/UV_PUBLISH_USERNAMEand--password/UV_PUBLISH_PASSWORD
Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.
You can launch the MCP Inspector via npm with this command:
npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-server-macos-defaults run mcp-server-macos-defaultsUpon launching, the Inspector will display a URL that you can access in your browser to begin debugging.