Features

Your knowledge,
programmable.

A Notion-style REST API and a ten-tool MCP server turn your workspace into infrastructure: agents search it, pipelines write to it, and scoped keys keep every caller in its lane.

The API

If you know Notion's API,
you already know ours.

NoteX exposes a Notion-style REST API on purpose: pages and blocks as resources, rich text with the annotations you expect, cursor pagination, and familiar error objects. List and create pages, read and append blocks, update, trash, and search, with the conventions half the automation world already speaks.

That familiarity is a migration feature too: integrations built for Notion have a recognizable twin shape on NoteX.

🔑

Search, from anywhere

The REST API in one request
bash
curl -X POST \
  -H "Authorization: Bearer nx_live_…" \
  -H "Content-Type: application/json" \
  -d '{"query": "deploy runbook"}' \
  https://<your-workspace>/functions/v1/notex-api/v1/search

Pages, blocks, rich text with annotations, and cursor pagination, shaped the way Notion's API shaped them. Your muscle memory transfers.

Keys with manners

Scoped keys,
audited requests.

API keys (prefixed nx_) are created in the app, shown once, and stored hashed. Each key is read-only or read/write, optionally limited to chosen pages and their sub-pages, and optionally expiring. Every request is logged with method, path, status, and latency, so key activity is auditable, not mysterious.

The practical patterns follow naturally: a read-only key for the research agent, a page-scoped key for the support bot that only needs the help center, an expiring key for the contractor's integration.

Permissions
2 levels
read-only or read/write
Scope
Optional
chosen pages + their sub-pages
Expiry
Optional
never, or N days
Logging
Every call
method, path, status, latency

Keys are managed in the app: create, scope, watch last-used, revoke.

MCP

Ten tools that make your notes
part of every agent's world.

The NoteX MCP server speaks the Model Context Protocol, the open standard AI assistants use to reach tools. Wire it into Claude Desktop, Claude Code, Cursor, or any MCP client and the agent gets ten tools over your workspace: search_pages, list_pages, get_page, get_page_content, create_page, update_page, append_blocks, update_block, delete_block, and trash_page.

It runs on your machine and talks only to the public API with your key, so the permissions story stays exactly as scoped as the key you gave it. Read-only key, read-only agent.

🤖

Claude, meet the wiki

MCP client configuration
json
{
  "mcpServers": {
    "notex": {
      "command": "node",
      "args": ["notex-mcp-server/index.mjs"],
      "env": {
        "NOTEX_API_URL": "https://…/notex-api/v1",
        "NOTEX_API_KEY": "nx_live_…"
      }
    }
  }
}

One config block and Claude Desktop, Claude Code, or Cursor can search, read, and write your workspace.

The endpoint map

EndpointWhat it does
POST /v1/searchFull-text search across the workspaceRead
GET · POST /v1/pagesList and create pagesR/W
GET · PATCH · DELETE /v1/pages/:idRead, update, trash a pageR/W
GET /v1/blocks/:id/childrenRead a page's blocksRead
PATCH /v1/blocks/:id/childrenAppend blocks (with position)Write
PATCH · DELETE /v1/blocks/:idUpdate or delete a blockWrite

Notion-style cursor pagination throughout, and errors shaped like the ones your integration already handles. Full reference documentation ships with the workspace.

Frequently asked questions

How close is the API to Notion's?

Deliberately close: pages and blocks as resources, rich-text annotations, cursor pagination, and similar error objects. Where the data models differ, NoteX documents the deviation instead of hiding it.

How do I create an API key?

In the workspace's API Access settings: name it, choose read-only or read/write, optionally scope it to specific pages and set an expiry. The key is shown once and stored hashed.

What can a page-scoped key see?

Only the pages you selected and everything nested under them. Requests outside the scope return a restricted-resource error, and everything is logged.

Which MCP clients work?

Any client that speaks the Model Context Protocol: Claude Desktop, Claude Code, Cursor, and the growing ecosystem. The server is a small Node process configured with your API URL and key.

Can agents delete things?

Only with a read/write key, and page deletion is a soft trash (restorable), not a hard delete. Give agents read-only keys unless writing is the point.

What do things like CI pipelines use this for?

Common patterns: CI writing release notes into the wiki, a research agent reading specs, dashboards pulling structured content, and bots filing meeting summaries. The AI teams page shows full setups.

Your notes deserve a better engine.

A Notion-style block editor on the engine behind the world's most popular code editor. Notes stay files you own, extensions add what you need, and AI plugs in natively. Free to start, on web and desktop.

Get NoteX free Book a demo

Free to start · Your files, your disk · Windows desktop & web