secure-github-ops
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | debug, info, warn, error (optional) | |
| GITHUB_TOKEN | Yes | Your GitHub PAT with repo access | |
| ALLOWED_REPOS | No | Lock it down to specific repos like owner/repo1,owner/repo2 (optional) | |
| ADMIN_API_KEYS | Yes | Comma-separated admin keys | |
| OPERATOR_API_KEYS | No | Comma-separated operator keys (optional) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| github.issues.createA | Create a GitHub issue (v1.0.0). Creates a pending action that requires admin approval before executing. |
| github.pr.openA | Open a GitHub pull request (v1.0.0). Creates a pending action that requires admin approval before executing. |
| github.comment.addA | Add a comment to a GitHub issue or pull request (v1.0.0). Creates a pending action that requires admin approval. |
| admin.approve_actionA | Approve and execute a pending action (v1.0.0). Admin role required. This is the ONLY way to execute GitHub write operations. |
| admin.deny_actionA | Deny a pending action (v1.0.0). Admin role required. |
| admin.list_pending_actionsB | List pending actions (v1.0.0). Admin role required. |
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 6 tools
Each tool has a distinct purpose: admin tools handle approval/denial/pending, while github tools target unique actions (comment, create issue, open PR). No overlap exists.
Tool names follow a domain.subdomain.action pattern, but admin tools use verb_noun (e.g., approve_action) while github tools use noun.verb (e.g., comment.add) and an abbreviation (pr.open). This minor inconsistency is manageable.
6 tools is well-scoped for a secure approval workflow with limited GitHub write operations. Each tool serves a necessary role without bloat.
The set covers creation and commenting but lacks update, delete, or merge operations for GitHub resources. Admin tools are complete for approval, but the overall surface feels incomplete for typical GitHub write needs.