Borrowing it
Nothing to install: this file belongs to Grey-Iris/easy-notion-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Grey-Iris/easy-notion-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/Grey-Iris/easy-notion-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/grey-iris/easy-notion-mcp/claude-md)<a href="https://agentmods.dev/instructions/grey-iris/easy-notion-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/grey-iris/easy-notion-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.04152 | $0.04152 |
| Opus 5 | $0.02076 | $0.02076 |
| Sonnet 5 | $0.00830 | $0.00830 |
| Haiku 4.5 | $0.00415 | $0.00415 |
Grade A, and why
easy-notion-mcp CLAUDE.md scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
6. Verify npm picked up the new version: `curl -s https://registry.npmjs.org/easy-notion-mcp/latest | jq -r .version` (avoid `npm view`, which can return stale local-cached data for several minutes). How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
easy-notion-mcp
Markdown-first Notion MCP server. Agents write markdown, the server converts it to Notion's block API. Agents never touch Notion block objects directly.
Open source context
This is open source software (MIT-licensed, published to npm as easy-notion-mcp and on GitHub as Grey-Iris/easy-notion-mcp). Commits, PR bodies, issue responses, and diffs become part of the public record — they are cited back at the project, not just read. That should shape how you work on this repo:
- Security claims are load-bearing. If CI allowlists a CVE as "not exploitable" or a commit claims "we don't use the vulnerable code path," that claim needs to be grounded in actual file:line evidence from the code paths involved, not in reasoning from what we import. When in doubt, patch rather than whitelist — users install this server and hand it their Notion workspace token, so "theoretically safe" is not the bar.
- Upstream-first for transitive fixes. If a root cause lives in a dependency (e.g.
@modelcontextprotocol/sdkpulling a vulnerablehono), file an issue or PR upstream alongside any local patch. Local overrides are a short-term workaround; upstream fixes help the whole ecosystem and reduce our long-term exception list. - Downstream consumers exist. People install via
npx easy-notion-mcp, wrap us in other MCP clients, or depend on us as a library. Consider how changes topackage.json,exports,bin, default behavior, and tool schemas affect them — not just our own CI. - PR scope discipline. Keep PRs narrowly scoped so reviewers and future auditors can tell what changed and why. Don't bundle unrelated fixes into a docs PR, don't let chores leak into feature branches. Semantic titles, focused diffs.
- Honest positioning. Avoid marketing superlatives in README/docs. Soften unverifiable comparisons, cite real numbers, and match the existing measured tone.
.meta/ publication policy (hybrid, 2026-07-02)
Two classes of .meta/ content, two defaults:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 184 lines · 4,152 tokens per session scan A 3fc9ce516ac4
easy-notion-mcp CLAUDE.md is an instructions file published in the GitHub repository Grey-Iris/easy-notion-mcp (51 stars, last pushed 6d ago), licensed MIT. It adds 4,152 tokens to every session, about $0.0208 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
md-feedback copilot-instructions.md
Copilot instructions for yeominux/md-feedback, covering plan review workflow, before implementing any plan, annotation types and mcp setup.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.