Back to Browse

Pageworkspace MCP Server

Developer ToolsModerate5.6MCP RegistryLocal
Free

Server data from the Official MCP Registry

Notion pages, databases and blocks via the REST API, as MCP tools.

About

Notion pages, databases and blocks via the REST API, as MCP tools.

Security Report

5.6
Moderate5.6Moderate Risk

pageworkspace is a clean, small Notion REST client. It reads NOTION_API_KEY from the environment, fails fast when it is missing, sends the key only as a Bearer header to the Notion API, and uses no shell, eval, or file access. The main points to note are that NOTION_API_URL can redirect the bearer token to any host, that several tools perform workspace writes and archiving, and that the npm scope, GitHub owner, and Docker org do not match, which the user should verify. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

NOTION_API_KEYRequired

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cloudcorprecords-pageworkspace": {
      "env": {
        "NOTION_API_KEY": "your-notion-api-key-here"
      },
      "args": [
        "-y",
        "@reneturcios/pageworkspace"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

pageworkspace

Notion pages, databases and blocks as MCP tools, talking to the Notion REST API. pageworkspace is a clean-room rebuild of the core surface of the Notion MCP server, under a new name: the same tool names and wire behaviour, fresh code, no copied branding. The original is a hosted remote MCP server; this rebuild is a REST-compatible client for the same upstream API — the hosted OAuth surface is not reproduced.

Tools (core subset, 12)

search, list_users, get_page, create_page, update_page, get_database, query_database, create_database, get_block, get_block_children, append_block_children, delete_block.

Not in this subset: page property-item endpoints, comments, file uploads, data sources (2025 API), synced blocks and template admin, search-by-data-source hosted tools, and the OAuth public-integration flow.

Setup

Create an internal integration in Notion, share the target pages and databases with it, and set its secret:

export NOTION_API_KEY=secret_...

Optionally override the API base with NOTION_API_URL (default https://api.notion.com/v1). Without the key, every tool call fails with an error naming the missing variable.

CLI

npx @reneturcios/pageworkspace search '{"query":"roadmap"}'
npx @reneturcios/pageworkspace mcp        # stdio MCP server

Each tool name is a subcommand taking one JSON object argument.

MCP client config

{
  "mcpServers": {
    "pageworkspace": {
      "command": "npx",
      "args": ["-y", "@reneturcios/pageworkspace", "mcp"],
      "env": { "NOTION_API_KEY": "secret_..." }
    }
  }
}

Docker

docker run -i -e NOTION_API_KEY ghcr.io/cloudcorprecords/pageworkspace

Development

npm install
npm run build
npm test

License

MIT

Reviews

No reviews yet

Be the first to review this server!