Overview
What is Smart Workspace Manager?
Smart Workspace Manager is a secure, local-first Model Context Protocol (MCP) server that exposes your files, notes, and projects to AI assistants like Claude Desktop, Cursor IDE, and custom LLM workflows. Built for macOS (Silicon) developers, it bridges your private filesystem with Large Language Models.
How to use Smart Workspace Manager?
Clone the repository, create a Python virtual environment, install dependencies, configure a .env file with WORKSPACE_PATH and other options, then run python server.py. You can also launch it automatically via your MCP client’s configuration (e.g., Claude Desktop).
Key features of Smart Workspace Manager
- Resource discovery: files, folders, notes as structured MCP Resources.
- Smart search by name, path, or keywords.
- Document summarization for notes, articles, or plans.
- File creation, rename, move, and optional deletion.
- Configurable file types, size limits, and destructive tool control.
- Local-first privacy: data never leaves your machine.
Use cases of Smart Workspace Manager
- Search and retrieve work documents from an AI assistant.
- Summarize meeting notes or project plans using an LLM.
- Create and organize files within a designated workspace directory.
- Read and analyze project files without switching applications.
FAQ from Smart Workspace Manager
What are the prerequisites for Smart Workspace Manager?
macOS (Silicon/ARM64), Python 3.10+, and an MCP‑compatible client (e.g., Claude Desktop).
How do I configure the workspace path?
Create a .env file in the project root and set WORKSPACE_PATH, ALLOWED_FILE_TYPES, MAX_FILE_SIZE_MB, and ENABLE_DESTRUCTIVE_TOOLS.
What file types are supported?
The default allowed file types are .txt, .md, and .pdf, configurable via the .env file.
Is Smart Workspace Manager secure?
Yes. By default it runs in read‑only mode; destructive tools (delete, move) are gated behind a secure configuration flag (ENABLE_DESTRUCTIVE_TOOLS).
Can I use Smart Workspace Manager with any MCP client?
Yes, it connects to any MCP‑enabled client without custom integration, using standard I/O transport.
