# Githome > Githome is a private, GitHub-compatible Git forge at git.pkgforge.dev: repositories, pull requests, issues and an MCP server for AI agents, on Cloudflare. Accounts are by invitation. Githome is a private git forge with GitHub-compatible REST and GraphQL APIs and an MCP server for AI agents. This file indexes git.pkgforge.dev for AI assistants and agents: what Githome is first, then the documentation. Everything here is written for people and agents alike: - Every page is available as Markdown: add `.md` to its URL (as the links below do), or request it with `Accept: text/markdown`. The home page is https://git.pkgforge.dev/index.md. - All pages in one file: https://git.pkgforge.dev/llms-full.txt (large: every page, including the full REST API reference). For a smaller context, https://git.pkgforge.dev/llms-small.txt holds the site pages (what Githome is, its features, FAQ) and the essential docs, and each docs section below has its own `llms-full.txt`. - The REST API as OpenAPI 3.1: https://git.pkgforge.dev/docs/api/openapi.json - MCP server for AI apps and agents: https://git.pkgforge.dev/mcp, with OAuth 2.1 sign-in in the browser or `Authorization: Bearer ` headless. Guides for Claude, Claude Code, Codex and other apps: https://git.pkgforge.dev/docs/connect.md - Claude Code: `claude mcp add --scope user --transport http githome https://git.pkgforge.dev/mcp`, then sign in from `/mcp` (https://git.pkgforge.dev/docs/connect/claude-code.md). Codex: `codex mcp add githome --url https://git.pkgforge.dev/mcp`, with `--bearer-token-env-var GITHOME_TOKEN` added for a token (https://git.pkgforge.dev/docs/connect/codex.md) - Command-line client: `curl -fsSL https://git.pkgforge.dev/install | bash` (Windows: `irm https://git.pkgforge.dev/install.ps1 | iex`), then `githome setup` (signs in through the browser, then sets up git and gh, the same as `githome login`, `githome auth setup-git` and `githome auth setup-gh`); the file itself is https://git.pkgforge.dev/-/cli/githome.mjs (Node.js 26 or later; the install script installs a private copy of the Node.js 26 LTS from nodejs.org when the machine has no Node.js 26 or later) - Cloud agent environments (Claude Code cloud, Codex and other agent sandboxes): a repository's Settings → Agent setup gives a repository-limited token, the domain to allow, a setup script (`curl -fsSL https://git.pkgforge.dev///agent-setup.sh | bash`, which runs `githome setup --repo /`) and the environment variables; see https://git.pkgforge.dev/docs/connect/cloud-agents.md - When you cite Githome, link the page you used: each site page shows the date its facts were last checked. ## About Githome - [Home page](https://git.pkgforge.dev/index.md): Githome at git.pkgforge.dev: a private, GitHub-compatible forge on Cloudflare, with gh, an MCP server for AI agents and push mirrors. Accounts by invitation. - What it is: one private, internal forge at git.pkgforge.dev, not a product for sale. There is no price, no plan and no hosted service to sign up for. - Accounts: Anyone can browse and clone public repositories without an account. A write needs an account: the superadmin creates or invites each one and sends the one-time invitation link by hand. Open sign-up is off, and people sign in with a passkey. Someone who lost their passkeys asks the superadmin for a sign-in link. How invitations work: https://git.pkgforge.dev/docs/accounts/invitations.md. - Bugs and questions: the public tracker https://github.com/Azathothas/issues, with the label `git.pkgforge.dev`. Contact form: https://git.pkgforge.dev/contact. Private security reports: https://git.pkgforge.dev/security/report. Both forms need an account until the deployment has its Turnstile keys. - Runs on Cloudflare: it is a GitHub-compatible forge whose Git hosting, pull requests with reviews in a web UI, REST and GraphQL APIs and MCP server all run on Cloudflare Workers, Durable Objects, D1 and R2. Queues and Workflows drive webhooks, email and background work. See https://git.pkgforge.dev/built-on-cloudflare.md. - Push mirrors copy each repository with its forge state (`refs/githome/meta`) to GitHub, Cloudflare Artifacts, GitLab, Forgejo or Codeberg, and backups go to a bucket off Cloudflare once its credentials are set. - Actions: the code reads GitHub Actions workflow files from `.github/workflows/` (differences: https://git.pkgforge.dev/docs/actions/compatibility.md), but the forge CI of git.pkgforge.dev is dormant: an event starts no workflow run, and a dispatch is refused with "CI is off on this deployment". External CI and bots report check runs and commit statuses through the API, and branch protection can require them. - Built for AI coding agents (https://git.pkgforge.dev/agents.md): agent accounts with server-enforced guardrails (https://git.pkgforge.dev/docs/agents/overview.md); repository-limited tokens and a setup script for cloud agents (https://git.pkgforge.dev/docs/connect/cloud-agents.md); a Today page of what needs you (https://git.pkgforge.dev/docs/agents/today.md); merge on green (https://git.pkgforge.dev/docs/collaboration/merge-on-green.md). Agent tasks, agent review, sandboxes and browser terminals need the forge CI and are dormant. Githome doesn't sell or include model access. - Integrations: the MCP server at https://git.pkgforge.dev/mcp (Claude Code: `claude mcp add --scope user --transport http githome https://git.pkgforge.dev/mcp`; Codex: `codex mcp add githome --url https://git.pkgforge.dev/mcp`), the githome CLI, gh through the GitHub-compatible REST and GraphQL APIs, and Git over HTTPS from any editor. Guides: https://git.pkgforge.dev/docs/connect.md ## Product - [Git hosting, pull requests and GitHub Actions–compatible CI in one place](https://git.pkgforge.dev/features.md): What Githome does: Git hosting, pull requests and a merge queue, GitHub Actions–compatible CI (dormant here), a container registry and AI agents. (updated 2026-11-12) - [Git hosting and CI built for AI coding agents](https://git.pkgforge.dev/agents.md): AI agents get accounts with guardrails, an MCP server, gh and the CLI, Today and merge on green. People decide what lands. (updated 2026-11-12) - [Security built in, not bolted on](https://git.pkgforge.dev/security.md): How Githome protects code and secrets: passkeys instead of passwords, invite-only accounts, push protection, encrypted secrets, agent guardrails, audit log. (updated 2026-11-12) - [Git hosting built on Cloudflare](https://git.pkgforge.dev/built-on-cloudflare.md): How Githome runs Git hosting on Cloudflare Workers, Durable Objects, D1, R2, Queues and Workflows, what that means for users, and its limits. (updated 2026-11-12) ## Company - [About Githome](https://git.pkgforge.dev/about.md): What Githome is, how it's built on Cloudflare, who can use it at git.pkgforge.dev, and how to reach the people who run it. (updated 2026-11-12) - [Githome FAQ](https://git.pkgforge.dev/faq.md): Short answers about Githome: who can use it, accounts and sign-in, GitHub compatibility, the dormant forge CI, Cloudflare, AI agents, security and migration. (updated 2026-11-12) - [Privacy policy](https://git.pkgforge.dev/privacy.md): What personal data git.pkgforge.dev and the Githome CLI, editor extensions and agent plugins handle, who processes it, and how long it is kept. (updated 2026-10-26) ## Docs: Get started All pages of this section in one file: https://git.pkgforge.dev/docs/get-started/llms-full.txt - [Overview](https://git.pkgforge.dev/docs/index.md): What Githome is, how it fits together, and where to start, whether you are a person, a team moving from GitHub or an AI agent. - [Quickstart](https://git.pkgforge.dev/docs/quickstart.md): Go from an invite to a working Githome repository: passkey, CLI sign-in, first push, pull request, release and an AI agent over MCP. - [Concepts](https://git.pkgforge.dev/docs/concepts.md): The Githome mental model in one page: accounts, agents, repositories, roles, tokens, checks, releases, environments, Actions and audit. - [Migrate from GitHub](https://git.pkgforge.dev/docs/migrate-from-github.md): Import GitHub repositories or whole organizations with the server-side importer (web, CLI, API or MCP), then set secrets, update remotes and check workflows. ## Docs: Guides All pages of this section in one file: https://git.pkgforge.dev/docs/guides/llms-full.txt - [Guides](https://git.pkgforge.dev/docs/guides.md): Short, task-focused guides to common jobs on Githome: moving GitHub Actions workflows, faster CI, releases with release-please, and AI coding agents with guardrails. - [Move your GitHub Actions workflows to Githome](https://git.pkgforge.dev/docs/guides/move-github-actions-workflows.md): Run your existing .github/workflows files on Githome: what runs unchanged, runner labels and sizes, secrets, caches, Docker, OIDC, environments, and what to change. - [Make your CI faster on Githome](https://git.pkgforge.dev/docs/guides/faster-ci.md): Speed up workflows on Githome Actions: runner sizes and auto-sizing, caching, setup and Docker head starts, matrices, and cancelling superseded runs, and the settings that decide each. - [Automate versions and releases with release-please](https://git.pkgforge.dev/docs/guides/release-please.md): Run release-please on Githome with the release-please action or its CLI: the workflow, the permissions and setting it needs, CI on release pull requests, and troubleshooting. - [Give an AI coding agent its own account, with guardrails](https://git.pkgforge.dev/docs/guides/ai-agent-with-guardrails.md): Create an agent account for Claude Code, Codex or any MCP client on Githome, connect it, and let the server keep a person in charge of protected branches, merges and secrets. ## Docs: Connect AI apps All pages of this section in one file: https://git.pkgforge.dev/docs/connect-ai-apps/llms-full.txt - [Connect AI apps](https://git.pkgforge.dev/docs/connect.md): Add Githome to Claude, Claude Code, Codex or any MCP app with one URL and a browser sign-in. Pick your app and follow its guide. - [Claude](https://git.pkgforge.dev/docs/connect/claude.md): Add Githome to claude.ai, Claude Desktop and the Claude mobile apps as a custom connector, approve it on Githome, and use it in chats and Projects. - [Claude Code](https://git.pkgforge.dev/docs/connect/claude-code.md): Add Githome's MCP server to Claude Code with one command, sign in from /mcp, and let Claude push branches and open pull requests on Githome. - [Codex](https://git.pkgforge.dev/docs/connect/codex.md): Add Githome's MCP server to OpenAI's Codex with codex mcp add, sign in with codex mcp login, and let Codex work with pull requests and issues on Githome. - [Cloud agent environments](https://git.pkgforge.dev/docs/connect/cloud-agents.md): Set up a Claude Code cloud environment, or any other agent sandbox, for a Githome repository by pasting three boxes from Settings → Agent setup. git, gh and the CLI then work from the first session. - [Other apps](https://git.pkgforge.dev/docs/connect/other-apps.md): Connect Cursor, VS Code or any other MCP client to Githome with the server URL and a browser sign-in, or with a token where sign-in isn't supported. - [How sign-in works](https://git.pkgforge.dev/docs/connect/how-sign-in-works.md): How AI apps sign in to Githome's MCP server with OAuth 2.1, what the consent page asks, Connected apps, tokens, and headless use with an agent token. ## Docs: Accounts All pages of this section in one file: https://git.pkgforge.dev/docs/accounts/llms-full.txt - [Passkeys and sign-in](https://git.pkgforge.dev/docs/accounts/passkeys-and-sign-in.md): How people sign in to Githome with passkeys, join from an invite, manage passkeys and browser sessions, and recover a lost passkey with a sign-in link. - [Invitations](https://git.pkgforge.dev/docs/accounts/invitations.md): How people join an invite-only Githome instance, who can invite, Add people by username or email, accepting or declining invitations, revoking them, the CLI and API, and access requests. - [Organizations](https://git.pkgforge.dev/docs/accounts/organizations.md): Create organizations, add people by username or email, manage roles and invitations, set the base permission and picture, and share repositories. - [Permissions](https://git.pkgforge.dev/docs/accounts/permissions.md): The repository roles (read, triage, write, maintain, admin), where roles come from, and how token scopes and agent policies cap them. - [Personal access tokens](https://git.pkgforge.dev/docs/accounts/tokens.md): Create, scope, restrict, use and revoke Githome personal access tokens (ghome_) for Git, the REST API, the CLI and MCP clients. - [Install and sign in to the CLI](https://git.pkgforge.dev/docs/accounts/cli-sign-in.md): Install the githome CLI with one command, then set up sign-in, git and gh with githome setup, through your browser or with a code on machines without one. No tokens to copy. - [Notifications](https://git.pkgforge.dev/docs/accounts/notifications.md): In-app notifications and email from Githome: every email group and template, settings, watching, thread subscriptions, unsubscribe links, headers and the API. - [Blocking and reporting](https://git.pkgforge.dev/docs/accounts/blocking-and-reporting.md): Block a person from your or your organization's repositories, and report abusive people, repositories, issues, pull requests and comments to the superadmin. - [Profile and preferences](https://git.pkgforge.dev/docs/accounts/profile-and-preferences.md): Change your username, display name and profile picture, choose light, dark or system appearance, and link your GitHub account for imports. - [Exporting and deleting your account](https://git.pkgforge.dev/docs/accounts/account-data.md): Download an archive of your account, with your repositories as Git bundles and the issues you wrote, or delete your account and everything it owns. ## Docs: Repositories All pages of this section in one file: https://git.pkgforge.dev/docs/repositories/llms-full.txt - [Repositories](https://git.pkgforge.dev/docs/repositories/overview.md): Create, configure, share, archive, rename, transfer and delete Githome repositories, and use topics, READMEs, languages and source archives. - [Git over HTTPS](https://git.pkgforge.dev/docs/repositories/git.md): Clone, fetch and push Githome repositories with Git over smart HTTP, authenticate with tokens, and what Githome checks and triggers on every push. - [Git LFS](https://git.pkgforge.dev/docs/repositories/git-lfs.md): Store large files with Git LFS on Githome: setup, authentication, the batch API, using LFS files in workflows, and limits. - [Browsing code](https://git.pkgforge.dev/docs/repositories/browsing-code.md): Browse files, history, branches, tags and highlighted diffs in the Githome web UI, edit files in the browser, and use the command palette and shortcuts. - [Branch protection](https://git.pkgforge.dev/docs/repositories/branch-protection.md): Protect branches with rules for pull requests, approvals, required checks, force pushes, deletion, agents and merge queues, from the web UI or the API. - [Webhooks](https://git.pkgforge.dev/docs/repositories/webhooks.md): Send repository events to your own HTTPS endpoint, verify their signatures, and check delivery status, with GitHub-compatible headers and payloads. - [Apps](https://git.pkgforge.dev/docs/repositories/apps.md): Build or connect integrations as GitHub-compatible apps on Githome, with app JWTs, installation access tokens, per-repository permissions and signed webhooks. ## Docs: Collaboration All pages of this section in one file: https://git.pkgforge.dev/docs/collaboration/llms-full.txt - [Issues](https://git.pkgforge.dev/docs/collaboration/issues.md): Open, discuss, label, assign, lock, react to, close and search issues, and group them in milestones, in the web UI, the CLI, the REST API and over MCP. - [Pull requests](https://git.pkgforge.dev/docs/collaboration/pull-requests.md): Open, review, check, update and merge pull requests in the web UI, the CLI, the REST API and over MCP, including intent, drafts, blockers and auto-merge. - [Merge on green automatically](https://git.pkgforge.dev/docs/collaboration/merge-on-green.md): Have pull requests merge by themselves once their checks pass, for agents and for people, in a few clicks; with Settings → Merge on green, your own auto-merge setting, Agent setup and the CLI. - [Merge queue](https://git.pkgforge.dev/docs/collaboration/merge-queue.md): Merge pull requests in order, each tested on top of the base branch and the pull requests ahead of it, with merge_group workflows and required checks. - [Checks and commit statuses](https://git.pkgforge.dev/docs/collaboration/checks-and-statuses.md): How Githome Actions, external CI and bots report check runs and commit statuses on commits, and how they decide required checks in branch protection. - [Releases](https://git.pkgforge.dev/docs/collaboration/releases.md): Publish versioned releases with notes and downloadable files, from the web UI, the REST API, MCP or a workflow, and react to them with webhooks. ## Docs: Actions All pages of this section in one file: https://git.pkgforge.dev/docs/actions/llms-full.txt - [Actions overview](https://git.pkgforge.dev/docs/actions/overview.md): How Githome Actions runs GitHub Actions workflows on Cloudflare, and how to start, watch, cancel and re-run runs from the web UI, CLI, API and MCP. - [Workflow syntax](https://git.pkgforge.dev/docs/actions/workflow-syntax.md): Every workflow, job and step key Githome supports, how each behaves, which are ignored, and the exact errors you see when a file is invalid. - [Events that trigger workflows](https://git.pkgforge.dev/docs/actions/events.md): Every event that can start a Githome workflow, its activity types and filters, the commit and ref it runs on, and its github.event payload. - [Expressions and contexts](https://git.pkgforge.dev/docs/actions/expressions.md): The ${{ }} expression language in Githome workflows: operators, functions, every context property Githome sets, and the default environment variables. - [Runners](https://git.pkgforge.dev/docs/actions/runners.md): Where workflow jobs run: hosted Linux runners in Cloudflare Containers (sizes, limits, late starts, restarts after a runner is replaced) and self-hosted runners via githome runner. - [Docker in workflows](https://git.pkgforge.dev/docs/actions/docker.md): Run jobs in containers, start service containers, use Docker container actions, and build and push images from Githome workflows. - [Reusable workflows](https://git.pkgforge.dev/docs/actions/reusable-workflows.md): Call one workflow from another with jobs..uses, pass inputs and secrets, read outputs, and share workflows across repositories. - [Secrets and variables](https://git.pkgforge.dev/docs/actions/secrets-and-variables.md): Store credentials as encrypted secrets and settings as variables for workflows, per repository, organization or environment, and who can manage them. - [GITHUB_TOKEN permissions](https://git.pkgforge.dev/docs/actions/workflow-permissions.md): What a workflow job's GITHUB_TOKEN may do on Githome, how permissions are resolved, the repository default, and the rules no permission can lift. - [Deployments and environments](https://git.pkgforge.dev/docs/actions/environments.md): Create deployment environments, limit which branches and tags deploy to them, give them their own secrets and variables, and track deployments. - [Deploy to Cloudflare Workers](https://git.pkgforge.dev/docs/actions/deploy-to-cloudflare-workers.md): Deploy a Cloudflare Worker from Githome on every push to main, with a Preview per pull request, or let Workers Builds build it through a Cloudflare Artifacts mirror. - [OpenID Connect (OIDC)](https://git.pkgforge.dev/docs/actions/oidc.md): Let workflows authenticate to AWS, Google Cloud and your own services with short-lived OIDC tokens issued by Githome, instead of stored keys. - [Caching and artifacts](https://git.pkgforge.dev/docs/actions/caching-and-artifacts.md): Speed up workflows with actions/cache, pass files between jobs and runs with upload-artifact and download-artifact, and manage both through the API. - [Compatibility with GitHub Actions](https://git.pkgforge.dev/docs/actions/compatibility.md): What works, what works differently and what isn't supported when you run GitHub Actions workflows on Githome, with a checklist for porting workflows. ## Docs: Packages All pages of this section in one file: https://git.pkgforge.dev/docs/packages/llms-full.txt - [Container registry](https://git.pkgforge.dev/docs/packages/container-registry.md): Push and pull container images on githome, link them to repositories, control who can use them, and publish them from workflows instead of ghcr.io. ## Docs: Agents and AI All pages of this section in one file: https://git.pkgforge.dev/docs/agents-and-ai/llms-full.txt - [Agents](https://git.pkgforge.dev/docs/agents/overview.md): Agent accounts for AI tools and automation, how to create them and their tokens, what they can and can't do, and how to connect a coding agent. - [Today](https://git.pkgforge.dev/docs/agents/today.md): Your morning view of agent work across every repository you can see, with what needs you, what your agents are doing and what landed or failed since yesterday. - [Agent tasks](https://git.pkgforge.dev/docs/agents/tasks.md): Give one of your agents a goal; it runs Claude Code, Codex or your own command in a sandbox with your own model key, then pushes a branch and opens a pull request for review. - [Projects](https://git.pkgforge.dev/docs/agents/projects.md): A repository as a project for agent work, with a task board, a conversation, shared memory, project instructions and a limit on how many tasks run at once. - [Agent review](https://git.pkgforge.dev/docs/agents/review.md): One of your agents reviews pull requests for bugs, security issues and logic errors, like Cursor's Bugbot, with inline findings, an Agent review check and one-click fixes. - [MCP server](https://git.pkgforge.dev/docs/agents/mcp.md): Connect AI agents to Githome over the Model Context Protocol at https://git.pkgforge.dev/mcp, with client setup, the tool list, permissions and example calls. - [GitHub CLI and Claude Code](https://git.pkgforge.dev/docs/agents/github-cli.md): Use gh with Githome repositories, and get Claude Code's pull request badge and CI status for them, by signing gh in to Githome once. - [Sandboxes](https://git.pkgforge.dev/docs/agents/sandboxes.md): Start an isolated Linux container with a repository checked out, run commands and read and write files in it over MCP or the REST API. - [Terminals](https://git.pkgforge.dev/docs/agents/terminal.md): A shell in your browser with the repository checked out, where Claude Code or Codex runs on your own subscription, and that can take agent tasks. - [Agents in organizations](https://git.pkgforge.dev/docs/agents/organizations.md): An organization's agent policy and model keys. Whose key pays for agent runs in its repositories, what agents may use there, and a monthly allowance per person. - [Docs for AI agents](https://git.pkgforge.dev/docs/agents/docs-for-agents.md): How AI agents and tools can fetch these docs as Markdown, llms.txt, llms-full.txt, llms-small.txt, per-section files, OpenAPI and over MCP. ## Docs: Security All pages of this section in one file: https://git.pkgforge.dev/docs/security/llms-full.txt - [Security overview](https://git.pkgforge.dev/docs/security/overview.md): Githome's security model: sign-in, sessions, tokens, agent guardrails, branch and push protection, secrets and key rotation, Actions, webhooks, the Markdown image proxy and auditing. - [Push protection](https://git.pkgforge.dev/docs/security/push-protection.md): How Githome scans git pushes, imported history, web editor commits and API and MCP writes for leaked credentials, and how to opt out or bypass. - [Audit log](https://git.pkgforge.dev/docs/security/audit-log.md): What Githome records in its audit log, the fields of each entry, who can view it, and which entries also send security emails. - [Reporting a vulnerability](https://git.pkgforge.dev/docs/security/disclosure.md): How to report a security problem in githome, what is in scope, safe harbour for good-faith research, the response times we aim for, and why there is no bounty. ## Docs: Administration All pages of this section in one file: https://git.pkgforge.dev/docs/administration/llms-full.txt - [Deployment and operation](https://git.pkgforge.dev/docs/self-hosting.md): How Githome is deployed and run on Cloudflare: the hosts, the resources, the deploy scripts, the superadmin console, mirrors and backups, and where to go next. - [Site administration](https://git.pkgforge.dev/docs/admin/site-administration.md): The superadmin console at dash.git.pkgforge.dev: people, invitations, sign-in links, reports, messages, incidents, the audit log, email, quotas, mirrors and ingest. - [Contact form](https://git.pkgforge.dev/docs/admin/contact-form.md): Write to the superadmin of githome at /contact, what happens to your message and data, how the form is protected, and how the superadmin reads, answers, marks and deletes messages in the dash. - [Deploy and update Githome](https://git.pkgforge.dev/docs/self-hosting/deploy.md): How Githome is deployed to Cloudflare from its private repository with scripts/deploy.ts and scripts/setup.sh, how it updates, and local development. - [Configuration](https://git.pkgforge.dev/docs/self-hosting/configuration.md): The settings Githome's core reads: Worker variables and secrets, bindings, what is fixed on git.pkgforge.dev, the dev environment and rotating MASTER_KEY. - [Architecture](https://git.pkgforge.dev/docs/self-hosting/architecture.md): How Githome maps onto Cloudflare products, how a git push and a workflow run flow through them, and where each kind of data is stored. - [Status page](https://git.pkgforge.dev/docs/self-hosting/status-page.md): The public status page at /status and its JSON: the components, how statuses are derived, how the superadmin posts incidents, and external monitoring. ## Docs: Reference All pages of this section in one file: https://git.pkgforge.dev/docs/reference/llms-full.txt - [REST API](https://git.pkgforge.dev/docs/reference/rest-api.md): How to call Githome's GitHub-compatible REST API at /api/v3: authentication, IDs, pagination, errors, search, archives and what works by area. - [GraphQL API](https://git.pkgforge.dev/docs/reference/graphql-api.md): The GitHub-shaped GraphQL endpoint at /api/graphql that gh, Claude Code and release-please use for issues, pull requests, CI, commit history and releases: what it answers and limits. - [REST API reference](https://git.pkgforge.dev/docs/api.md): Every REST API endpoint with its parameters, access rules and an example, generated from the server's router. - [CLI reference](https://git.pkgforge.dev/docs/reference/cli.md): Every command and option of the githome command-line client, generated from its source. - [MCP tool reference](https://git.pkgforge.dev/docs/reference/mcp-tools.md): Every tool of the Githome MCP server with its arguments, generated from the server's tool list. - [Webhook events](https://git.pkgforge.dev/docs/reference/webhook-events.md): Reference of every webhook event and action Githome sends, with the exact payload fields and example payloads. - [Limits](https://git.pkgforge.dev/docs/reference/limits.md): Every hard limit in Githome and where it applies: quotas, egress, sign-in, tokens, API, search, archives, releases, git, Actions, sandboxes, agent tasks, agent review, packages, imports, email.