ContextBridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | Yes | Your GitHub token for accessing the GitHub API. | |
| GEMINI_API_KEY | No | Google Gemini API key for chat provider. | |
| OPENAI_API_KEY | No | OpenAI API key for chat provider. | |
| CONTEXTBRIDGE_DRY_RUN | No | If true, mutation tools are simulated rather than executed. | true |
| GITHUB_WRITES_ENABLED | No | If true, live GitHub write operations are enabled when approved. | false |
| CONTEXTBRIDGE_CHAT_READ_ONLY_DEFAULT | No | Default read-only mode for chat interface. | true |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoA | Return identity and runtime information for this ContextBridge server. |
| healthA | Return a lightweight health check for the ContextBridge process. |
| github_connection_statusA | Check GitHub authentication and return the connected account plus rate-limit state. |
| list_repositoriesB | List repositories accessible to the authenticated GitHub token. Read-only. |
| get_repositoryA | Get metadata for one GitHub repository. Read-only. |
| search_issuesA | Search GitHub issues across accessible repositories using safe structured filters. Read-only. |
| get_issueB | Get one GitHub issue by repository and number. Read-only. |
| list_pull_requestsB | List pull requests for a GitHub repository. Read-only. |
| get_pull_requestA | Get detailed metadata for one GitHub pull request. Read-only. |
| list_commitsA | List commits in a repository, optionally filtered by branch, path, author, or time. Read-only. |
| get_file_contentsB | Read a UTF-8 text file or list a directory in an accessible GitHub repository. Read-only. |
| search_codeA | Search code visible to the authenticated GitHub token. Read-only; subject to GitHub code-search limits. |
| get_workflow_runsB | List GitHub Actions workflow runs for a repository. Requires Actions: read. Read-only. |
| get_commit_statusA | Get combined legacy commit-status contexts for a SHA, branch, or tag. Requires Commit statuses: read. |
| get_tool_metricsB | Return tool-call success, failure, latency, and per-tool metrics from local telemetry. |
| get_recent_tool_callsB | Return recent local MCP tool executions with redacted arguments and timing/error metadata. |
| get_audit_summaryB | Summarize the immutable local audit stream and return its most recent events. |
| get_evaluation_summaryA | Return the latest or specified local tool-selection evaluation summary. Read-only. |
| get_write_policyA | Inspect mutation gates and human-confirmation requirements without changing anything. |
| list_pending_actionsA | List human-confirmation actions. This tool cannot approve or reject them. |
| get_pending_actionA | Inspect one pending/decided action by ID without changing its state. |
| execute_approved_actionC | Execute exactly one human-approved action; DRY_RUN simulates without contacting GitHub. |
| create_issueA | Request creation of a GitHub issue; queues exact action for human approval. |
| add_issue_commentA | Request an issue comment; queues exact action for human approval. |
| add_labelsA | Request existing labels be added to an issue; queues exact action for human approval. |
| close_issueA | Request closure of an issue; destructive action always requires human approval. |
| reopen_issueA | Request reopening of an issue; queues exact action for human approval. |
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 27 tools
Tools separate cleanly into read-only GitHub queries, mutation requests, approval actions, and telemetry. A few telemetry tools (get_audit_summary vs get_evaluation_summary) could be confused, but descriptions clarify their distinct sources. No two tools appear to do the same operation.
Most tools follow verb_noun snake_case (list_repositories, create_issue, get_workflow_runs). Two exceptions: server_info and health lack verbs, and github_connection_status is a noun phrase. Consistency is strong overall but not perfect.
27 tools is above the comfortable range. The count is inflated by four telemetry tools that could arguably be combined. However, the server covers multiple subdomains (GitHub reads, mutation requests, approval execution, system health), so the count is defensible albeit heavy.
Read-only GitHub coverage is broad (repos, issues, PRs, commits, code, workflows, file contents). Mutation coverage is limited to issues (create, comment, label, close, reopen) with no PR mutations or issue editing. The human-approval workflow is well-defined, but the lack of broader write operations creates noticeable gaps for a GitHub-oriented server.