Notion Workflow Orchestrator

A Model Context Protocol (MCP) server engineered for seamless connectivity with Notion estates, empowering models like Claude to execute advanced document management tasks.

Core Functionalities

• Workspace Indexing: Perform comprehensive searches across all accessible Notion content.
• Page Content Retrieval: Fetch the full content structure from a designated Notion page.
• Page Provisioning: Instantiate entirely new pages within the workspace.
• Page Revision: Apply modifications to extant page content or alter page titles.
• Database Generation: Establish novel databases complete with predefined property schemas.
• Database Interrogation: Execute complex queries against databases, incorporating filtering and sorting directives.
• Entry Property Modification: Revise specific attributes within existing database records.
• New Record Insertion: Append fresh entries (rows) to established databases, specifying initial property values.

Deployment Guide

1. Source Code Acquisition

2. Dependency Installation bash npm install

3. Notion Credentials Configuration

4. Secure an integration token via the Notion Developer Portal.
5. Capture the generated secret key.

6. Deployment options:

   • Modify the .env file, substituting the placeholder with your actual key, or
   • Embed the key directly into the Claude for Desktop configuration (this method is preferred).

7. Compilation Phase bash npm run build

8. Server Launch bash npm start

Integration with Claude for Desktop

1. Ensure Claude for Desktop is installed.
2. Access the configuration file for Claude for Desktop:
3. macOS Path: ~/Library/Application Support/Claude/claude_desktop_config.json

4. If the file is absent, create it.

5. Incorporate this Notion connector definition into your configuration:

{ "mcpServers": { "notion": { "command": "node", "args": [ "/Users/shaheerahmad/Documents/notion-mcp-server/dist/index.js", "--notion-api-key=YOUR_ACTUAL_API_KEY_HERE" ] } } }

Note: Substitute the placeholder path with your installation directory and YOUR_ACTUAL_API_KEY_HERE with your Notion secret.

1. Reinitialize the Claude for Desktop application.

Operational Usage

Once the connection is established via Claude for Desktop, interact with the system by issuing natural language directives, such as:

• "Scan my Notion space for documents related to Q3 financial reviews"
• "Retrieve the complete contents of the 'Product Roadmap' page"
• "Draft a new page detailing upcoming sprints"
• "Revise the content of Notion item (ID: 1aaada269d1b8003adceda69cf7bcd97) to include 'Key findings from the latest audit'"
• "Establish a fresh data repository within the page identified by 1aaada269d1b8003adceda69cf7bcd97"
• "Fetch all records from the database (ID: 1aaada269d1b8003adceda69cf7bcd97) where the 'Lifecycle' field equals 'Archived'"

Claude intelligently maps these instructions to the requisite underlying tools.

Tool Invocation Examples

Search Operations

Execute a search for "project debriefs" throughout my Notion repository

Content Fetching

Fetch the structural composition of page ID 1aaada269d1b8003adceda69cf7bcd97

New Page Creation

Construct a fresh Notion document titled "Executive Summary for Q4" containing the text "Performance exceeded targets by 15%..."

Page Modification

Update the document ID 1aaada269d1b8003adceda69cf7bcd97 by appending the text "Final review complete."

Alternatively, updating metadata:

Modify the title of Notion page 1aaada269d1b8003adceda69cf7bcd97 to "Revised Q4 Briefing" and inject supplemental details.

Database Initialization

Instantiate a new data table on parent page 1aaada269d1b8003adceda69cf7bcd97 named "Resource Allocator" with the following schema definitions: { "Resource Name": { "title": {} }, "Allocation Status": { "select": { "options": [ { "name": "Pending", "color": "orange" }, { "name": "Assigned", "color": "green" } ] } }, "Target Date": { "date": {} } }

Database Data Retrieval

Interrogate the database ID 1aaada269d1b8003adceda69cf7bcd97 for entries where the property 'Allocation Status' is precisely 'Assigned'

Sorting directive example:

Query the Notion database 1aaada269d1b8003adceda69cf7bcd97, ordered by the 'Target Date' field in ascending sequence

Database Record Update

Modifying attributes of an extant record within a database structure.

{ "tool_name": "update-database-entry", "tool_params": { "pageId": "page_id_of_database_entry", "properties": { "Allocation Status": { "select": { "name": "Assigned" } }, "Target Date": { "date": { "start": "2024-01-15" } } } } }

Ensure the structure of properties adheres strictly to the Notion API specifications for the respective property type (e.g., text, select, date).

Database Record Creation

Adding a new line item to an existing repository, defining its initial attribute values.

{ "tool_name": "create-database-row", "tool_params": { "databaseId": "your_database_id_here", "properties": { "Resource Name": { "title": [ { "text": { "content": "Server Cluster Upgrade" } } ] }, "Allocation Status": { "select": { "name": "Pending" } }, "Target Date": { "date": { "start": "2024-02-01" } } } } }

The properties object must contain definitions for all mandatory fields within the target database, formatted according to Notion's object model.

Troubleshooting

• If tool invocation fails, inspect the companion desktop application logs: bash tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

• Verify the Notion access token is correctly provisioned and that the associated integration has explicit permissions for the targeted content areas.

• Resolution for "Unexpected token" messages: This often stems from extraneous console.log() outputs interfering with the MCP communication stream. This implementation has been refined to mitigate such log pollution.

Roadmap for Enhancements

• Expansion of sophisticated database retrieval logic.
• Refinement and standardization of rendered content structure.
• Incorporation of support for a broader spectrum of Notion block entities.