How to Configure MCP Server Permissions to Avoid Repeated Prompts
I set up an MCP server (things-mcp) to work with Claude Desktop, but every time I launched Claude, I got a pop-up asking for permission to access data. This became tedious quickly. Here’s how I solved it.
The Problem
There are two types of permission prompts you might encounter:
- macOS security prompts (TCC) — System dialogs like “uvx wants to access your reminders”
- Claude Desktop permission system — Claude asking to use specific MCP tools
The macOS prompts happen because uvx creates ephemeral environments each time, and macOS treats each as a new process requiring fresh permissions.
The Solution: Use uv tool install Instead of uvx
The key insight is that uvx creates temporary environments. Instead, install the MCP server permanently:
uv tool install things-mcp --python 3.11Then update your Claude Desktop config:
{ "mcpServers": { "things": { "command": "things-mcp", "args": [] } }}This creates a persistent installation where macOS permissions are granted once to the installed tool.
Alternative: Grant System Permissions
If you prefer using uvx, you can grant Full Disk Access to your terminal:
- Open System Settings > Privacy & Security > Full Disk Access
- Add your terminal app (Terminal.app, iTerm.app) or Claude Desktop
- Restart Claude Desktop
For things-mcp specifically, you only need Reminders access, not Full Disk Access.
Config Location
On macOS, your Claude Desktop config is here:
open ~/Library/Application\ Support/Claude/The config file is claude_desktop_config.json.
Troubleshooting
JSON validation error? Check your config:
cat ~/Library/Application\ Support/Claude/claude_desktop_config.json | python -m json.toolThings data not found? Make sure the Things app is installed and synced to Apple Reminders.
Comparison
| Approach | Security | Convenience | Use Case |
|---|---|---|---|
uvx | Higher (ephemeral) | Lower (repeated prompts) | Testing, one-time use |
uv tool install | Moderate (persistent) | Higher (no prompts) | Regular use, trusted tools |
Summary
The main takeaway: use uv tool install instead of uvx for MCP servers you use regularly. The ephemeral nature of uvx causes macOS to treat each run as a new process, triggering permission prompts. A permanent installation retains permissions across sessions.
Final Words + More Resources
My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me
Here are also the most important links from this article along with some further resources that will help you in this scope:
- 👨💻 MCP Documentation
- 👨💻 uv Documentation
Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!
Comments