Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Sourcehut Builds (BYOK) — connector documentation

  • MCP endpoint: https://byok-sourcehutbuilds.connectorbay.com/mcp
  • REST API: POST https://byok-sourcehutbuilds.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-sourcehutbuilds.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Sourcehut Builds SourceHut personal access token (needs PROFILE and JOBS read scopes), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-sourcehutbuilds.connectorbay.com/health · Tool schemas: https://byok-sourcehutbuilds.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-sourcehutbuilds · agent@connectorbay.com

What Sourcehut Builds (BYOK) is for

Sourcehut Builds (BYOK) lets an AI assistant read your own Sourcehut Builds data through the Sourcehut Builds API with a key you supply (SourceHut personal access token (needs PROFILE and JOBS read scopes)). Read-only: 7 tools (get_me, list_jobs, get_job, list_job_tasks, get_job_log, list_job_artifacts, list_user_jobs). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to builds.sr.ht. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sourcehut Builds. Sourcehut Builds and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which SourceHut account is my builds token for?"
  • "What are my latest SourceHut builds and did they pass?"
  • "Show SourceHut build job 1234"
  • "Which step of SourceHut build 1234 failed?"
  • "Show the log of SourceHut build job 1234"
  • "What files did SourceHut build 1234 produce?"

What it does

  • get_me: Show the SourceHut account the token belongs to: username, canonical name, URL, location and bio.
  • list_jobs: List your most recent build jobs (newest first) with status, note, tags, image and runner; page with the returned cursor.
  • get_job: Get one build job by id: status, note, tags, visibility, image, runner and dates.
  • list_job_tasks: List the tasks (steps) of a build job with their status and last update time, to see which step failed.
  • get_job_log: Get the build log of a job: the last 128 KiB of the main log and the URL of the full log.
  • list_job_artifacts: List the artifacts a build job produced with path, size and a download URL when available.
  • list_user_jobs: List the build jobs of another SourceHut user that you are allowed to see, newest first.

BYOK key

You bring your own Sourcehut Builds SourceHut personal access token (needs PROFILE and JOBS read scopes) (https://meta.sr.ht/oauth2/personal-token). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to builds.sr.ht over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Sourcehut Builds API (builds.sr.ht) with a BYOK key; documentation: https://docs.sourcehut.org/builds.sr.ht. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sourcehut Builds. Sourcehut Builds and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Sourcehut Builds account.

Built for: Worldwide. Languages: English.