Automic VaultAutomic Vault

brew

Install xcode-build-server with Homebrew, MacPorts

Build server protocol implementation for integrating Xcode with sourcekit-lsp. Version 1.3.0 via Homebrew; verified 2026-05-14.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install xcode-build-server

local Homebrew formula metadata

MacPortsverified · 94%
sudo port install xcode-build-server

MacPorts ports tree · devel/xcode-build-server/Portfile · source: api.github.com

overview

Package summary

Build server protocol implementation for integrating Xcode with sourcekit-lsp

Commands and aliases

  • xcode-build-server

history

Project history and usage

xcode-build-server is a Build Server Protocol implementation for using Xcode projects with Apple's SourceKit-LSP. Its README states the motivation plainly: SourceKit-LSP does not directly support Xcode projects, but it can integrate with other build systems through BSP.

Project history

The project was created by SolaWing to make iOS and Apple-platform development practical in editors outside Xcode. The README says the goal is to integrate Xcode with SourceKit-LSP and support the language set Xcode handles: Swift, C, C++, Objective-C, and Objective-C++.

xcode-build-server's implementation reflects the gap it fills. Instead of replacing Xcode's build system, it watches or parses Xcode build logs, extracts compile flags, and exposes the information SourceKit-LSP needs. The repository is primarily Python and includes the `xcode-build-server` executable, config helpers, log parsing code, and Xcode automation scripts.

The GitHub repository lists about 142 commits, five releases, and v1.3.0 as the latest release on 5 January 2026. Earlier release search results show v1.0.0 in February 2024, suggesting the tool moved from a useful niche script into a versioned utility as SourceKit-LSP/BSP workflows became more common.

Adoption history

Adoption is concentrated among Swift developers who want Neovim, VS Code, JetBrains IDEs, or another LSP-capable editor to understand Xcode projects. A Swift Forums discussion from 2024 describes SourceKit-LSP's BSP integration and the need for build servers to provide build settings, target information, and index data; xcode-build-server is one practical community implementation of that idea for Xcode.

The tool is cited in SourceKit-LSP issue discussions and editor setup guides as a working answer for Xcode project support. MacPorts describes it as implementing a build server to provide SourceKit-LSP with the build information it needs for an Xcode project, and the GitHub page shows nearly a thousand stars, making it one of the better-known utilities in this small niche.

How it is used

The simplest documented workflow is to run `xcode-build-server config` in the workspace root with a workspace or project and scheme. That creates or updates `buildServer.json` with `kind: xcode`, instructing the server to watch and use compile flags from the newest Xcode build log. Afterward, opening files with SourceKit-LSP enabled should provide editor intelligence.

For non-Xcode builds, the README documents `xcode-build-server parse` on a build log or on piped `xcodebuild` output. That mode writes compile information to `.compile` and updates `buildServer.json` with `kind: manual`. The README repeatedly notes that stale compile info should be refreshed by building again or rerunning the parse step when files, SDKs, configurations, or macros change.

The package-nerd detail is that it relies on the standard `buildServer.json` discovery convention used by BSP/LSP tooling. The project root must be the working directory where `buildServer.json` is created, so editor setup and repository layout matter as much as the executable itself.

Why package nerds care

xcode-build-server is significant because Xcode projects are historically hard to use outside Xcode. SourceKit-LSP supports Swift and C-family editor features, but it needs exact compiler arguments, SDK paths, target membership, and index locations. xcode-build-server turns Xcode's own build output into that missing protocol layer.

For Swift tooling users, it represents a pragmatic compromise: keep Xcode as the authoritative build system, but let other editors participate through SourceKit-LSP and BSP. That makes it a bridge between Apple's proprietary project model and the open editor tooling world.

Timeline

  • 2023: SourceKit-LSP issue discussions identify xcode-build-server as a practical solution for Xcode project support.
  • 2024-02-14: GitHub release listings show v1.0.0 and v1.0.1 releases.
  • 2024: Swift Forums discusses extending SourceKit-LSP's use of Build Server Protocol for richer build-system integration.
  • 2026-01-05: GitHub repository lists v1.3.0 as the latest release.

Related projects

  • SourceKit-LSP is Apple's language-server implementation for Swift and C-family languages and is the main consumer of the build information xcode-build-server provides.
  • The Build Server Protocol defines the editor-to-build-server layer that xcode-build-server implements.
  • Other Swift BSP work, such as sourcekit-bsp and Swift build-server experiments, addresses similar integration problems for different build systems.

security posture

Risk level: blue

broad file, network, media, or database tool signal.

Risk classifier

blue risk · medium confidence · tool

Why

  • broad file, network, media, or database tool signal

Signals

  • text:server

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 1 platform targets.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
./buildServer.json./.compile

executables

Installed executables

CommandKindExposureNote
xcode-build-servercliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version1.3.0
manager updated2026-05-14
local dataok
upstreamcurrent
latest detectedv1.3.0

https://github.com/SolaWing/xcode-build-server

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:xcode-build-server
Version1.3.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/xcode-build-server
Homepagehttps://github.com/SolaWing/xcode-build-server
Repositoryhttps://github.com/SolaWing/xcode-build-server
Upstream docshttps://github.com/SolaWing/xcode-build-server#readme
LicenseMIT
Source archivehttps://github.com/SolaWing/xcode-build-server/archive/refs/tags/v1.3.0.tar.gz
Last updated2026-05-14T17:32:27-04:00
Pulseupdated
Uses from macOSpython
Bottleavailable (on all)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namexcode-build-server
Version Scheme0
Revision0
Head VersionHEAD
Requirements
  • macos
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

MacPorts95%

xcode-build-server

sudo port install xcode-build-server
  • normalized package name match
  • Matched by: Xcode Build Server
MacPorts ports tree · api.github.com · MacPorts ports tree: devel/xcode-build-server/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment