[dev] Install git and linear MCP servers

[geropl]

Description

Where the MCP servers have write access is governed by these env vars one can set in their Gitpod settings:

• GIT_MCP_WRITE_ACCESS: if true, it enables push
• LINEAR_MCP_WRITE_ACCESS: if true, it enables adding/updating linear comments and issues

Also, for linear to work, it requires a LINEAR_API_KEY to be present.

Related Issue(s)

Fixes #

How to test

Documentation

Preview status

gitpod:summary

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft preemptible
  Saves cost. Untick this only if you're really sure you need a non-preemtible machine.
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[corneliusludmann]

I get the point of the setup of the install script. From a security standpoint, running a shell script from the main branch of a private repo sounds not that great, TBH.

Ideally, we should fork the repo in the gitpod org, IMO. Or at least fetch a specific commit instead of the latest from main. That would work as well, IMO. In both cases, it's need an action on Gitpod side when the script changes.

What do you think, am I being too restrictive here?

[geropl]

From a security standpoint, running a shell script from the main branch of a private repo sounds not that great, TBH.

Totally agree. But as we/I control those, I'd say let's give it a try for now. The only risk I see is that it could be taken as bad precedent.

I see it more as an experiment right now: If this works, we should add the binary to the base image.
And then maybe add the "register with cline" functionality as a subcommand to the binary... ? 🫧

[geropl]

@corneliusludmann But as I'm thinking about it, we can totally "vendor" the scripts here. Let me do that. 💯

[github-actions]

⚠️ Hey reviewer! BE CAREFUL ⚠️
Review the code before opening in your Gitpod. .gitpod.yml was changed and it might be harmful.

[geropl]

/unhold