ghark
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GH_TOKEN | No | A GitHub personal access token with read access to the repositories and pull requests you watch. Provide either GH_TOKEN or GITHUB_TOKEN. | |
| GITHUB_TOKEN | No | A GitHub personal access token with read access to the repositories and pull requests you watch. Provide either GH_TOKEN or GITHUB_TOKEN. | |
| GHARK_POLL_SECONDS | No | Polling interval in seconds. The default is 30 seconds. | 30 |
| GHARK_BATCH_SECONDS | No | Event coalescing window in seconds. The default is 5 seconds. | 5 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {
"claude/channel": {}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| subscribeB | Watch a GitHub pull request for new activity. |
| unsubscribeC | Stop watching a pull request. |
| subscriptionsA | List pull requests watched by this session. |
| pending_eventsB | Read pending events and report any events dropped at the queue limit. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a clearly distinct operation: subscribe and unsubscribe are opposite pair, subscriptions lists watches, and pending_events reads queued events. There is no realistic confusion between listing subscriptions and reading pending events, as they operate on different resources.
Names are all snake_case and thematically coherent (subscribe/unsubscribe/subscriptions pair nicely). The only minor deviation is pending_events being a pure noun while the others read as verbs/plurals, but overall the pattern is predictable and readable.
Four tools is well-matched to the narrow, focused purpose of watching pull requests for a session. It is on the lean side but each tool pulls its weight, so nothing feels redundant.
The watch lifecycle is fully covered: add (subscribe), remove (unsubscribe), list (subscriptions), and consume events (pending_events). Minor gaps exist around identifying the session or inspecting individual events, but the core workflow is complete.