Skip to content

feat: Allow using the MCP in read-only mode (KEEP-841)#1592

Merged
sanbotto merged 2 commits into
stagingfrom
feat/KEEP-841-read-only-mcp
Jun 22, 2026
Merged

feat: Allow using the MCP in read-only mode (KEEP-841)#1592
sanbotto merged 2 commits into
stagingfrom
feat/KEEP-841-read-only-mcp

Conversation

@sanbotto

Copy link
Copy Markdown

Opening now in order to test in a PR env.

@sanbotto sanbotto self-assigned this Jun 18, 2026
@sanbotto sanbotto changed the title feat: Allow using the MCP in read-only mode feat: Allow using the MCP in read-only mode (KEEP-841) Jun 18, 2026
@github-actions

Copy link
Copy Markdown

PR Environment Deployed

Your PR environment has been deployed!

Environment Details:

Components:

  • Keeperhub Application
  • PostgreSQL Database (isolated instance)
  • LocalStack (SQS emulation)
  • Redis (isolated instance)
  • Schedule Dispatcher (staging image)
  • Block Dispatcher (staging image)
  • Event Tracker (staging image)

The environment will be automatically cleaned up when this PR is closed or merged.

@sanbotto

Copy link
Copy Markdown
Author

Tested thoroughly. See screenshots for reference. Read-only works as expected, full access continues working as it currently does.

1-ui 2-result

I have a secondary proposed UI for the modal, just to better visually differentiate each button:
1-ui-alt

LMK which one is preferred.

@sanbotto sanbotto marked this pull request as ready for review June 18, 2026 21:26
@sanbotto sanbotto requested review from a team, OleksandrUA, eskp, joelorzet and suisuss and removed request for a team June 18, 2026 21:27
@joelorzet

joelorzet commented Jun 18, 2026

Copy link
Copy Markdown

Tested thoroughly. See screenshots for reference. Read-only works as expected, full access continues working as it currently does.

1-ui 2-result

I have a secondary proposed UI for the modal, just to better visually differentiate each button: 1-ui-alt

LMK which one is preferred.

👋 @sanbotto,

I would recommend the first option, as we don't have any green buttons in the UI.

Regarding the third button, Read-only, I would suggest using either a dropdown to select the desired scope or a set of checkboxes. All-Write could be the default option, with additional Write and Read-only scope checkboxes available for more granular control.

Besides that, scopes addition is a great feature for the MCP!

@sanbotto

Copy link
Copy Markdown
Author

Yeah, using checkboxes is a good option, leaving the original 2 buttons untouched. I'll try it out.

@sanbotto

Copy link
Copy Markdown
Author

Checkboxes looking good and working as expected. Selecting a scope gives you that scope; no more, no less. Tested locally. PR env will be ready in ~30m for anyone else to double check this. Video of the UI:

checkboxes.mp4

@github-actions

Copy link
Copy Markdown

PR Environment Deployed

Your PR environment has been deployed!

Environment Details:

Components:

  • Keeperhub Application
  • PostgreSQL Database (isolated instance)
  • LocalStack (SQS emulation)
  • Redis (isolated instance)
  • Schedule Dispatcher (staging image)
  • Block Dispatcher (staging image)
  • Event Tracker (staging image)

The environment will be automatically cleaned up when this PR is closed or merged.

Copy link
Copy Markdown

Looks very good there! probably a nit one, but if you have write permissions you should have read ones I guess. Not totally sure about this!

Anyways, currently for me looks good to merge

@sanbotto

Copy link
Copy Markdown
Author

Looks very good there! probably a nit one, but if you have write permissions you should have read ones I guess. Not totally sure about this!

I thought of that, makes sense, but I rather leave that decision to the user.

@joelorzet joelorzet left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

lgtm

@sanbotto sanbotto merged commit 9be6014 into staging Jun 22, 2026
43 checks passed
@sanbotto sanbotto deleted the feat/KEEP-841-read-only-mcp branch June 22, 2026 19:10
@github-actions

Copy link
Copy Markdown

🧹 PR Environment Cleaned Up

The PR environment has been successfully deleted.

Deleted Resources:

  • Namespace: pr-1592
  • All Helm releases (Keeperhub, Scheduler, Event services)
  • PostgreSQL Database (including data)
  • LocalStack, Redis
  • All associated secrets and configs

All resources have been cleaned up and will no longer incur costs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants