Notion Mcp V2 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Notion Mcp V2 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
An MCP server that turns your Notion task list into an AI-optimized daily schedule.
Every night you pull tomorrow's tasks from your "Upcoming Tasks" database and manually slot them into half-hour blocks. This agent does that for you — it reads your tasks (including page body content like workout plans and watchlists), understands priorities via the Eisenhower matrix, respects fixed-time commitments parsed from task names, and writes a clean schedule back to Notion.
Upcoming Tasks database
Task detail with body content
CLI schedule generation
Schedule written to Notion
MCP server code
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ Upcoming Tasks │──────▶│ AI Scheduler │──────▶│ Schedule Today │
│ (Notion DB) │ │ (OpenAI) │ │ (Notion Table) │
│ │ │ │ │ │
│ • Task name │ │ • Reads page │ │ 6:00 Free time │
│ • Priority │ │ body content │ │ 9:00 LeetCode │
│ • Weekday │ │ • Parses times │ │ 9:30 Standup │
│ • Page content │ │ • Sorts by │ │ 10:00 Deep work │
│ │ │ priority │ │ ... │
└──────────────────┘ └──────────────────┘ └──────────────────┘| Status | Meaning | Scheduling |
|---|---|---|
Imp Urg | Important & Urgent | Peak focus hours first |
Urg ~Imp | Urgent, not important | Soon, lighter slots |
Imp ~Urg | Important, not urgent | Focused time available |
In Progress | Currently being worked on | Dedicated blocks |
~Imp ~Urg | Neither important nor urgent | Fill remaining gaps |
Pinned | Recurring/daily tasks | Spread across the day |
plan_day, get_tasks, and apply_schedulepip install -r requirements.txtNOTION_API_KEYhttps://notion.so/workspace/YOUR_DB_ID?v=... Copy the 32-character hex ID.
cp .env.example .envEdit .env with your keys:
NOTION_API_KEY=ntn_your_key_here
OPENAI_API_KEY=sk-your_key_here
NOTION_TASKS_DB_ID=your_database_id
NOTION_SCHEDULE_PAGE_ID=your_page_id# List tomorrow's tasks
python -m src.cli tasks tomorrow
# Generate and apply a schedule for tomorrow
python -m src.cli plan tomorrow
# Plan a specific day
python -m src.cli plan mondayThe plan command shows a preview and asks for confirmation before writing to Notion.
Run the server for use with Claude Desktop, Cursor, or any MCP client:
python -m src.mcp_server#### Claude Desktop configuration
Add to your claude_desktop_config.json:
{
"mcpServers": {
"notion-schedule-agent": {
"command": "python",
"args": ["-m", "src.mcp_server"],
"cwd": "/path/to/notion-mcp-v2",
"env": {
"NOTION_API_KEY": "ntn_...",
"OPENAI_API_KEY": "sk-...",
"NOTION_TASKS_DB_ID": "...",
"NOTION_SCHEDULE_PAGE_ID": "..."
}
}
}
}#### Available MCP Tools
| Tool | Description |
|---|---|
get_tasks(day) | List tasks for a given day from Notion |
plan_day(day) | Generate an AI-optimized schedule (preview) |
apply_schedule() | Write the previewed schedule to Notion |
day accepts "today", "tomorrow", or a weekday name like "Monday".
notion-client — reads task database + page content, writes schedule tablegpt-4o-mini) — intelligent scheduling with priority awarenessmcp SDK — exposes tools to any MCP clientsrc/
config.py — environment config, time slots, priority mapping
notion_ops.py — Notion API operations (read tasks + page content, write schedule)
scheduler.py — OpenAI-powered schedule generation
mcp_server.py — MCP server entry point with tool definitions
cli.py — standalone CLI for direct usageMIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.