Integration

Beanstalk integration

Beanstalk (beanstalkapp.com, by Wildbit) hosts Git and Subversion repositories with code review and deployments. Agents can list and manage repositories, branches and tags, read commits and their diffs, browse files, comment on commits, run code reviews (request, comment, raise and resolve issues, assign, approve, cancel, reopen), start and retry deployments to server environments, and manage users, invitations, team membership and repository permissions. Not exposed: release servers (they hold server credentials), integrations, public and feed keys, repository imports, code review settings, adding or removing watchers, editing files, updating the account, creating, changing or deleting teams and server environments, and deleting users, repositories, code reviews or review issues. Authentication is HTTP Basic with a Beanstalk username and one of its API access tokens (API access must be enabled by the account owner), plus the account sub-domain (the part before .beanstalkapp.com).

Connect Beanstalk How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Beanstalk.Built from the 65 Beanstalk tools below, on the connection you add once.

What you can do with Beanstalk

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

User, 8 operations

add_team_userAdd team userPUTAdds a user to a team.
create_userCreate userPOSTCreates a user in the account with a login, email, name and password. Needs admin privileges.
get_userGet userGETReturns one user of the account by id: login, name, email, admin and owner flags and time zone. Needs admin privileges.
list_team_usersList team usersGETLists the users of a team (personal data: names and emails).
list_user_commentsList user commentsGETLists the code comments written by one user across repositories. Admins pass user_id for any user; without it, the caller's own comments.
list_usersList usersGETLists the account's users: login, name, email, admin and owner flags, time zone. Needs admin privileges. Contains personal data.
remove_team_userRemove team userDELETERemoves a user from a team.
update_userUpdate userPUTUpdates a user's email, name, admin flag or time zone; only the fields sent change. Needs admin privileges.

Comment, 6 operations

create_code_review_commentCreate code review commentPOSTAdds a discussion comment (Markdown) to a code review; its watchers get an email.
create_commentCreate commentPOSTPosts a comment on a changeset (by revision) of a repository.
get_code_review_commentGet code review commentGETReturns one discussion comment of a code review.
get_commentGet commentGETReturns one code comment by id: body, rendered HTML, author, file, line and revision.
list_code_review_commentsList code review commentsGETLists the discussion comments of a code review, with paging totals.
list_commentsList commentsGETLists the code comments of a repository, or of one changeset with revision: body, author, file, line and revision.

Code review, 5 operations

create_code_reviewCreate code reviewPOSTRequests a code review of a branch against another, optionally assigning reviewers and watchers, who are notified.
get_code_reviewGet code reviewGETReturns one code review by id: branches, state, possible transitions, requester, assignees and comment and event counts.
list_code_reviewsList code reviewsGETLists code reviews across the repositories the user can access, filterable by state, creator and assignee, with paging totals.
list_repository_code_reviewsList repository code reviewsGETLists the code reviews of one repository, with the same filters and paging as list_code_reviews.
update_code_reviewUpdate code reviewPUTUpdates a code review's description or merge flag. State changes have their own tools.

Repository, 5 operations

create_repositoryCreate repositoryPOSTCreates a Git or Subversion repository with a name (unique in the account) and a title. Needs admin privileges.
get_repositoryGet repositoryGETReturns one repository by id: name, title, type, default branch, clone URL, color label, storage used and last commit time.
list_repositoriesList repositoriesGETLists the account's Git and Subversion repositories: id, name, title, type, default branch, clone URL, color label and last commit time.
list_repository_changesetsList repository changesetsGETLists the commits of one repository: message, author, time, revision or hash and changed files.
update_repositoryUpdate repositoryPUTUpdates a repository's title, description, color label or default branch; only the fields sent change. Needs admin privileges.

Release, 4 operations

create_releaseCreate releasePOSTStarts a real deployment of a revision to a server environment (its servers receive the code). Pending new or retry releases of it are deleted.
get_releaseGet releaseGETReturns one deployment by id: state (pending, waiting, failed, success, skipped), revision, environment and times.
list_releasesList releasesGETLists recent deployments (releases) across the account: state, revision, environment, comment, author and times.
list_repository_releasesList repository releasesGETLists the deployments (releases) of one repository: state, revision, environment, comment, author and times.

Assignee, 3 operations

assign_code_reviewAssign code reviewPOSTAssigns a user with access to the repository to a code review.
list_code_review_assigneesList code review assigneesGETLists the users assigned to a code review, with when they were assigned and approved.
unassign_code_reviewUnassign code reviewDELETERemoves a user from the assignees of a code review.

Invitation, 3 operations

create_invitationCreate invitationPOSTInvites a person into the account: creates their user and emails them a signup link.
get_invitationGet invitationGETReturns one invitation by id: creator, invited user id and dates.
list_invitationsList invitationsGETLists the account's invitations: who created each one, the invited user id and creation dates.

Issue, 3 operations

create_code_review_issueCreate code review issuePOSTAdds an issue (a comment that needs action, Markdown) to a code review.
get_code_review_issueGet code review issueGETReturns one issue of a code review: its comment, and who resolved it and when.
list_code_review_issuesList code review issuesGETLists the issues of a code review, optionally only open or only resolved ones, with paging totals.

Permission, 3 operations

delete_permissionDelete permissionDELETERemoves one repository permission from a user by its id. Needs admin privileges.
list_user_permissionsList user permissionsGETLists a user's repository permissions: read, write and deployment access per repository. Admins can read any user's; other users only their own.
set_permissionSet permissionPOSTSets a user's permissions on one repository (read, write, deployment access), replacing the permissions they had there. Needs admin privileges.

Changeset, 2 operations

get_changesetGet changesetGETReturns one commit of a repository by its revision number or hash: message, author, time and changed files and directories.
list_changesetsList changesetsGETLists recent commits across every repository the user can see: message, author, time, revision or hash and changed files.

Reopen, 2 operations

reopen_code_reviewReopen code reviewPUTReopens an approved or cancelled code review.
reopen_code_review_issueReopen code review issuePUTMarks a resolved issue of a code review as unresolved again.

Server environment, 2 operations

get_server_environmentGet server environmentGETReturns one deployment environment of a repository by id: name, branch, deployment mode and current revision.
list_server_environmentsList server environmentsGETLists a repository's deployment environments (for example staging or production): name, branch, automatic or manual mode, current revision.

Team, 2 operations

get_teamGet teamGETReturns one team by id: name, color label and dates.
list_teamsList teamsGETLists the account's teams: id, name, color label and dates.

Account, 1 operation

get_accountGet accountGETReturns the Beanstalk account: id, name, sub-domain, time zone, plan id, owner id and whether it is suspended for a failed payment.

Approve, 1 operation

approve_code_reviewApprove code reviewPUTApproves a code review; with the merge flag set, the reviewed branch is merged.

Blob, 1 operation

get_blobGet blobGETReturns the contents of a blob (file) of a Git repository by its SHA id, with its content type.

Branch, 1 operation

list_branchesList branchesGETLists the branches of a Git repository.

Cancel, 1 operation

cancel_code_reviewCancel code reviewPUTCancels a code review; it stays readable with its history.

Current, 1 operation

get_current_userGet current userGETReturns the user the credentials belong to: login, name, email, admin and owner flags and time zone.

Difference, 1 operation

get_changeset_diffsGet changeset diffsGETReturns the per-file diffs of one commit: path, change status and diff text.

Event, 1 operation

list_code_review_eventsList code review eventsGETLists the events of a code review (requests, comments, issues, approvals, state changes), with paging totals.

For branch, 1 operation

find_code_review_by_branchesFind code review by branchesGETFinds the code review of a repository for a source and target branch pair.

Node, 1 operation

get_nodeGet nodeGETReturns a file or directory of a repository at a path and revision: its children for a directory, and optionally size and contents for a file.

Plan, 1 operation

list_plansList plansGETLists the Beanstalk subscription plans with their limits (repositories, users, storage, servers) and price.

Rename, 1 operation

rename_repositoryRename repositoryPUTRenames a repository (its file-system name, which changes its clone URL). Needs admin privileges.

Resend, 1 operation

resend_invitationResend invitationPUTEmails the invitation again to an invited user who has not signed up yet.

Resolve, 1 operation

resolve_code_review_issueResolve code review issuePUTMarks an issue of a code review as resolved.

Retry, 1 operation

retry_releaseRetry releasePUTRetries a failed deployment, deploying to its servers again.

Tag, 1 operation

list_tagsList tagsGETLists the tags of a Git repository.

Watcher, 1 operation

list_code_review_watchersList code review watchersGETLists the users and teams watching a code review.

Use Beanstalk from Claude Code, Cursor or Codex

Connect Beanstalk in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Beanstalk operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Beanstalk

Create your workspace
Sign up free. Nothing to install.
Connect Beanstalk once
Add your Beanstalk connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.