notion-bloom
Related Servers
Alternatives to notion-bloom
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenancePlan-bank MCP for AI agents and Notion. Agents read and write Markdown implementation plans with line + section addressing — no ad-hoc temp scripts.127 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to generate teaching materials such as PPTs, handouts, lecture scripts, mind maps, teaching video storyboards, and Manim math animations, plus run quality checks and language normalization through 15 MCP tools.MIT
- AlicenseNot gradedqualityAmaintenanceGives AI agents headless, token-authenticated read/write access to a Notion workspace through MCP, using three context-efficient tools that cover 47 operations across pages, databases, blocks, templates, comments, users, and files. Supports creating and editing pages, querying and filtering databases, batch mutations with rollback and idempotency, markdown round-trips, and image/file uploads, runnable over stdio or HTTP in CI and self-hosted deployments.4,610 npmMIT
- AlicenseNot gradedqualityAmaintenanceGives MCP clients like Claude, Cursor and Codex read/write access to Notion through a single token, letting agents search, create and edit pages, query databases, comment and upload files in plain language. It uses only three lightweight tools, supports batched idempotent writes, and runs headless in CI or self-hosted environments.4,610 npmMIT
- AlicenseNot gradedqualityDmaintenanceTranscribes audio/video files, generates summaries and structured knowledge items, and supports Notion integration and chat-based interaction. Works as a standalone CLI, Notion integration, or MCP server tool for agent ecosystems.7 npmMIT
- AlicenseAqualityDmaintenanceEnables AI agents to generate real Office documents (.pptx, .docx, .xlsx) and source code from natural language via MCP protocol.4MIT
TDQS
Scored across 17 tools
Most tools target distinct pipeline stages, but draft_lecture and run_lecture_pipeline both return a structure skeleton, and run_lecture_pipeline overlaps with apply_plan on writing/beautifying. The audit and preview tools are separable by dimension, but agents must read long descriptions to choose correctly.
All names use snake_case and mostly follow a verb_noun pattern. Minor deviations like handoff_status, rollback, and diff_after_beautify keep it from being perfectly uniform.
17 tools is borderline heavy for a single lecture-to-Notion pipeline. Several audit and preview variants could be consolidated, though each has a plausible role.
The surface covers ingest, drafting, content review, apply, audits, diff, rollback, and rendering, which is strong lifecycle coverage. Explicit page creation/deletion and comment handling are missing, but core workflows are workable.