Ben Lambert

@niallthomson that's correct. There's a little bit of docs [here](https://github.com/backstage/backstage/tree/master/plugins/mcp-actions-backend#authentication-configuration) which specifically callout that this is basically just an interim solution until we work out how to take forward `device...

@niallthomson so the RFC outlines that this will be a possibility: > In order to allow for flexibility in the MCP servers available to end users, it will be configurable...

I wonder if we should be moving in #22244 direction instead? `git:repo:push` and `gitlab:mr:create` with a branch name instead. It feels like we're halfway there to be honest with this...

@madsteer I think that's what https://github.com/backstage/backstage/issues/30083#issuecomment-3004442297 is referring to, there's a PR out to fix it, could you test with that code?

Is the `stepId` not unique enough here? Aren't they unique across all steps? :pray:

@jvmdc yeah I appreciate your use case - I wonder if there's another way we can do that though. Thinking something like: `ctx.checkpoint({ key: 'asd', global: true }, () =>...

> stepId is unique, I would include stepName only to make it human readable, otherwise with many steps, the manual correlation, what step 16 out of 25 can lead to...

Let's go with this :tada:

:wave: Hey! Thanks for raising this issue, I think that you might want to follow in the footsteps of @benjidotsh did to add the `autocomplete` to the bitbucket picker. https://github.com/backstage/backstage/pull/25132...

https://github.com/backstage/backstage/pull/27367 is the latest work on this