GitHub

Connect GitHub to ORQO so that agents can browse repositories, read files, search code, and sync repos as document sources for the knowledge graph.

Category	Development
Capabilities	MCP tools only (no send/receive channel)
Adapter path	/github
Auth method	Personal Access Token

info

GitHub is an MCP-only integration. It provides tools for agents to interact with repositories programmatically, and can sync repository content into the knowledge graph as a document source.

Prerequisites

• A GitHub account
• A Personal Access Token (classic or fine-grained) from github.com/settings/tokens
• Access to the ORQO Settings area

Setup

1. Create a Personal Access Token

1. Go to github.com/settings/tokens.
2. Click Generate new token.
3. For classic tokens: select the repo scope (or public_repo for public repos only).
4. For fine-grained tokens: grant Contents read access to the repositories you want to use.
5. Copy the generated token.

2. Install the GitHub App in ORQO

1. Navigate to Settings > Apps in ORQO.
2. Find GitHub in the app catalog and click Install.
3. The app is created with the correct adapter URL and capabilities.

3. Add Credentials

After installation, the credentials checklist shows what's required:

Credential	Type	Description
GITHUB_TOKEN	api_token	Personal Access Token for GitHub API access

Create the credential in Settings > Credentials with the key GITHUB_TOKEN, paste your token, then assign it to the GitHub App.

4. Verify the Connection

Click Verify on the GitHub app card in ORQO. This tests the token against the GitHub API and discovers the available MCP tools.

Available Tools

The GitHub adapter exposes MCP tools that agents can use in workflows:

Tool	Description
github_list_repos	List repositories accessible to the authenticated user
github_list_files	List files and directories at a path in a repository
github_read_file	Read the text content of a file in a repository
github_search_code	Search for code across repositories
source_list_changes	List all files in a repo with fingerprints for change detection
source_fetch_file	Download a file from a repository by path

These tools are discovered automatically when the App is verified and can be assigned to agents via Skills.

Document Source Tools

The source_list_changes and source_fetch_file tools support using GitHub repositories as document sources for the knowledge graph. They enable:

• Change detection — compare the current repo tree against a previous sync cursor to find added, modified, and deleted files.
• File filtering — use glob patterns (e.g., *.md) to sync only specific file types.
• Subpath scoping — sync a subdirectory of a repo using owner/repo:path/ format.

This allows ORQO to automatically keep its knowledge graph in sync with repository content.

Platform-Specific Behavior

• Token-based auth — GitHub uses a Personal Access Token, not OAuth. The token is sent as a Bearer header on every API request.
• Rate limiting — GitHub enforces API rate limits (5,000 requests/hour for authenticated users). The adapter returns errors if limits are exceeded.
• Repository path format — All tools use owner/name format for repository references (e.g., octocat/hello-world).
• No channel capabilities — GitHub does not support send/receive channels. It is a tool-only integration for programmatic repository access.

What's Next

• Connect Document Sources to auto-sync repository content into the knowledge graph
• Apps & Channels for the full architecture
• Create a Skill to bundle GitHub tools for agents
• Set Up Assignments to give agents access to GitHub tools in workflows