Context Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JIRA_EMAIL | Yes | Email address associated with the Jira API token | |
| JIRA_BASE_URL | Yes | Your Atlassian base URL (e.g. https://yourcompany.atlassian.net) | |
| JIRA_API_TOKEN | Yes | Jira API token for authentication | |
| GITHUB_PERSONAL_ACCESS_TOKEN | No | GitHub PAT with actions:read scope |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_jira_ticketC | Retrieves a Jira ticket based on a ticket ID using the Jira REST API. |
| get_github_actions_runsC | Retrieves recent GitHub Actions workflow runs for a repository. |
| get_sentry_issuesC | Retrieves recent unresolved issues from a Sentry project. |
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 3 tools
Each of the three tools targets a different external service (Jira, GitHub Actions, Sentry) with an unambiguous, non-overlapping purpose. There is no realistic scenario in which an agent would confuse retrieving a Jira ticket with fetching CI runs or Sentry issues.
All three tools follow the same get_<source>_<resource> snake_case pattern (get_jira_ticket, get_github_actions_runs, get_sentry_issues). The convention is predictable and self-describing, so an agent can guess a tool name from its intent.
Three tools is at the thin end for a server framing itself as a 'context bridge' — each tool earns its place, but the surface is narrow. A single tool per integration means there is no fallback or alternative granularity, making it borderline under-scoped.
Read-only retrieval across three sources is coherent, but the surface has notable gaps for the stated purpose: only Actions runs (no PRs, commits, or issues), only unresolved Sentry issues (no detail or resolution filtering), and no pagination/filter parameters documented. Agents assembling cross-source context will hit dead ends quickly.