Sorry, this is a bit of an edge case. And you probably have your hands tied on the solutions available on fixing this properly. It's also more of a macOS issue than the extension itself.
Description:
Running the Bear Notes MCP server via a Claude Cowork scheduled job constantly triggers macOS file access prompts for the Bear SQLite database. This issue is specific to background Cowork jobs; standard foreground chat interactions in Claude Desktop persist permissions correctly.
Cause:
macOS TCC fails to anchor the "Allow" choice to the background process (likely due to the dynamic execution of npx or the .mcpb bundle), treating each scheduled run as a new execution context.
Steps to Reproduce:
- Create a Claude Cowork scheduled job that queries Bear Notes.
- When the background job triggers, macOS prompts for data access.
- Click "Allow" (the query succeeds).
- Let the next scheduled job run -> macOS prompts for permission again.
Workaround 1 - Give full disk access to node
This is super dangerous and not something I'm personally comfortable with
- System Settings > Privacy & Security > Full Disk Access
- Add the path to
node
Workaround 2 - Give full disk access to a "burner node"
cp /path/to/node /Users/YOUR_USER/bin/claude-node
- System Settings > Privacy & Security > Full Disk Access, Add the path to
claude-node
- Use the following MCP server config.
"bear-notes": {
"command": "/Users/YOUR_USER/bin/claude-node",
"args": [
"/path/to/npx",
"-y",
"bear-notes-mcp@latest"
]
}
Sorry, this is a bit of an edge case. And you probably have your hands tied on the solutions available on fixing this properly. It's also more of a macOS issue than the extension itself.
Description:
Running the Bear Notes MCP server via a Claude Cowork scheduled job constantly triggers macOS file access prompts for the Bear SQLite database. This issue is specific to background Cowork jobs; standard foreground chat interactions in Claude Desktop persist permissions correctly.
Cause:
macOS TCC fails to anchor the "Allow" choice to the background process (likely due to the dynamic execution of npx or the .mcpb bundle), treating each scheduled run as a new execution context.
Steps to Reproduce:
Workaround 1 - Give full disk access to node
This is super dangerous and not something I'm personally comfortable with
nodeWorkaround 2 - Give full disk access to a "burner node"
cp /path/to/node /Users/YOUR_USER/bin/claude-nodeclaude-node