Plan filtered data-source queries
Design a request to Notion’s data-source query API using the real schema, selected properties and cursor pagination.
Your connection path
NotionYour AI
Stacksync MCP OAuth
Your assistant builds a workflow for the app’s API. API access and configuration are required.
First request
“Design an overdue-task review”
Stacksync MCP · Custom API workflow
Notion MCP integration.
Prepare a custom Notion integration with Stacksync MCP using HTTP or code workflow steps. The reviewed Stacksync catalog does not list Notion, so page retrieval, data-source queries and updates require a verified API implementation rather than an assumed native connector.
01 / The connection
What Notion can do through MCP
Prepare a custom Notion integration with Stacksync MCP using HTTP or code workflow steps. The reviewed Stacksync catalog does not list Notion, so page retrieval, data-source queries and updates require a verified API implementation rather than an assumed native connector. Choose an AI client below to get started with the Stacksync MCP server.
This guide connects Notion through a custom Stacksync workflow. It does not provide a prebuilt Notion MCP server.
Explore the Notion connector →02 / Capabilities
Notion capabilities through MCP
Choose the connection path that fits the job. Your assistant inspects the available tools before configuring or running an action.
Prepare page creation
Propose a page-creation request with the correct parent and property types, after verifying the integration has access and insert capability.
Design approved property updates
Prepare an update for a specific page ID and property, with the original value and proposed value shown for review.
03 / Setup
Set up your AI client
Connect the MCP server first. Then configure a custom workflow for the Notion API using the requirements below.
Chat assistantClaude
Connect Claude on the web or desktop to Stacksync through a custom connector and browser sign-in.
Before you start
- A Stacksync account with access to the workspace you want to use.
- Permission to add an external MCP server in your AI client.
- On a Claude Team or Enterprise account, an owner must first add Stacksync under Organization settings → Connectors.
Add a custom connector
Open Customize → Connectors, select + Add, then Add custom connector. Name it Stacksync and use the server URL below.
https://mcp.stacksync.com/mcpConnect your Stacksync account
Select Connect, complete the Stacksync sign-in in your browser and choose the default workspace. Clear Make changes on the consent screen if you only want read access.
Check your workspace
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Check the connection
Ask “List my Stacksync workspaces.” Select the workspace you want to use.
Ask the assistant to check the live connector catalog first. This guide uses a custom HTTP or code workflow for Notion; configure API access and secure credentials outside chat before testing that workflow.
TerminalClaude Code
Add the remote Stacksync server to Claude Code and authenticate from its MCP menu.
Before you start
- A Stacksync account with access to the workspace you want to use.
- Permission to add an external MCP server in your AI client.
- Claude Code installed with the claude command available in your terminal.
Add Stacksync over HTTP
Run the command below. Add --scope user if you want the connection available across your projects.
claude mcp add --transport http stacksync https://mcp.stacksync.com/mcpFinish browser sign-in
Open Claude Code, run /mcp, select stacksync and complete the Stacksync sign-in. Choose the workspace you want requests to use by default.
Check your workspace
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Check the connection
Ask “List my Stacksync workspaces.” Select the workspace you want to use.
Ask the assistant to check the live connector catalog first. This guide uses a custom HTTP or code workflow for Notion; configure API access and secure credentials outside chat before testing that workflow.
Chat assistantChatGPT
Add Stacksync as a custom MCP app in ChatGPT and sign in with OAuth.
Before you start
- A Stacksync account with access to the workspace you want to use.
- Permission to add an external MCP server in your AI client.
- A ChatGPT account with Developer mode and custom MCP apps available. The Stacksync guide lists Plus, Pro, Business, Enterprise and Edu; workspace administrators can restrict access.
Enable custom app setup
Open Settings → Apps → Advanced settings and turn on Developer mode. If the option is unavailable, check the account or workspace policy with your administrator.
Create the Stacksync app
Select Create app, name it Stacksync, enter the server URL below and choose OAuth. Complete the Stacksync sign-in and select your default workspace.
https://mcp.stacksync.com/mcpEnable Stacksync in your chat
Select Stacksync from the chat tools menu so the conversation can use its tools. Signing in to ChatGPT itself does not sign you in to Stacksync.
Check your workspace
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Check the connection
Ask “List my Stacksync workspaces.” Select the workspace you want to use.
Ask the assistant to check the live connector catalog first. This guide uses a custom HTTP or code workflow for Notion; configure API access and secure credentials outside chat before testing that workflow.
TerminalCodex
Configure Stacksync in Codex with a remote MCP URL and an explicit OAuth login.
Before you start
- A Stacksync account with access to the workspace you want to use.
- Permission to add an external MCP server in your AI client.
- Codex CLI installed with the codex command available.
Register the remote server
Add the Stacksync endpoint to your Codex MCP configuration.
codex mcp add stacksync --url https://mcp.stacksync.com/mcpSign in with OAuth
Run the login command and complete the Stacksync browser sign-in. Select a default workspace; restart your Codex session if the tools are not yet listed.
codex mcp login stacksyncCheck your workspace
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Check the connection
Ask “List my Stacksync workspaces.” Select the workspace you want to use.
Ask the assistant to check the live connector catalog first. This guide uses a custom HTTP or code workflow for Notion; configure API access and secure credentials outside chat before testing that workflow.
Code editorCursor
Use Stacksync from Cursor by adding a remote server to its MCP configuration.
Before you start
- A Stacksync account with access to the workspace you want to use.
- Permission to add an external MCP server in your AI client.
- Cursor installed with permission to configure MCP servers.
Add the server configuration
Merge this stacksync entry into the mcpServers object in ~/.cursor/mcp.json. Preserve any servers you already use.
{ "mcpServers": { "stacksync": { "url": "https://mcp.stacksync.com/mcp" } } }Connect from Cursor
Open Cursor’s MCP settings, select Connect beside stacksync and finish the Stacksync sign-in in your browser.
Check your workspace
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Check the connection
Ask “List my Stacksync workspaces.” Select the workspace you want to use.
Ask the assistant to check the live connector catalog first. This guide uses a custom HTTP or code workflow for Notion; configure API access and secure credentials outside chat before testing that workflow.
Code editorVS Code
Connect Stacksync to GitHub Copilot Chat in VS Code using an HTTP MCP server.
Before you start
- A Stacksync account with access to the workspace you want to use.
- Permission to add an external MCP server in your AI client.
- VS Code with Copilot Chat Agent mode available.
Add Stacksync to VS Code
Run the command below. Alternatively, add a stacksync entry with type http and this URL under servers in your project’s .vscode/mcp.json.
code --add-mcp '{"name":"stacksync","type":"http","url":"https://mcp.stacksync.com/mcp"}'Start it in Copilot Chat
Open Copilot Chat in Agent mode. Start stacksync from the tools picker and complete the Stacksync browser sign-in.
Check your workspace
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Check the connection
Ask “List my Stacksync workspaces.” Select the workspace you want to use.
Ask the assistant to check the live connector catalog first. This guide uses a custom HTTP or code workflow for Notion; configure API access and secure credentials outside chat before testing that workflow.
Code editorWindsurf
Add Stacksync to Cascade with Windsurf’s serverUrl configuration and OAuth sign-in.
Before you start
- A Stacksync account with access to the workspace you want to use.
- Permission to add an external MCP server in your AI client.
- Windsurf installed with Cascade and MCP configuration available.
Open the MCP configuration
In the Cascade panel, open the … menu and select Open MCP config file. Merge this entry into mcp_config.json without removing other servers.
{ "mcpServers": { "stacksync": { "serverUrl": "https://mcp.stacksync.com/mcp" } } }Authorize the first connection
Save the configuration. Cascade opens the Stacksync sign-in flow the first time it uses the server. Choose your default workspace.
Check your workspace
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Check the connection
Ask “List my Stacksync workspaces.” Select the workspace you want to use.
Ask the assistant to check the live connector catalog first. This guide uses a custom HTTP or code workflow for Notion; configure API access and secure credentials outside chat before testing that workflow.
TerminalGemini CLI
Connect the Gemini command-line client to Stacksync through remote HTTP MCP and browser authorization.
Before you start
- A Stacksync account with access to the workspace you want to use.
- Permission to add an external MCP server in your AI client.
- Gemini CLI installed with the gemini command available. These instructions apply to Gemini CLI, not the Gemini web app.
Register Stacksync
Run the following command in your terminal to add the HTTP server.
gemini mcp add --transport http stacksync https://mcp.stacksync.com/mcpAuthenticate inside Gemini CLI
Start Gemini CLI, run the command below and finish the Stacksync sign-in in your browser.
/mcp auth stacksyncCheck your workspace
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Check the connection
Ask “List my Stacksync workspaces.” Select the workspace you want to use.
Ask the assistant to check the live connector catalog first. This guide uses a custom HTTP or code workflow for Notion; configure API access and secure credentials outside chat before testing that workflow.
04 / Put it to work
Notion workflow prompts
Example prompts for Notion. The outcomes describe what to expect, not results from your account. Review the proposed configuration before running it.
01
Custom API workflow
Design an overdue-task review
Check the Stacksync catalog for Notion first. If the needed action is absent, propose a custom HTTP or code workflow that queries the Notion data source I choose. Inspect its property names before defining a due-date and status filter, include cursor pagination, and show the fields to return. Do not fetch private content, save or run the workflow until I review the request.
What to expect
A scoped custom task-query plan using actual Notion properties and access requirements.
02
Custom API workflow
Prepare a project-page workflow
Inspect the available Stacksync workflow steps and check for Notion modules. If a custom API step is required, propose creating a page in the Notion data source I specify. Verify the parent access and insert capability, map each property to the data-source schema and use a source project ID for duplicate detection. Show the complete proposed payload before saving or creating a page.
What to expect
A schema-aware custom page-creation proposal with an explicit parent and source identifier.
03
Custom API workflow
Propose a Notion status change
Check for a suitable Notion action; otherwise design a custom HTTP step for the page ID I provide. Verify access and update capability, inspect the current status property and prepare only the requested status change. Show the page, original value and proposed value. Do not write to Notion or deploy the workflow until I confirm.
What to expect
A single-page update proposal that identifies exactly what would change.
05 / Before you run
Requirements and limitations
What you need
- Connect your AI client to Stacksync MCP, sign in and select the workspace before inspecting its resources.
- A Notion connection or token with the minimum required content capabilities, and access to the intended pages or parent database.
- Store custom API authentication outside chat. Verify the current Notion API version and data-source schema before implementing HTTP or code steps.
What to account for
- No native Stacksync Notion connector is established by the reviewed public catalog. These are custom workflow patterns that require implementation and testing.
- Notion content access and read, insert or update capabilities are separate requirements. Sharing a link in chat does not grant API access.
- Use the current data-source API for modern Notion integrations; a page-property response is not the same as retrieving all of the page’s body content.
Your workspace. Your permissions.
OAuth access follows your Stacksync role. Choose read-only access during sign-in when appropriate. Workspace owners can enable “Ask before every change”; it is a configurable setting. Direct connector actions also follow gateway policies.
Read about permissions and approvals ↗If setup does not work
- The MCP server does not appear
- Check your client’s custom MCP settings and any plan or administrator prerequisites. Reconnect using the setup instructions above.
- Your workspace or app is missing
- Verify the Stacksync account and workspace selected during OAuth, then check the live catalog. For this custom workflow, configure HTTP or code steps and provide the required API credentials through approved secret storage outside chat.
- An action is unavailable or denied
- Check the workflow configuration, API version, required inputs and app token permissions. Confirm that your Stacksync role and OAuth consent allow the proposed workflow changes.
06 / Common questions
Notion MCP questions
Is a native Notion MCP connector included here?
No native Stacksync Notion connector is verified in the reviewed catalog. The documented route is a custom Stacksync workflow using Notion’s API, unless live module discovery finds a supported action.
Why do I need to share the Notion database with the integration?
Notion enforces resource access as well as content capabilities. The integration must have access to the parent database for a data-source query, and the appropriate capability for reads, inserts or updates.
Can the assistant read a complete Notion page using its properties endpoint?
Page properties and page content are different. Select the appropriate content endpoint when body text is needed; do not treat a property-only response as the full document.
Reviewed · Product documentation and connector references
Keep building
