日常小助手 MCP Server
v2.1.0AI-powered daily task management MCP Server — recommend next task, inherit uncompleted todos, detect overdue, generate reviews. Deterministic ops in code (ze...
⭐ 0· 100·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (daily task MCP server) matches the actual code and instructions: Python-based deterministic task parsing, tools to read/write daily Markdown files, recommendations, overdue checks, and integration with MCP-compatible editors. Requiring python3 and creating a venv + installing fastmcp is proportional to this purpose. The only notable capability beyond bare file ops is that the setup will modify editor configuration files (to register the MCP server) — this is explainable by the goal of integrating with editors.
Instruction Scope
SKILL.md tells the user to git clone and run src/setup.py --auto. setup.py will create a .venv, pip-install fastmcp, create a data directory (~/Desktop/日常小助手/Daily), generate config.json, and auto-merge an entry into various editor MCP config files (e.g. ~/.claude.json, ~/.cursor/mcp.json, ~.kiro/settings/mcp.json, etc.). These actions go beyond merely reading/writing task files because they modify editor config files in the user's home directory; this is consistent with registering an MCP server but worth explicit user consent.
Install Mechanism
No registry install spec is provided, but the package's setup.py will create a virtualenv and run pip install fastmcp (download from PyPI). The SKILL.md also instructs a git clone from the project's GitHub. Both git clone (GitHub) and pip install from PyPI are typical but require network access and trust in upstream sources. There is no download from obscure URLs or archive extraction from untrusted hosts.
Credentials
The skill does not request environment variables or credentials. However, setup.py reads and writes editor config files under the user's home (which may contain API keys/tokens for those editors). The script attempts a safe JSON merge (preserving existing content) but writing into files that can contain secrets is a sensitive action — the change is explainable by the integration goal but should be done with caution and backups.
Persistence & Privilege
always:false (no forced global installation). The setup will register the server persistently in detected editor MCP config files, making the server available to editors in the future. That persistent registration is a normal part of integrating an MCP server, but it does grant ongoing presence in editor configs and should be done only with user consent. The skill does not request elevated OS privileges.
Assessment
What to consider before installing:
- This repo will create a .venv and run pip install fastmcp (network access to PyPI). If you prefer, inspect setup.py and run the venv/pip steps manually.
- setup.py will create a data folder (default: ~/Desktop/日常小助手/Daily) and write Dashboard.md and config.json. If you want a different location, run setup interactively instead of --auto.
- setup.py auto-merges an entry into various editor MCP config files (e.g., ~/.claude.json, ~/.cursor/mcp.json, ~/.kiro/..., ~/.codeium/...). Those files may already contain API keys or other settings; the script attempts a safe merge but you should back up those config files before running --auto.
- The SKILL.md suggests git cloning the repo from GitHub; the registry already contains the code — cloning fetches the upstream repo (possible update). If you want zero-network install, skip the git clone and run setup.py from the bundled files after reviewing them.
- I reviewed the visible parts of core.py, server.py and setup.py; the logic is consistent with the stated purpose (file parsing, ranking, writing daily files, and adding MCP config). core.py was truncated in the provided bundle, so if you need higher assurance, inspect the full core.py for any unexpected network calls or obfuscated behavior.
- Recommended actions: (1) review setup.py and server.py locally before running, (2) back up editor config files you care about, (3) run setup in interactive mode (no --auto) to see prompts and paths, or run inside an isolated account/VM if you want stronger containment.Like a lobster shell, security has layers — review code before you run it.
latestvk9705zycae478trmf9kz6ek9p983yexy
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📅 Clawdis
Binspython3
