Can I use Notion as a CLI?

Yes. KosmoKrator exposes a Notion CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Notion through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Notion tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Notion credentials stored?

Notion credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Notion MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Notion MCP Integration for LangChain

Connect Notion to LangChain through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

7 functions 6 read 1 write Bearer token auth

Submit Notion feedback View package source

Connect Notion to LangChain

Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls.

Use the MCP gateway when the agent should discover tools, or wrap kosmo integrations:call for fixed chains. The gateway is local, scoped to this integration, and starts with --write=deny so LangChain can inspect read-capable tools without receiving write access by default.

Notion MCP Config for LangChain

Keep the gateway scoped to the integration and operation class needed by the chain.

{
  "mcpServers": {
    "kosmokrator-notion2": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=notion2",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=notion2 --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Notion instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Notion Tools Visible to LangChain

LangChain sees stable MCP tool names generated from the Notion integration catalog.

MCP tool	Source function	Type	Description
`integration__notion2__notion2_list_pages`	`notion2.notion2_list_pages`	Read	Search and list pages in your Notion workspace.
`integration__notion2__notion2_get_page`	`notion2.notion2_get_page`	Read	Get detailed information about a Notion page.
`integration__notion2__notion2_create_page`	`notion2.notion2_create_page`	Write	Create a new page in Notion.
`integration__notion2__notion2_list_databases`	`notion2.notion2_list_databases`	Read	List databases in your Notion workspace.
`integration__notion2__notion2_query_database`	`notion2.notion2_query_database`	Read	Query a Notion database with optional filters.
`integration__notion2__notion2_list_users`	`notion2.notion2_list_users`	Read	List all users in your Notion workspace.
`integration__notion2__notion2_get_current_user`	`notion2.notion2_get_current_user`	Read	Get the currently authenticated Notion user/bot.

Related Notion Pages

Notion CLIUse direct JSON commands instead of MCP discovery. Notion MCPFull gateway reference and MCP tool names. KosmoKrator for LangChainClient-level gateway setup.