You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "guilleov (via GitHub)" <gi...@apache.org> on 2026/07/13 15:19:00 UTC
[D] MCP update_dashboard tool cannot set dashboard owners [superset]
GitHub user guilleov created a discussion: MCP update_dashboard tool cannot set dashboard owners
### Summary
The MCP `update_dashboard` tool can edit a dashboard's title, description, slug, `published` flag, tags, CSS, layout and `json_metadata`, but it has **no way to set the dashboard's owners**, and no other MCP tool sets owners either.
### Why this matters
A dashboard created through the MCP (`generate_dashboard`) is owned only by the MCP agent's user. Since an unpublished dashboard is visible only to its owners, the human who drove the agent cannot see or manage their own newly created dashboard, and no MCP client can transfer ownership to them. Today the only workarounds are the Superset UI or direct metadata-DB access.
### Proposed change
Add an optional `owners` field (full-replacement list of user IDs) to the existing `update_dashboard` tool, mirroring the REST dashboard owners semantics:
- unknown user IDs are rejected up front with a clear `OwnersNotFound` error,
- an empty list clears owners,
- omitting the field leaves owners unchanged.
Editorship remains enforced via `raise_for_editorship`, so only current owners or an Admin can change owners (same guarantee as the REST PUT).
### Additional context
Small, self-contained enhancement to an existing tool (not a new tool / not SIP-scope). PR to follow and will link back here.
GitHub link: https://github.com/apache/superset/discussions/42001
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] MCP update_dashboard tool cannot set dashboard editors [superset]
Posted by "guilleov (via GitHub)" <gi...@apache.org>.
GitHub user guilleov closed a discussion: MCP update_dashboard tool cannot set dashboard editors
### Summary
The MCP `update_dashboard` tool can edit a dashboard's title, description, slug, `published` flag, tags, CSS, layout and `json_metadata`, but it has no way to set who may edit the dashboard (its `editors`), and no other MCP tool sets them either.
### Why this matters
A dashboard created through the MCP (`generate_dashboard`) has only its creating agent as an editor. Since an unpublished dashboard is visible only to its editors, the human who drove the agent cannot see or manage their own newly created dashboard, and no MCP client can grant them access. Today the only workarounds are the Superset UI or direct metadata-DB access.
### Proposed change
Add an optional `editors` field (full-replacement list of user IDs) to the existing `update_dashboard` tool. User IDs are mapped to their USER `Subject` rows and run through the same `compute_subject_list(..., ensure_no_lockout=True)` helper the REST update command uses, then assigned to the dashboard's `editors` relationship:
- unknown user IDs are rejected up front with an `EditorsNotFound` error,
- an empty list clears editors, except a non-admin caller who currently edits the dashboard is retained (no-lockout guard),
- omitting the field leaves editors unchanged.
### Additional context
Small, self-contained enhancement to an existing tool (not a new tool / not SIP-scope). PR: apache/superset#42002.
GitHub link: https://github.com/apache/superset/discussions/42001
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] MCP update_dashboard tool cannot set dashboard editors [superset]
Posted by "guilleov (via GitHub)" <gi...@apache.org>.
GitHub user guilleov edited a discussion: MCP update_dashboard tool cannot set dashboard editors
### Summary
The MCP `update_dashboard` tool can edit a dashboard's title, description, slug, `published` flag, tags, CSS, layout and `json_metadata`, but it has no way to set who may edit the dashboard (its `editors`), and no other MCP tool sets them either.
### Why this matters
A dashboard created through the MCP (`generate_dashboard`) has only its creating agent as an editor. Since an unpublished dashboard is visible only to its editors, the human who drove the agent cannot see or manage their own newly created dashboard, and no MCP client can grant them access. Today the only workarounds are the Superset UI or direct metadata-DB access.
### Proposed change
Add an optional `editors` field (full-replacement list of user IDs) to the existing `update_dashboard` tool. User IDs are mapped to their USER `Subject` rows and run through the same `compute_subject_list(..., ensure_no_lockout=True)` helper the REST update command uses, then assigned to the dashboard's `editors` relationship:
- unknown user IDs are rejected up front with an `EditorsNotFound` error,
- an empty list clears editors, except a non-admin caller who currently edits the dashboard is retained (no-lockout guard),
- omitting the field leaves editors unchanged.
### Additional context
Small, self-contained enhancement to an existing tool (not a new tool / not SIP-scope). PR: apache/superset#42002.
GitHub link: https://github.com/apache/superset/discussions/42001
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] MCP update_dashboard tool cannot set dashboard owners [superset]
Posted by "guilleov (via GitHub)" <gi...@apache.org>.
GitHub user guilleov added a comment to the discussion: MCP update_dashboard tool cannot set dashboard owners
PR opened: https://github.com/apache/superset/pull/42002 (adds an `owners` field to the `update_dashboard` MCP tool as proposed above).
GitHub link: https://github.com/apache/superset/discussions/42001#discussioncomment-17624180
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] MCP update_dashboard tool cannot set dashboard editors [superset]
Posted by "guilleov (via GitHub)" <gi...@apache.org>.
GitHub user guilleov edited a discussion: MCP update_dashboard tool cannot set dashboard editors
### Summary
The MCP `update_dashboard` tool can edit a dashboard's title, description, slug, `published` flag, tags, CSS, layout and `json_metadata`, but it has no way to set who may edit the dashboard (its `editors`), and no other MCP tool sets them either.
### Why this matters
A dashboard created through the MCP (`generate_dashboard`) has only its creating agent as an editor. Since an unpublished dashboard is visible only to its editors, the human who drove the agent cannot see or manage their own newly created dashboard, and no MCP client can grant them access. Today the only workarounds are the Superset UI or direct metadata-DB access.
### Proposed change
Add an optional `editors` field (full-replacement list of user IDs) to the existing `update_dashboard` tool. User IDs are mapped to their USER `Subject` rows and run through the same `compute_subject_list(..., ensure_no_lockout=True)` helper the REST update command uses, then assigned to the dashboard's `editors` relationship:
- unknown user IDs are rejected up front with an `EditorsNotFound` error,
- an empty list clears editors, except a non-admin caller who currently edits the dashboard is retained (no-lockout guard),
- omitting the field leaves editors unchanged.
### Additional context
Small, self-contained enhancement to an existing tool (not a new tool / not SIP-scope). PR: apache/superset#42002.
GitHub link: https://github.com/apache/superset/discussions/42001
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org