Skip to content

fix: targeted personal MCP installs#4459

Draft
priyanshu0x wants to merge 1 commit into
archestra-ai:mainfrom
priyanshu0x:fix/mcp-server-target-user-installs
Draft

fix: targeted personal MCP installs#4459
priyanshu0x wants to merge 1 commit into
archestra-ai:mainfrom
priyanshu0x:fix/mcp-server-target-user-installs

Conversation

@priyanshu0x
Copy link
Copy Markdown
Contributor

@priyanshu0x priyanshu0x commented May 8, 2026

Summary

  • Allow POST /api/mcp_server personal installs to target another organization member via userId when the caller has mcpServerInstallation:admin.
  • Keep same-user personal installs as the default when userId is omitted.
  • Use the effective personal owner for duplicate detection, MCP server ownership, user assignment, personal gateway tool assignment, and linked IdP token fallback.
  • Reject userId on non-personal installs and document the API behavior.

Root Cause

The install route accepted userId in the schema but overwrote both ownerId and userId with the authenticated request user. That made admin pre-provisioning for another user impossible and caused duplicate detection and tool assignment to resolve against the API key owner instead of the intended personal installation owner.

Fixes #4452

@joeyorlando joeyorlando changed the title Fix targeted personal MCP installs fix: targeted personal MCP installs May 8, 2026

- **Personal installations** are owned by one user and are useful when each person needs their own upstream account.
- **Team installations** are shared with a team and are useful for shared service accounts or team-owned integrations.
- **Organization installations** are shared across the organization and require MCP server installation admin permission.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

require MCP server installation admin permission.

I would document the explict <resource>:<action> permission here instead

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is similar behaviour allowed through the MCP tool as is now through the API endpoint handler?

@priyanshu0x
Copy link
Copy Markdown
Contributor Author

@joeyorlando I am reviewing it myself. I will mark it ready when done.

@priyanshu0x priyanshu0x force-pushed the fix/mcp-server-target-user-installs branch from 062eade to f6a1843 Compare May 8, 2026 13:49
@priyanshu0x priyanshu0x force-pushed the fix/mcp-server-target-user-installs branch from f6a1843 to d111689 Compare May 8, 2026 14:12
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.

MCP server install API ignores target user for personal installs

2 participants