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

Sourcehut Tickets (BYOK) — connector documentation

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

What Sourcehut Tickets (BYOK) is for

Sourcehut Tickets (BYOK) lets an AI assistant read your own Sourcehut Tickets data through the Sourcehut Tickets API with a key you supply (SourceHut personal access token (needs PROFILE, TRACKERS and TICKETS read scopes)). Read-only: 6 tools (get_me, list_trackers, get_tracker, list_tickets, get_ticket, list_labels). 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 todo.sr.ht. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Sourcehut Tickets. Sourcehut Tickets 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 tickets token for?"
  • "Which SourceHut issue trackers do I have?"
  • "Show the SourceHut tracker rid-example-1"
  • "What tickets are open in my SourceHut tracker rid-example-1?"
  • "Show ticket 1 of my SourceHut tracker rid-example-1"
  • "Which labels does my SourceHut tracker rid-example-1 use?"

What it does

  • get_me: Show the SourceHut account the token belongs to: username, canonical name, URL, location and bio.
  • list_trackers: List the issue trackers you own with name, description, visibility and dates; page with the returned cursor.
  • get_tracker: Get one tracker by resource id: name, description, visibility, owner and dates.
  • list_tickets: List the tickets of a tracker (newest activity first as the server orders them) with subject, status, resolution and labels.
  • get_ticket: Get one ticket by tracker and number: subject, body text, status, resolution, labels and assignees.
  • list_labels: List the labels defined on a tracker with name and colors.

BYOK key

You bring your own Sourcehut Tickets SourceHut personal access token (needs PROFILE, TRACKERS and TICKETS 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 todo.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 Tickets API (todo.sr.ht) with a BYOK key; documentation: https://docs.sourcehut.org/todo.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 Tickets. Sourcehut Tickets 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 Tickets account.

Built for: Worldwide. Languages: English.