Skip to content

Proposal: Add an option to disable the authentication header#105

Merged
ksinder merged 2 commits into
makenotion:mainfrom
rapportlabs:master
Jan 31, 2026
Merged

Proposal: Add an option to disable the authentication header#105
ksinder merged 2 commits into
makenotion:mainfrom
rapportlabs:master

Conversation

@piljaechae

Copy link
Copy Markdown
Contributor

Proposal: Add an option to disable the authentication header

We are running the Notion MCP server behind the agentgateway, which multiplexes multiple MCP servers.

Since all communication happens within the same network, adding an authentication header is unnecessary in our case. Configuring the auth header is also relatively complex.

This feature would be especially useful in local development environments, where security requirements are relaxed and ease of setup is a priority.

I propose introducing an option to disable the authentication header for setups where it is not required.

@DjinnS

DjinnS commented Aug 12, 2025

Copy link
Copy Markdown

Same use case here but with https://github.com/stacklok/toolhive who already handle the authentication via the same header. Currently, we can't use the MCP with Toolhive.

@ksinder ksinder merged commit f4a87aa into makenotion:main Jan 31, 2026
4 checks passed
jyoansah added a commit to drapesinc/notion-mcp that referenced this pull request Feb 2, 2026
Merged 63 commits from upstream bringing:
- feat: Add retrieve database endpoint to OpenAPI spec (makenotion#195)
- feat: Add option to disable authentication (makenotion#105)
- fix: preserve const values and allow any property in page schemas (makenotion#173)
- fix: handle double-serialized JSON parameters from MCP clients (makenotion#180)
- feat: Add tool annotations for improved LLM tool understanding (makenotion#169)
- feat: add streamable HTTP transport and NOTION_TOKEN env var support (makenotion#75)

Preserved our customizations:
- Multi-workspace support with NOTION_TOKEN_* env vars
- Custom unified tools (notion-page, notion-blocks, etc.)
- get-due-tasks with assignee filtering and dual date property checking
- Toolset configuration and filtering

Merged deserializeParams fix into our multi-workspace flow.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants