Build Service FAQs

Question 1

How does Build Service ensure secure operations?

Accepted Answer

Security is a core feature. Build Service uses validated commands to prevent accidental harmful operations. For remote access via HTTP, it employs session key authentication to ensure only authorized clients can interact with your repositories and build environments.

Question 2

What Git operations are supported by Build Service?

Accepted Answer

To ensure security, Build Service supports a limited set of safe Git operations including `status`, `log`, `checkout`, `pull`, `branch`, `diff`, `fetch`, and `show`.

Question 3

Does Build Service provide real-time output for long-running tasks?

Accepted Answer

Yes, in addition to its MCP protocol, Build Service features a Hybrid REST/Streaming API. It provides REST endpoints for quick operations and a Streaming SSE API that delivers real-time, line-by-line output for long-running commands like complex builds or extensive Git operations.

Question 4

What is Build Service?

Accepted Answer

Build Service is a Model Context Protocol (MCP) server that provides secure and controlled access to software project repositories. It enables AI assistants and other clients to execute builds, run tests, and perform safe Git operations across multiple projects.

Question 5

Can Build Service manage multiple software repositories?

Accepted Answer

Yes, Build Service offers robust multi-repository support. It automatically discovers Git repositories within its configured directory, allowing you to manage various projects from a single service instance.

Build Service

About

Key Features

Use Cases