mcpField
P
pageworkspace

pageworkspace

Local
github.com/CloudCorpRecordsProductivity0Updated 2w ago
Repository

About pageworkspace

pageworkspace is an MCP server for accessing Notion pages, databases, and blocks through the Notion REST API. It offers a core subset of tools with the same names and wire behavior as the referenced Notion MCP server, without its hosted OAuth surface.

Key features

  1. 01Search Notion content
  2. 02Read and update pages
  3. 03Create pages and databases
  4. 04Query databases
  5. 05Read and append block children
  6. 06Delete blocks

Use cases

  1. 01Search pages for a project roadmap
  2. 02Update a page through an MCP client
  3. 03Query a database and inspect its entries

MCP support

It exposes 12 tools for Notion pages, databases, and blocks to MCP clients. Calls use the Notion REST API and require an internal integration key.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cloudcorprecords-pageworkspace": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/pageworkspace"
      ]
    }
  }
}
Run commandnpx -y @reneturcios/pageworkspace

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/pageworkspace0.1.0
ocighcr.io/cloudcorprecords/pageworkspace:0.1.0

Tools

12

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
querystringNoOptional search text matched against page and database titles; when omitted, recent items are returned.
page_sizenumberNoOptional maximum number of results to return in one page.

Details

From the project 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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.