Skip to content
Integrations

Developer Tools

Connect GitHub to browse and edit real repositories, and Vercel to deploy them, from inside DevGhouse.

Developer Tools

If you write code, the Coding module connects DevGhouse to GitHub and Vercel so you (or an assistant working on your behalf) can read a file, commit a fix, and ship it, without leaving DevGhouse.

Open the Coding dashboard

  1. From your workspace home, turn on the Coding module if it is not on already (under Modules → Manage modules).
  2. Click the Coding tile.

Coding dashboard with GitHub and Vercel both connected

The dashboard shows GitHub, Vercel, and a few other features as tiles, and an Integrations panel at the bottom listing what is connected.

Connect GitHub

  1. On the Coding dashboard, find GitHub under Integrations and click Manage Connection (it reads Connect if you have not connected it yet).
  2. Sign in to GitHub and approve access.
  3. Once connected, click the GitHub tile to browse your repositories, pick a branch, open a file, edit it, and commit, right from DevGhouse.

GitHub page connected, listing imported repositories and their latest commits

With GitHub connected, you can also open issues and pull requests, review workflow runs, and manage collaborators, without switching to github.com.

Connect Vercel

  1. On the Coding dashboard, find Vercel under Integrations and click Manage Connection (or Connect).
  2. Sign in to Vercel and approve access.
  3. Click the Vercel tile to see your projects and deployments, trigger a new deployment, or check a deployment's build logs.

Vercel projects page connected, listing real deployments with their latest commit message and branch

For agents and routines

Once GitHub and Vercel are connected, an assistant with your MCP Server connected can work the same surface: list repositories with github_list_repositories, read a file with github_get_file_content, commit a change with github_create_or_update_file, open an issue with github_create_issue, and check a build with vercel_get_deployment_logs. Ask it to "read the pricing page in the client-storefront repo and fix the typo" and it can do the whole round trip: read, edit, commit.