Skip to main content
Glama
Sign In

Notion MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted Notion MCP server for Claude, ChatGPT and Cursor, with each action switched per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/notion-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.5/5.0

Scored across 4 tools

Disambiguation2/5

execute_action and query_data carry near-identical descriptions (both are 'Step 3 (FINAL)' of the same workflow, both require the same two query_contexts calls, and both are documented as read-only SELECT-only), so an agent cannot tell which to use for a given intent. prompts_menu and query_contexts are clearly distinct, but the core execution pair is effectively a coin flip.

Naming Consistency3/5

Three tools roughly follow verb_noun (execute_action, query_contexts, query_data), but prompts_menu breaks the pattern as a noun-first menu label. The reused 'query_' prefix on two semantically different tools (metadata contexts vs. actual Notion data) further muddies the convention.

Tool Count4/5

Four tools is a reasonable scaffolding for a meta-tool that funnels operations through a discovered action catalog plus a helper and prompt menu. It is slightly thin, since most capability is hidden behind one generic dispatcher, but nothing feels redundant in count terms.

Completeness3/5

Read-only scope is explicit and documented, so missing write/DDL operations is by design, and the dynamic available_actions catalog theoretically covers all reads. However, the surface offers no error-recovery, pagination, or schema-discovery tool outside the mandatory two-step preamble, and the execute_action/query_data split leaves execution responsibility ambiguous.

Available Tools

4 tools
execute_actionNotion Data Execute ActionA
Destructive
Inspect

Execute Notion action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, gcp_project_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

Notion is read-only here (OAuth scope notion.readonly): only SELECT queries succeed; DDL/DML/scripts are rejected by Google.

Inputs: body (required). Returns: object

prompts_menuNotion PromptsA
Read-only
Inspect

Access Notion prompt catalog with 4 operations:

  1. List Public Prompts: • request='menu' - No additional params needed • Returns: All public/system prompts available for Notion

  2. List Custom Prompts: • request='menu', prompt_type='custom', workspace_id= • Returns: All custom prompts for the specified workspace

  3. Get Public Prompt Details: • request='prompt_details', prompt_id= • Returns: Full text/details of a public prompt

  4. Get Custom Prompt Details: • request='prompt_details', prompt_id=, is_custom=True, workspace_id= • Returns: Full text/details of a custom prompt

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsNotion Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe Notion requests.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, gcp_project_id, other source metadata, AND available_actions (all read-only actions you can call).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_dataNotion DataA
Read-only
Inspect

Query Notion data (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id, gcp_project_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before querying.

Notion is read-only here (OAuth scope notion.readonly): only SELECT queries succeed; DDL/DML/scripts are rejected by Google.

Inputs: body (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources