npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

notion-block-reader-mcp

v1.0.0

Published

A tiny, dependency-free, read-only Notion MCP server: extract every link URL in a page (including link_preview/embed/bookmark cards the official connectors hide), read raw blocks, and read page properties. No write tools.

Readme

notion-block-reader-mcp

A tiny, dependency-free, read-only Model Context Protocol server for Notion.

It surfaces what the official Notion connectors hide — the real target URLs of link_preview / embed / bookmark cards (the rich preview blocks you get when you paste a Discord/GitHub/Jira/etc. link), plus raw block reading and page properties. It only issues GET requests, so it can never create, edit, or delete anything in your workspace.

Why this exists

Notion's own MCP/markdown renderers return link-preview cards as opaque "external object" blocks without the URL (their spec marks them "not supported in the API yet"). But the Notion REST API does include the URL ({ "type": "link_preview", "link_preview": { "url": "…" } }). This server bridges that gap with a few focused, read-only tools.

Tools

| Tool | What it does | |------|--------------| | notion_extract_links | Every link URL under a page/block — including link_preview/embed/bookmark cards and inline links. Recurses nested blocks. | | notion_get_block_children | Direct child blocks of a page/block (compact: id, type, text, url). recursive: true to include nested. | | notion_get_block | One raw block by ID (full JSON, incl. link_preview.url). | | notion_get_page | A page's properties. |

Requirements

  • Node 18+ or bun (uses the runtime's global fetch; no install/build step).
  • A Notion internal integration token:
    1. Create one at https://www.notion.so/my-integrationsInternal → capability Read content.
    2. Copy the Internal Integration Secret (starts with ntn_…).
    3. Connect it to your data: open the page/database → Connections → add your integration (the token can only read pages it's been connected to).

Quick start (npx)

Add to your MCP client config (Claude Code / Cursor .mcp.json, Claude Desktop claude_desktop_config.json):

{
  "mcpServers": {
    "notion-block-reader": {
      "command": "npx",
      "args": ["-y", "notion-block-reader-mcp@latest"],
      "env": { "NOTION_TOKEN": "your_notion_integration_token" }
    }
  }
}

Restart the client, approve the server, and you're set.

Run directly

NOTION_TOKEN=your_token npx notion-block-reader-mcp
# or from a clone:
NOTION_TOKEN=your_token node index.mjs      # or: bun index.mjs

Token can also be passed as --config <token> instead of the env var.

Quick manual test

printf '%s\n' \
  '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{}}}' \
  '{"jsonrpc":"2.0","id":2,"method":"tools/list"}' \
| NOTION_TOKEN=your_token node index.mjs

How it works

MCP's stdio transport is newline-delimited JSON-RPC 2.0: the client launches this process and exchanges one JSON message per line over stdin/stdout. The server handles initialize, tools/list, and tools/call, mapping each tool to a Notion REST GET. All logging goes to stderr so stdout stays a clean protocol stream.

Security

  • Read-only: only GET requests. No create/update/delete, no comment writes.
  • The integration can only read pages/databases you've explicitly connected it to.
  • Keep your token in the client config's env, not in code. This repo contains no token.

License

MIT © Vorakorn Kosidphokin