Skip to content

[Refactor] Centralize native MCP authentication policy - #1433

Draft
roomote-roomote[bot] wants to merge 1 commit into
developfrom
feature/centralize-native-mcp-auth-2upoyb022aqh3
Draft

[Refactor] Centralize native MCP authentication policy#1433
roomote-roomote[bot] wants to merge 1 commit into
developfrom
feature/centralize-native-mcp-auth-2upoyb022aqh3

Conversation

@roomote-roomote

Copy link
Copy Markdown
Contributor

​Created by Roomote. View the task or mention @roomote-roomote for follow-up asks.

What changed

  • Added one shared authorization resolver for deployment-scoped native MCP handlers.
  • Routed Asana, Grafana, Granola, Notion, Snowflake, and Vercel through the shared missing-auth, run-token, and user-auth policy while leaving provider credential resolution unchanged.
  • Replaced repeated authorization contract cases with one parameterized suite covering all six providers, while retaining focused provider behavior and credential tests.

Why this change was made

The same authorization invariant had six independent implementations and synchronized test copies. Centralizing it gives the policy one owner and reduces the risk that a future provider change drifts from the others.

Impact

There is no intended user-facing behavior change. Existing public authorization errors and provider-specific credential lookup remain unchanged, while the native MCP authorization policy is easier to maintain consistently.

@roomote-community

roomote-community Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

No code issues found. See task

Reviewed 3cab27c

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.

1 participant